- From: Bert Van Nuffelen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Apr 2024 08:05:13 +0000
- To: public-dxwg-wg@w3.org
@svituz when reading your case I get the feeling it could be resolved with as @rob-metalinkage mentioned creating a proper DCAT profile. For you specific profiling case, DCAT has 3 options for classifications: - keywords which are literals - subject which are concepts usually exprected from some classification - themes which are a special kind of subjects In the DCAT-AP ecosystem we encounter this need regulary that one would like to classify the datasets according to some domain specific needs. There are two strategies here: - an aggregation one: use dct:subject directly - an precise distinctive one: use a subproperty of dct:subject The second option is the safest in case one deals with datasets that must be documented by multiple DCAT profiles. It means that in your domain you can express a specific set of constraints on that one, and that any other user of that metadata can use it as if it was dct:subject. > > ``` > :studyDataset1 a dcat:Dataset; > dcat:theme icd10:C50; > profile:collectionOrigin obo:NCIT_C25294. > > profile:collectionOrigin rdfs:subPropertyOf dct:subject. > profile:collectionOrigin rdfs:description "The origin of data collection"@en. > profile:collectionOrigin skos:note "This is indicated using the NCIT classification"@en. > ``` > You can use this pattern for as many classifications you want without loosing compatibility with DCAT (because of the subPropertyOf relationship). -- GitHub Notification of comment by bertvannuffelen Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1548#issuecomment-2082109634 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 April 2024 08:05:14 UTC