Self-Description of a data service from the Catena-X project
-
Research Catena-X -
Understand scope of data services -
Figure out information do we need to describe Catena-X data service (describe like #161 (closed) in a checklist to be created here), by reviewing the two specifications (DEx and TF) against DCAT @langec (cf. review at gaia-x/technical-committee/federation-services/data-exchange#20) -
Participant
class-
add attribute name
of typestring
(we leave the decision of whether or not this is mandatory to WG Compliance)
-
-
LegalPerson
class-
remove attribute legalName
(actually doesn't exist in Trust Framework!) – instead say that, in the context ofLegalPerson
,name
has minimum cardinality 1.
-
-
DataResource
class-
exposedThrough
(min. cardinality 1) should not point toParticipant
but to aDataExchangeComponent
-
low priority (maybe move to a separate issue): @JohannesL @moosmannp please define (not in YAML but in a separate ontology file) exposedThrough
as a subproperty of the inverse ofdcat:servesDataset
, and/or that the property chaindcat:distribution ∘ dcat:accessService
is a subproperty ofexposedThrough
. #105 opens a way for defining additional knowledge outside of YAML in separate files, but eventually our tools should merge this knowledge into what's generated from YAML.
-
-
add dcterms:issued
-
add dcat:keyword
-
add dcat:theme
-
add policies
, for now with the least restrictive datatype (domain) that's possible – @moosmannp please help what that could be (I mean "no range", or "range = rdfs:Resource")-
low prio: @JohannesL @moosmannp in a separate ontology define odrl:hasPolicy
has a subproperty ofpolicies
-
-
no not yet do anything about dataController
andconsent
, as well asaggregationOf
– still needs clarification -
add copyrightOwnedBy
(a general range like explained above forpolicies
)-
low prio: @JohannesL @moosmannp in a separate ontology file, make it a subproperty of prov:wasAttributedTo
-
-
add dcterms:license
-
add dcterms:identifier
(min. cardinality 1) -
add dcat:distribution
, being of typeDistribution
(see below), min. cardinality 1
-
-
Distribution
class, defined as a subclass ofdcat:Distribution
.-
add dcterms:title
(min. cardinality 1) -
add dcat:mediaType
(min. cardinality 1) -
add dcat:byteSize
-
reuse location
exactly like it's already been defined forPhysicalResource
(@moosmannp could you please advise @jan.froemberg regarding the best way of doing that?) -
add sdpx:checksum
(for this and other terms from external namespaces, mind the right URIs / prefixes!)
-
-
DataExchangeComponent
should be defined as a subclass ofdcat:DataService
. With no attributes for now, as the DEWG spec does not yet specify any.
-
-
implement it in SPoT/YAML (!130 (closed)) @jan.froemberg -
rewrite old/previous "air quality data" example with the new schema @hylkevds -
Update (as needed) the old data service tutorial.
Edited by Jan Frömberg