You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the observations made at the April 2023 code sprint was that there is a need to identify a media type for AsyncAPI.
Consider the following fragment from the links in a landing page, for instance. The only way to distinguish between links to the OpenAPI and AsyncAPI definition documents is through the type property. The media type application/json however is too general and would likely need disambiguation in the future if another JSON-encoded API definition language came along. Is anyone aware of alternative options for media types for representing AsyncAPI definition documents?
{
"rel": "service-desc",
"type": "application/vnd.oai.openapi+json;version=3.0",
"title": "The OpenAPI definition as JSON",
"href": "http://localhost:5000/openapi"
},
{
"rel": "service-desc",
"type": "application/json",
"title": "AsyncAPI document in JSON",
"href": "http://localhost:5000/asyncapi"
},
The text was updated successfully, but these errors were encountered:
One of the observations made at the April 2023 code sprint was that there is a need to identify a media type for AsyncAPI.
Consider the following fragment from the links in a landing page, for instance. The only way to distinguish between links to the OpenAPI and AsyncAPI definition documents is through the
type
property. The media typeapplication/json
however is too general and would likely need disambiguation in the future if another JSON-encoded API definition language came along. Is anyone aware of alternative options for media types for representing AsyncAPI definition documents?The text was updated successfully, but these errors were encountered: