Open frankkilcommins opened 1 year ago
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 vnd.
prefix so workflows are aligned with the OAS media type registrations. Was that resolved, and if so is there an rationale I can read somewhere?
@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.