Output classifications as SKOS

Implementation of a SKOS-Export for REST-API v2

I used the following paper with examples to refresh my knowledge:
https://epubs.stfc.ac.uk/manifestation/685/SKOS-XTech2005.pdf

Implementation itself is straightforward

• used MCRCategory Java implementation and JDOM

• registered mime-type application/rdf+xml + extension .rdf within REST api

We need to discuss the URI-Concept for our classifications:

• Where does it come from?

  • URI-Attribute in category

  • x-uri Label

  • http://mycore.org/classifications/classid#categid

  • http://my-application.my-instititution.de/classifications/classid#categid

• the combination of all of them

  • What happens if categories provide own URIs via x-uri-Label or uri-Attribute?

  • baseURI from classification, ID from categories?

• Do we want to / How to link between Concepts / URIs?

  • via skos:exactMatch or owl:sameAs or xxx:yyyy ?

  • Links between classification-URIs in my repository (my base URL) to http://mycore.org?

  • resolve links between our classifications via x-mapping label?

• The URI itself (as link) should be resolvable and return (via Content-Negotiation / Accept-Header) the RDF-XML for the classification OR category.

  • http://localhost:8880/rosdok/api/v2/classifications/doctype

  • http://localhost:8880/rosdok/api/v2/classifications/doctype/epub.monograph

  • Attention: For categories we currently return all parent categories and the classification root
    (technically there is not problem (only “to much information”), but is this the intendented behaviour for the RDF-Response?)

  • Do we need an object type vocabulary (Classification, Category, MyCoReObject, MyCoRe-Derivate, User, …)
    (URI for rdf:type)