Open sskagemo opened 5 years ago
Input from Tore, consider ADMS: "Asset is a profile of DCAT [ DCAT ] for describing so-called Semantic Assets(or just 'Assets'), that is, highly reusable metadata (e.g. xml schemata, generic data models) and reference data (e.g. code lists, taxonomies, dictionaries, vocabularies) that are used for eGovernment system development [ TOGD ], https://www.w3.org/TR/vocab-adms/#skos-altlabel."
Input from Øystein: Kan denne være løysinga?: https://w3c.github.io/dxwg/dcat/#Class:Resource
Har de forresten vurdert acat som ei utviding av dcat:DataService? https://w3c.github.io/dxwg/dcat/#Class:Data_Service
I forslaget til DCAT 2 er de generelle delene av katalog-vokabularet endret til ikke å snakke om kun datasett, dermed er DCAT 2 kanskje godt egnet som utgangspunkt for vokabular for API-beskrivelser. I tillegg er det også innført "Data Service" som parallell til "Dataset", som kan bli velegnet til å beskrive API-er.
From: https://www.w3.org/TR/vocab-dcat-2/#Class:Catalog
"The scope of DCAT 2014 was catalogs of datasets [VOCAB-DCAT-20140116]. This has been generalized, and properties common to all cataloged resources are now associated with a super-class dcat:Resource.
Moreover, an explicit class for data services has been added in this revision of DCAT, to enable these to be part of a catalog."
https://github.com/Informasjonsforvaltning/acat/blob/6e29fd059439bea5ed9f0ed238c0ec3bbcf89664/acat.ttl#L32`
Should we maintain a link to the DCAT-vocabulary by for instance sub-classing the corresponding DCAT-elements in the ACAT-vocabulary?