Path to standardisation! #3
Replies: 4 comments 1 reply
-
A discussion relating to the option to self publish: #69 |
Beta Was this translation helpful? Give feedback.
-
Discussion of publishing a specification with the purpose of moving it out of "draft" status an into an initial state of stability: #282 |
Beta Was this translation helpful? Give feedback.
-
Hi! There are several SMPTE (www.smpte.org) Standards projects that need a standardized JSON Schema Language. Most notable is SMPTE ST2135 RegJSON whose goal is a canonical isomorphic mapping between JSON and SMPTE ST336 KLV (binary) Encoding. KLV is the underpinnings of SMPTE ST377 MXF which is the predominant format for professional media files. I am the Editor of ST2135 RegJSON. Previously I was the author of KLV and the creator of MXF and chaired the committees that brought all these Standards to publication. My long time colleague Bruce Devlin is the chair of the RegJSON project. In an ideal world, ST2135 RegJSON would be able to normatively reference an RFC or a W3C specification based on your excellent work. If that is not your path, we have also contemplated if it would be possible to publish your work in our proposed Standard. Please forgive my newness to json-schema.org and help me to address my questions to the right people in the right forums (here? slack? direct email? voice?) best regards |
Beta Was this translation helpful? Give feedback.
-
Ben: Thanks for your prompt reply. That said, it might be possible to count LF as such. I can ask SMPTE ST.
I completely understand that the SDO process is consuming and distracts from work towards tangible projects. So it needs a dedicated resource.
thanks |
Beta Was this translation helpful? Give feedback.
-
How? When? Where?
These are questions that have been asked about JSON Schema and standardisation many times.
We now want to assess possible directions.
There have been some really great discussions, and I want to link to as many as possible from here.
I'll also be creating a new discussion to track specific possible paths.
It's worth noting that joining a foundation as a project does not prohibit us publishing the specification to any specific standards organisation if we choose to do so. In this I mean, if we choose to join the OpenJS Foundation, we aren't prohibited from still publishing specification documents through the IETF.
I'll try to keep this top post updated with the current status, as well as posting the same content as follow up comments.
Beta Was this translation helpful? Give feedback.
All reactions