The Core Assessment Vocabulary represents, expresses, and defines what an “Assessment” of “Assets” is and how to perform the assessment based on “Criteria”. It is a domain-agnostic vocabulary, meaning that it can be used to assess any asset. The CAV addresses semantic interoperability by reusing existing generic ontologies and vocabularies. This way, the semantics of common concepts and properties are agreed without having to re-discuss them. When concepts or properties have not been identified nor defined for the purposes pursued, they have to be proposed either as extensions or from scratch.
The methodological approach followed for the development of the CAV reuses the following ontologies and vocabularies:
adms | <http://www.w3.org/ns/adms#> |
cav | <http://data.europa.eu/2sa/cav#> |
cc | <http://creativecommons.org/ns#> |
cv | <https://data.europa.eu/m8g/> |
dc | <http://www.omg.org/spec/UML/20131001/UMLDC> |
dcat | <http://www.w3.org/ns/dcat#> |
dct | <http://purl.org/dc/terms/> |
foaf | <http://xmlns.com/foaf/0.1/> |
org | <http://www.w3.org/ns/org#> |
owl | <http://www.w3.org/2002/07/owl#> |
rdf | <http://www.w3.org/1999/02/22-rdf-syntax-ns#> |
rdfs | <http://www.w3.org/2000/01/rdf-schema#> |
sch | <https://schema.org/> |
skos | <http://www.w3.org/2004/02/skos/core#> |
vann | <http://purl.org/vocab/vann/> |
xml | <http://www.w3.org/XML/1998/namespace> |
xsd | <http://www.w3.org/2001/XMLSchema#> |
A CAV Assessment is a specialization of an Asset, which is itself also a specialization of the dcat:Dataset
and, by extension, of dcat:Resource
. As any adms:Asset
, the Assessment can be identified and described, and has individuals' distributions, publishers, etc. Additionally, to these properties, the cav:Assessment
needs to specify who are the requestors and evaluators of the Assessments. These can be anything represented by a foaf:Agent
, such as a natural person, a group, or an organization. Notice that the objects assessed are also Resources, meaning that the CAV may be used to assess anything that is considered a valuable resource. Examples of such resources could be products, services, or, in the case of CAMSS, standards and specifications.
An Assessment results in Statements capturing the produced knowledge and providing value judgments. These can refer to the Assessment as a whole or a specific section, even being as detailed as to refer to individual evaluated criteria.
A cv:Criterion
is typically derived from a Reference Framework, which is to be understood as a series of “agreed and descriptive reference requirements” coming from one or more sources (e.g., legislation, specifications and standards, ICT policy-related works like the EIF within the EIS, etc.). Throughout the Assessment, each cv:Criterion
is assigned a cav:Score
(in principle by humans, but potentially also by systems) as the value output that is considered when formulating the resulting Statement(s). The cav:Score
can take into consideration any resource input (e.g., when the score is calculated based on different input parameters, algorithms, and formulae).
Any Assessment is performed in the context of a cav:Scenario
. The Scenario defines the purpose of the Assessment and the set of Criteria to be scored by one or more Agents. Scenarios can be defined with a flexible structure, including nested sections (represented as sub-Scenarios) that serve to provide additional context, group thematically Criteria, and be referred to by the assessment’s resulting Statement(s). Criteria can themselves be simple or complex and originate from various reference sources. The overall context for the evaluation of the Criteria is provided by the Scenario; however, in case certain Criteria require additional contextualization or evaluation instructions, these can exceptionally be provided by means of an cav:EvaluationContext
, which is related to a resource. Moreover, an Assessment might trigger another related Assessment of different content, which has its own Scenario and Criteria.
Finally, an Assessment has a dct:title
and a dct:description
to facilitate the identification of the Asset. Note that it is also possible to model work in progress, expressed by having the Assessment define optional links to Scores, Statements, reports, and summaries. The versioning of an Assessment is represented by the dcat:version
to keep track of the current version of the Assessment and its relationship with a previous one; setting up the dct:issued
(assessment performance date) and the dcat:releaseDate
(assessment publication date) of the Assessment is also recommended, where the CAV reuses the dct:issued
(date) property for both.
IRI: http://data.europa.eu/2sa/cav#Assessment
IRI: http://data.europa.eu/2sa/cav#Asset
IRI: http://www.w3.org/ns/dcat#Dataset
IRI: http://data.europa.eu/2sa/cav#EvaluationContext
IRI: http://data.europa.eu/2sa/cav#Scenario
IRI: http://data.europa.eu/2sa/cav#Score
IRI: http://data.europa.eu/2sa/cav#Statement
IRI: http://data.europa.eu/2sa/cav#assesses
IRI: http://data.europa.eu/2sa/cav#assignedTo
IRI: http://data.europa.eu/2sa/cav#basedOn
IRI: http://data.europa.eu/2sa/cav#considers
IRI: https://schema.org/contactPoint
IRI: http://data.europa.eu/2sa/cav#contextualisedBy
IRI: http://data.europa.eu/2sa/cav#contextualises
IRI: http://data.europa.eu/2sa/cav#definedBy
IRI: http://data.europa.eu/2sa/cav#defines
IRI: http://data.europa.eu/2sa/cav#definesSub
IRI: http://www.w3.org/ns/dcat#distribution
IRI: http://data.europa.eu/2sa/cav#documentedIn
IRI: http://data.europa.eu/2sa/cav#formulatedBy
IRI: http://data.europa.eu/2sa/cav#hasInput
IRI: http://data.europa.eu/2sa/cav#hasReport
IRI: http://data.europa.eu/2sa/cav#hasSummary
IRI: http://data.europa.eu/2sa/cav#includes
IRI: http://data.europa.eu/2sa/cav#performedBy
IRI: http://www.w3.org/ns/dcat#previousVersion
IRI: http://data.europa.eu/2sa/cav#providedBy
IRI: http://data.europa.eu/2sa/cav#providesScore
IRI: http://data.europa.eu/2sa/cav#refersTo
IRI: http://data.europa.eu/2sa/cav#relatesTo
IRI: http://data.europa.eu/2sa/cav#requestedBy
IRI: http://data.europa.eu/2sa/cav#resultsIn
IRI: http://data.europa.eu/2sa/cav#triggeredFrom
IRI: http://data.europa.eu/2sa/cav#triggers
IRI: http://purl.org/dc/terms/description
IRI: http://data.europa.eu/2sa/cav#instructionDescription
IRI: http://data.europa.eu/2sa/cav#interpretation
IRI: http://purl.org/dc/terms/issued
IRI: http://data.europa.eu/2sa/cav#judgement
IRI: http://data.europa.eu/2sa/cav#purpose
IRI: http://www.w3.org/ns/dcat#releaseDate
IRI: http://www.w3.org/ns/adms#status
IRI: http://purl.org/dc/terms/title
IRI: http://data.europa.eu/2sa/cav#type
IRI: http://data.europa.eu/2sa/cav#value
IRI: http://data.europa.eu/2sa/cav#valueDescription
IRI: http://www.w3.org/ns/dcat#version
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.