Have alternative options for label and description when creating a new vocabulary

[dpancic]

In GitLab by @KlausIllmayer on Jun 18, 2021, 14:32

Currently, when creating a new vocabulary the label is taken from the rdfs:label-triple and the description is expected in the rdfs:comment-triple (see https://gitlab.gwdg.de/sshoc/sshoc-marketplace-backend/-/blob/develop/src/main/java/eu/sshopencloud/marketplace/services/vocabularies/rdf/RDFModelParser.java#L41)

But we often have vocabularies that do not hold an rdfs:label or an rdfs:comment-triple. Instead it is very common to use dublin-core-relations to describe a vocabulary.

• for label: http://purl.org/dc/elements/1.1/title (= dc:title) and/or http://purl.org/dc/terms/title (= dct:title)
• for description: http://purl.org/dc/elements/1.1/description (= dc:description)

As I like to prevent adding triples by hand, it would be great if you could implement this alternative options for holding information on label/description. The order could be:

• for label: rdfs:label => dc:title => dct:title
• for description: rdfs:comment => dc:description

[dpancic]

In GitLab by @tparkola on Jun 24, 2021, 14:05

Done with priorities

• for label: rdfs:label => dc:title => dct:title
• for description: rdfs:comment => dc:description

and English labels and descriptions have priority over other languages.