What values are intended to be used for `omexManifest/content@format`?

sys-bio / libOmexMeta

libOmexMeta is a library aimed at providing developer-level support for reading, writing, editing and managing semantic annotations for biosimulation models.

https://sys-bio.github.io/libOmexMeta/

Apache License 2.0

8 stars 6 forks source link

What values are intended to be used for `omexManifest/content@format`? #99

Open jonrkarr opened 3 years ago

jonrkarr commented 3 years ago

How is this intended to work with OMEX Metadata stored in the various supported formats (RDF-XML, turtle, etc)?

CiaranWelsh commented 3 years ago

Prodding @jhgennari @nickerso for some help with this one.

nickerso commented 3 years ago

Great question. I think we should just be using the appropriate media type for the given serialisation. Some examples:

Turtle: text/turtle
N-Triples: application/n-triples
RDF/XML: application/rdf+xml
JSON-LD: application/ld+json

Although we had at one point thought about using the generic OMEX Metadata format and letting tools determine themselves the actual serialisation format, and that then allows tools to detect "OMEX Metadata" compliant annotations from the manifest...but not sure how useful that actually is.

jonrkarr commented 3 years ago

I agree with David about using the real media types.

Given that OMEX Metadata is trending toward specific conventions beyond the various serializations, I think it would be helpful for the format to capture that files are OMEX Metadata files rather than other triple files,

Something like

text/omexmetadata-turtle
application/omexmetadata+rdf+xml

OR something like

http://identifiers.org/combine.specifications/omex-metadata.turtle
http://identifiers.org/combine.specifications/omex-metadata.n-triples