Ben Hutton

Agreed. I think we're no longer looking to solve this as a part of the MME API itself, but provide a documented solution that we can suggest or reccomend, but...

I'm not sure point 1 is relevant any longer. I mean, even if the reciving system knows it has an older version, it won't know which items from the ontology...

I guess it's possible that there could be "additional notes" which have a human readable text which explains any transcoding or changes made to the incoming request data. I think...

It could be useful to create a summary of this issue and add that to the first or second post.

Decipher has both public (consented) and non public data, but the data that isn't consented is considered only in holding to be made public in the event consent is sought...

@derberg has been working on an approach to copy sets of files (like GH Actions) to mutliple repositires within an org. I thought I'd mention it in case he has...

I don't know what the differences are! I was hoping as an implementer, you might 😅

> think the living standard one can change over time so it could always be out of date. That's... a really good point. Compliant today, out of date tomorrow 😞....

The answer is... Yes. > The unversioned meta-schema URIs should no longer be used. https://github.com/json-schema-org/json-schema-org.github.io/blob/66969467feb494dcc02247a431a1905a6f283baf/_layouts/redirect.html#L13 The most recent draft is now 2020-12. The URIs are for determining the appropriate draft...