Linked Data Rights (LDR)


Title
Linked Data Rights (LDR)
URI
http://purl.oclc.org/NET/ldr/ns
Description
The Linked Data Rights ontology provides the vocabulary for creating rights expressions for Linked Data resources by extending the ODRL ontology. Linked Data assets (RDF triples, graphs, datasets, mappings...) can be object of protection by the intellectual property law, the database law or its access or publication be restricted by other legal reasons (personal data pro- tection, security reasons, etc.). Publishing a rights expression along with the digital asset, allows the rightsholder waiving some or all of the IP and database rights (leaving the work in the public domain), permitting some operations if certain conditions are satisfied (like giving attribution to the author) or simply reminding the audience that some rights are reserved. Specific vocabulary is given for authorising specific uses of Linked Data.
License
Creative Commons CC-BY
Languages
en
LOV page
See the entry for ldr in LOV

The following evaluation results have been generated by the RESTFul web service provided by OOPS! (OntOlogy Pitfall Scanner!). OOPS! is a software on development, and we will be happy to receive your feedbak. If you notice any issue in the evaluation, please contact us at oops@delicias.dia.fi.upm.es.

OOPS! logoIt is obvious that not all the pitfalls are equally important; their impact in the ontology will depend on multiple factors. For this reason, each pitfall has an importance level attached indicating how important it is. We have identified three levels:

Critical
It is crucial to correct the pitfall. Otherwise, it could affect the ontology consistency, reasoning, applicability, etc.
Important
Though not critical for ontology function, it is important to correct this type of pitfall.
Minor
It is not really a problem, but by correcting it we will make the ontology nicer.

Evaluation results

P04. Creating unconnected ontology elements2 cases detected. Minor

Ontology elements (classes, object properties and datatype properties) are created isolated, with no relation to the rest of the ontology.

This pitfall affects to the following ontology elements:

P08. Missing annotations47 cases detected. Minor

This pitfall consists in creating an ontology element and failing to provide human readable annotations attached to it. Consequently, ontology elements lack annotation properties that label them (e.g. rdfs:label, lemon:LexicalEntry, skos:prefLabel or skos:altLabel) or that define them (e.g. rdfs:comment or dc:description). This pitfall is related to the guidelines provided in [5].

This pitfall affects to the following ontology elements:

P10. Missing disjointness ontology *Important

The ontology lacks disjoint axioms between classes or between properties that should be defined as disjoint. This pitfall is related with the guidelines provided in [6], [2] and [7].

*This pitfall applies to the ontology in general instead of specific elements

P11. Missing domain or range in properties11 cases detected. Important

P13. Inverse relationships not explicitly declared4 cases detected. Minor

This pitfall appears when any relationship (except for those that are defined as symmetric properties using owl:SymmetricProperty) does not have an inverse relationship (owl:inverseOf) defined within the ontology.

This pitfall affects to the following ontology elements:

P34. Untyped class1 case detected. Important

An ontology element is used as a class without having been explicitly declared as such using the primitives owl:Class or rdfs:Class. This pitfall is related with the common problems listed in [8].

This pitfall affects to the following ontology elements:

P40. Namespace hijacking1 case detected. Critical

It refers to reusing or referring to terms from another namespace that are not defined in such namespace. This is an undesirable situation as no information can be retrieved when looking up those undefined terms. This pitfall is related to the Linked Data publishing guidelines provided in [11]: "Only define new terms in a namespace that you control" and to the guidelines provided in [5].

This pitfall affects to the following ontology elements:


References: