-
Notifications
You must be signed in to change notification settings - Fork 46
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
Register Workflows Media Types #71
Comments
Registrations filed:
|
Shouldn't this be coordinated with the existing draft RFC to register the main OAS media types? |
I don't know if it needs to be coordinated with the existing RFC (which I've only recently found). This has followed the existing IANA registration process. It would be nice if eventually it ends up in the RFC but I don't see one blocking the other in any way. @darrelmiller is anyway the expert reviewer for the media types registry so he's in the loop and aware of both 😉 |
The registration of Media Types for the Workflows Specification with IANA has been completed. Registrations: The specification was updated to support the registration process with the addition of: |
ToDo: define fragment identifier considerations and update registrations |
@frankkilcommins I recall some conversation (but have forgotten where it was) about not using the |
@handrews I had a chat with @darrelmiller on this and the thought process is to wait until there's a clear process in place for supporting "Community Specifications". This process will likely be trashed out as part of the OAS media type registrations. Once done we can then make a request to add a new media type for Workflows and at that point we'll decide if we want to mark the vnd one as deprecated. |
@frankkilcommins thanks so much for the explanation! That makes sense to me. |
Ideally we should have a media types for workflows so that they can be exposed as proper resources.
Once registered etc., we should add the relevant information to the specification.
The text was updated successfully, but these errors were encountered: