-
-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
define formal media type (MIME type) for AsyncAPI Object #936
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
Awesome! Do you know what the process looks like? I honestly never did anything similar. |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
It looks like there is an application form at https://www.iana.org/form/media-types. Having said this, it would be valuable to:
cc @ghobona |
@fmvilas OGC is looking into using AsyncAPI in support of OGC API Standards. It would be helpful if the AsyncAPI Initiative either registered a media type for AsyncAPI definition documents at IANA, or specified a media type for AsyncAPI definition documents in the AsyncAPI specification. Are you aware of any discussions, within the AsyncAPI initiative, towards specifying and registering a media type for AsyncAPI definition documents? |
Somewhat related: The IETF HTTP API WG is working on an Internet-Draft for media types for JSON Schema and OpenAPI (JSON and YAML): https://ietf-wg-httpapi.github.io/mediatypes/draft-ietf-httpapi-rest-api-mediatypes.html. |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
At this point it looks like |
Sorry I missed lots of comments here somehow. I think |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
In the spirit of OAI/OpenAPI-Specification#110, it would be valuable to have a similar effort here in AsyncAPI for IANA considerations (https://datatracker.ietf.org/doc/html/draft-polli-rest-api-mediatypes#name-iana-considerations).
Ref: opengeospatial/ogcapi-common#329
The text was updated successfully, but these errors were encountered: