search

isa-camss / CAV

The Core Assessment Vocabulary represents 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 type of assets.
3 stars 1 forks source link

Replace the ADMS Asset (DCAT Dataset) with W3C DCAT Resource #5

Open paulakeen opened 3 years ago

paulakeen commented 3 years ago

Both ADMS-AP and DCAT-AP are currently Application Profiles of W3C DCAT.

In the current CAV model, we are saying that the Assessment 'is an asset' (an ADMS Dataset). The intention was to have a kind of 'abstract' asset class that links the CAV to other vocabularies that also use the idea of 'asset' (such as CSSV, CCCEV, different flavours of DCAT, etc.).

Proposal: Use the latest W3C DCAT 'Resource' class (instead of Dataset) as the base class for Assessment. Since the W3C DCAT Dataset 'isA' 'dcat:Resource' the axiom 'an assessment is a dataset' would still hold.

Important Note: This approach should make reflect the CSSV Working Group on the convenient of proceed similarly to make the 'cssv:Specification' class inherit from 'dcat:Resource'.

Reactions will be appreciated, thank you!

costas80 commented 3 years ago

This sounds good as it would make the CAV more generic. We would need to ensure however that other dependencies are catered for (e.g. distributions).

paulakeen commented 3 years ago

Considerations on the use of dcat:Resource:

  1. Fortunately, the important set of attributes needed by the CAV and other Core Vocabularies (e.g. the CSSV) are in the class dcat:Resource (e.g. creator, rights, type, title, description, etc.);

  2. About the access to the class "dcat:Distribution":

    • In the case of Summaries and Reports, we alredy use the class dcat:Distribution directly without going through the dcat:Dataset (via the properties cav:hasSummary and cav:hasReport:

image

  • Situation 1: What does cav:Assessment assesses, dcat:Resources or dcat:Datasets? We propose that CAV assesses "dcat:Resources". This opens many doors: any instantiation of dcat:Dataset and dcat:Dataservice could then be assessed. Alternatively, the dcat:landingPage can be used to gather more information about how to access the asset to be assessed.

  • Situation 2: Should cav:Assessment be a subclass of dcat:Resource or of dcat:Dataset? We propose that cav:Assessment subclasses dcat:Resource. This way any type of resource can be assessed (e.g. cssv:Specification(s), amongst other).

jseguraf commented 3 years ago

Another alternative, which we start liking very much, is using the W3C adms:Asset. If the "interface" class between vocabularies is an asset, everything makes sense for us.

jseguraf commented 3 years ago

The WG suggests analysing two other works the PROV ontology and dolce ultra light - lightweight foundational ontology

jseguraf commented 3 years ago

This would analysed in the very next release of the CAV since the public review about the current one is already closed.