Slot: license

The license of the ontology/vocabulary. Ontologies and SKOS vocabularies should refer to license documents on the web via PIDs. The license text helps others to evaluate how they may reuse the ontology/vocabulary. Only ontologies with an open license will be published on the TIB Terminology Service.

This metadatum is also recommended as required by:

• https://github.com/information-artifact-ontology/ontology-metadata/pull/106#issuecomment-1117383852
• http://purl.obolibrary.org/meta/context.jsonld
• https://w3id.org/mod/2.0
• https://lov.linkeddata.es/Recommendations_Vocabulary_Design.pdf
• https://dgarijo.github.io/Widoco/doc/bestPractices/index-en.html
• https://doi.org/10.1371/journal.pcbi.1009041
• http://ceur-ws.org/Vol-3127/#paper-15
• Best Practices for Implementing FAIR Vocabularies and Ontologies on the Web

URI: dcterms:license

Applicable Classes

Name	Description
RequiredMetadata	A mixin that provides the required properties needed to index an ontology or ...
Ontology	An OWL ontology
SkosConceptScheme	A SKOS vocabulary serialized in RDF using the skos:ConceptScheme

Properties

• Range: Uriorcurie
• Required: True

Comments

• For the RDF implementation, we recommend using the URI provided here as a standard, but the URI(s) listed under See Also might be used as alternative for this predicate.

TODOs

• We should point to types of different licenses and give recommendations on which to choose when.

See Also

• http://purl.org/dc/terms/rights
• http://purl.org/dc/elements/1.1/rights
• http://creativecommons.org/ns#license
• http://dbpedia.org/ontology/license

LinkML Source

name: license
description: "The license of the ontology/vocabulary. Ontologies and SKOS vocabularies\
  \ should refer to license documents on the web via PIDs. The license text helps\
  \ others to evaluate how they may reuse the ontology/vocabulary.\nOnly ontologies\
  \ with an open license will be published on the TIB Terminology Service.\n\nThis\
  \ metadatum is also recommended as required by:\n\n  * https://github.com/information-artifact-ontology/ontology-metadata/pull/106#issuecomment-1117383852\n\
  \  * http://purl.obolibrary.org/meta/context.jsonld\n  * https://w3id.org/mod/2.0\n\
  \  * https://lov.linkeddata.es/Recommendations_Vocabulary_Design.pdf\n  * https://dgarijo.github.io/Widoco/doc/bestPractices/index-en.html\n\
  \  * https://doi.org/10.1371/journal.pcbi.1009041\n  * http://ceur-ws.org/Vol-3127/#paper-15\
  \ \n  * [Best Practices for Implementing FAIR Vocabularies and Ontologies on the\
  \ Web ](http://dgarijo.com/papers/best_practices2020.pdf)\n"
todos:
- We should point to types of different licenses and give recommendations on which
  to choose when.
comments:
- For the RDF implementation, we recommend using the URI provided here as a standard,
  but the URI(s) listed under **See Also** might be used as alternative for this predicate.
from_schema: http://terminology.tib.eu/schema
see_also:
- http://purl.org/dc/terms/rights
- http://purl.org/dc/elements/1.1/rights
- http://creativecommons.org/ns#license
- http://dbpedia.org/ontology/license
rank: 1000
slot_uri: dcterms:license
alias: license
domain_of:
- RequiredMetadata
range: uriorcurie
required: true