Create application_vnd.openminds.schema+json.jsonld

[lzehl]

We may also want to create one for the schema templates (TBD).

Not sure how to handle versioning here. The syntax should be separately versioned (if we would define it as a schema format). From now to the start we had at least one version increase, from the old to the new pipeline (where we separated fully build schemas from schema templates more clearly through different file extensions).

@apdavison @olinux what do you think? (one review is sufficient I think)

[apdavison]

"JSON-Schema inspired schema syntax"

How is the syntax different from pure JSON-Schema? I'm unclear on this point.

[lzehl]

The openMINDS schema syntax is not the same as JSON-Schema. In several aspects. We introduced multiple attributes that JSON-Schema does not know and does not interpret. If someone would provide a full valid JSON-Schema it would fail our pipeline (maybe not the simple schemas but the complex ones for sure).

[lzehl]

@openMetadataInitiative/openminds-developers please provide your opinion :grin:

[lzehl]

@apdavison @olinux @openMetadataInitiative/openminds-developers I've updated this PR according to the namespace change, updated the instance and bit and added an instance for the openMINDS schema template as well. Before I populate across versions, please provide your feedback/approval for these changes.

[apdavison]

I think we should use "openmetadatainitiative" rather than "om-i". Other than that, it looks fine.

[lzehl]

I think we should use "openmetadatainitiative" rather than "om-i". Other than that, it looks fine.

@apdavison done; I'll populate now across versions and then retrigger your review