cmd | <https://w3id.org/cmd#> |
dqv | <http://www.w3.org/ns/dqv#> |
schema | <http://schema.org/> |
skos | <http://www.w3.org/2004/02/skos/core#> |
The core component of the CMD vocabulary is illustrated in Figure 1. Hence, a TSoR consists of a set of AnalysisElements and Requirements that form a tree structure. The elements of the tree are linked by the relations isSpecifiedBy and expects. In addition, they are associated with a content (name, description...) through the relation hasContent. The content of an analysis element is of type skos:Concept, and a requirement is intended to measure a specific aspect, therefore its content is of type dqv:Metric. Note that analysis elements and requirements can only structure a single TSoR. However, their contents, concepts or metrics, can appear in multiple TSoRs. The cardinalities, shown in gray in Figure 1, ensure that the TSoR is properly designed.
Additional information can be added to the structure to make it a fully defined measure. Therefore, an Implementation is linked to a requirement to indicate how to evaluate them, with isImplementedBy. Each requirement and analysis element has a weight that represents its relative importance compared to its siblings in the tree. An aggregation function (aggregFunction) is associated with a TSoR and indicates how to compute an overall score based on results obtained on each requirement and on the weights of the structural elements. Other information can be added to enhance the transparency of the TSoR thus defined, such as creators, creation and modification dates, etc.Figure 2 shows a small example of a TSoR that represents a part of the FAIR-Checker measure: it considers only the "A1.1" sub-principles. Another example representing a measure of accountability, as described here, is available in RDF.
SHACL shapes are defined to ensure that the TSoR defined with the vocabulary is well-formed, i.e. it actually forms a tree structure. It also checks that the TSoR satisfies the cardinalities and some other recommendations.
This ontology has the following classes and properties.
IRI: https://w3id.org/cmd#AnalysisElement
IRI: https://w3id.org/cmd#Implementation
IRI: https://w3id.org/cmd#Requirement
IRI: https://w3id.org/cmd#TSoR
IRI: https://w3id.org/cmd#expects
IRI: https://w3id.org/cmd#hasRoot
IRI: https://w3id.org/cmd#hasContent
IRI: https://w3id.org/cmd#isFollowedBy
IRI: https://w3id.org/cmd#isImplementedBy
IRI: https://w3id.org/cmd#isSpecifiedBy
IRI: https://w3id.org/cmd#aggregFunction
IRI: https://w3id.org/cmd#weight
This work is supported by the ANR DeKaloG (Decentralized Knowledge Graphs) project, ANR-19-CE23-0014, CE23 - Intelligence artificielle.
The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.