Skip to content

Use of datacite:hasIdentifier #20

Description

@vroddon

I have created an real example that follows the metashare ontology, so you could see what is the correct structure and vocabulary using the metashare ontology, how we have designed it. The example is the CC-BY-4.0 licence (see attachment). I know that unfortunately all this information cannot derive directly from the metashare xml records, we need to design an extra mapping.

<http://nlpli.ilsp.gr/example/data/> a owl:Ontology;
  owl:imports datacite:2018-01-20, ms:2.0.0, <http://w3id.org/meta-share/omtd-share/> .

:cc0 a ms:LicenceTerms;
  datacite:hasIdentifier :cc_by_40_id;
  ms:conditionOfUse ms:attribution;
  ms:licenceCategory ms:allowsDirectAccess, ms:allowsProcessing;
  ms:licenceTermsAlternativeName "CC-BY-4.0"@en;
  ms:licenceTermsName "Creative Commons Attribution 4.0 International"@en;
  ms:licenceTermsShortName "CC-BY-4.0"@en;
  ms:licenceTermsURL "https://creativecommons.org/licenses/by/4.0/"^^xsd:anyURI, "https://creativecommons.org/licenses/by/4.0/legalcode"^^xsd:anyURI;
  rdfs:label "CC-BY-4.0"@en .

:cc_by_40_id a ms:LicenceIdentifier;
  datacite:usesIdentifierScheme ms:SPDX;
  literal:hasLiteralValue "CC-BY-4.0";
  rdfs:label "CC-BY-4.0 id"@en .

As you could see in the example the relation between a LicenceTerms and its identifier is represented using the datacite:hasIdentifier property and following datacite suggestions we use the property literal:hasLiteralValue to declare the actual value. Though, we are not sure if this is the right approach. We know that it is good as we reuse existing vocabulary, but both vocabularies are not maintained and more importantly are not dereferencable and one needs to manuall search in order to find them. Do you think that this is the right way to approach the issue? Do you think that literal:hasLiteralValue has the correct semantics for our case?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions