ASC 2022 - API Specifications Conference

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

Inter-parameter dependencies are constraints that restrict the way in which two or more input parameters of an API operation can be combined to form valid calls to the service. For example, in the search operation of the YouTube API, when looking for videos in 3D (videoDimension='3d'), the type parameter must be set to 'video' (type='video'), otherwise a client error is returned. Four out of every five APIs contain these dependencies, and yet they are not supported by current API specification languages. Instead, they must be written in natural language, which is ambiguous and hinders the automation of many tasks in the API life cycle such as code generation, documentation and testing. OpenAPI users want this feature integrated into the standard, as reflected in the GitHub issue #256: “Support interdependencies between query parameters”. This issue has become the most upvoted issue of all time in the OpenAPI repository (over 500 positive reactions), and is still open after seven years.

In this talk, I aim to raise awareness of the problem of inter-parameter dependencies in web APIs, and how supporting them in current API specification languages would benefit greatly existing tool ecosystems. I will discuss the frequency and rich variety of these dependencies in real-world APIs, giving examples. Then, I will delve into my team’s experience on devising a solution to specify and support the automated analysis of these dependencies, and how we integrated this solution into OpenAPI. I will finish commenting on several applications that this solution has enabled, including automated testing of APIs with dependencies, a dependency-aware API gateway, and automated generation of client and server code including built-in assertions for the dependencies specified. These applications are promising results of what could be achieved if inter-parameter dependencies were part of the standard.

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

Every company is either making their own API style guide or following something shared in the industry. But there is no easy way to bootstrap an API style guide, generate all the Spectral rules and incorporate them into existing API descriptions (e.g. in an OpenAPI or AsyncAPI format). In this talk I want to share my experience with building and automating API style guides, quick wins and common painpoints; and invite the API community to collaborate together on creating a visual constructor for API style guides and unified ways of referring to API styles from popular API specifications.

I believe this should greatly improve interoperability of APIs and make it easier for developers to learn about API behaviors directly from API specifications.

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

Application testing is one of the biggest barriers to achieving truly Continuous Deployments because it's use-case specific. Developers often avoid writing test cases because its time consuming, needs to be maintained for every change and metrics like coverage don't necessarily guarantee quality.

In this session, we'll talk about how we could capture test cases from traffic data, how all infrastructure can be mocked automatically and how application writes could be safely replayed. We'll walk through examples of how keploy can work alongside existing testing frameworks and capture test cases quickly and mock infrastructure without needing to write Unit API test cases. We'll also cover how these test cases would evolve as the application grows.

The core contributors to Keploy will provide an overview of its features and capabilities, and how it is used at scale covering use-cases across microservices across various programming languages.

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

An API is no different than any other product. You need to help traditional business management understand the relevance of the API program. Let's understand the importance of treating your APIs as products and how to demonstrate that business value. Then, we'll walk through the concrete steps to integrate this process into your API strategy and the key components needed to successfully scale.

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

Achieving a productive workflow for API development under Kubernetes is a challenge, especially for developers who are new to Kubernetes and related constructs like manifests, Ingress controllers, GitOps, etc. Adopting an OpenAPI-centric approach to API development can bring many benefits in this regard; the metadata contained in OpenAPI can be used to automate many of the tasks related to building and deploying APIs to Kubernetes - both in manual and CI/CD workflows - helping your team to keep up the pace while transitioning to Kubernetes.

This talk will show you how to leverage OpenAPI to accelerate your API development workflow for Kubernetes. Both design-first and code-first approaches are covered, with both manual and automated CI/CD/GitOps processes.

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

URI Templates are a popular standard that allows clients to construct a URI according to the server's instructions, rather than following a hyperlink, or implementing manually-written directions in the documentation.

Wouldn't it be useful if you could use these same URI templates to handle incoming HTTP requests? I will show how to reverse this process, so that when a request is received, the URI can be routed to a matching URI Template, from among all of the ones used in the API; recovering the values used to fill in the variables.

I'll show applications for this technique, including a router that reads directly from an OpenAPI description, and detecting overlapping or ambiguous routes.

And I will show the basis in Automata Theory, starting by modeling URI Templates as a regular grammar, then taking the union of all of the URI Templates in use to produce a deterministic finite state machine to find the ones that match (in constant time, with respect to the size of the routing table!).

Finally, I'll discuss implications for various API description standards, including how to support nearly the full range of URI Template operators, and what it should mean when there's overlapping routes.

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

To mash up various APIs you need data to have a well defined meaning: imagine meshing up healthcare APIs using different units for human temperature, or financial APIs using different currencies.

This talk describes a strategy for creating semantically interoperable REST APIs based on including semantic information inside OpenAPI documents, after analyzing
[different alternatives](https://docs.google.com/document/d/1fBRH2wtg1p_g4voNSTlHiSJmKgvfNaIsUXwPBO36RuM/edit).

Basic knowledge of semantic web and JSON-LD is required.

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

Generating SDKs and Code Samples from API specifications is a common practice among API providers. The generated code is considered as a wrapper over the API specification, and often lack the depth of a production-quality code. On the other hand, some hand-written SDKs offer quality code and valuable features such as time-outs, caching and retries. However, manual SDKs are hard to maintain, so the debate over auto-generated vs manual ones continues.

In this talk, I will be covering the developer requirements for idiomatic and production-ready code, and how can those requirements be made part of an API specification. For SDKs or client libraries, my focus would be taking them beyond API-wrappers by adding the layers of developer experience, both for API consumers and providers. At the end, I will elucidate the limitations of the specs-generated code samples, and a few thoughts to make them usable in production.  

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
Watch the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!

---------------------------------------------------------------------------------------------------------------------------------------------------

JSON Schema plays a crucial role of defining message payloads in the OpenAPI and AsyncAPI specifications. The JSON Schema specification is a very mature and robust standard for describing how to validate a JSON payload. It is a sharp sword, precise and well-honed to that job.

But the other edge of that sword may also draw blood when applied as a data modeling language. What works beautifully for validation can cause code generation nightmares for marshaling request and response JSON into native programming language constructs such as interfaces, types, classes, and prototypes. This is the result of using the JSON Schema standard for two different purposes in the API specifications – killing two birds with one sword, to butcher a metaphor or two.

In this talk, I'll discuss techniques for using a subset of JSON Schema effectively in API design. Next, we'll provide guidance on protecting yourself and your API from the perils of the more intricate aspects of JSON Schema that make consuming the API and coding API services and clients so... perilous. Finally, you will learn of efforts to define JSON Schema vocabularies and API specification changes to enable "better" tool-generated client and service code.

Virtual Track sessions will be available on-demand on the OpenAPI Initiative YouTube channel at 9:00 AM PT on Monday, September 19. View the sessions here and watch your favorites before joining the Speaker Q&A session on the OpenAPI Initiative Slack workspace at 12:00 PM PT.
View the Sessions
Join the OAI Slack Workspace
Once you’ve joined Slack, join the #asc2022_virtual-track channel. A thread will be created for each talk where speakers and attendees can discuss the content. Please note that not all virtual speakers are able to participate in the Q&A session, but please keep the conversation going with fellow viewers!