Mappings between JSON-LD context and RDF vocs - and documentation

Open aisaac opened this issue 5 years ago • 2 comments

I'm wondering where changes in the mappings between context and RDF vocabularies between v2 and v3 have been documented. I.e. profile is now dcterms:conformsTo instead of doap:implements, protocol is now dcterms:type instead of dcterms:conformsTo and service is schema:potentialAction instead of svcs:has_service. Maybe there are others?

Why the last one, by the way? This doesn't feel right at first sight. In https://github.com/IIIF/api/pull/1722 I didn't find a reference to this property. The type Service is mapped to schema:WebAPI, which is not really a schema:Action. Or am I misreading the JSON in the context files? Well, having this documented in the change log may fix my wrong interpretation then ;-)

Feb 19 '20 22:02 aisaac

They're not documented, because the context files aren't part of the normative specification.

I think this is a process issue that should be discussed and resolved - documentation of the ontology and profile for the predicates. Probably in /annex/ ?

Apr 13 '20 18:04 azaroth42

An annex would sound good!

Apr 13 '20 19:04 aisaac

Editors agree - not going to document non-semantically-versioned changes as there's nowhere useful to put them, and the number of people who would use that document is likely under 5.

Jun 07 '24 21:06 azaroth42