ISSUE-37: How should dcat publishers figure out good URIs for properties with non-literal ranges?
nonLiterals
How should dcat publishers figure out good URIs for properties with non-literal ranges?
- State:
- CLOSED
- Product:
- dcat
- Raised by:
- Ed Summers
- Opened on:
- 2010-05-27
- Description:
- Raised by Ed Summers:
http://lists.w3.org/Archives/Public/public-egov-ig/2010May/0056.html
I wonder if it is worthwhile acknowledging (at least to ourselves) that the ranges of dct:publisher, dct:accrualPeriodicity, dct:spatial, dct:temporal, dcat:granularity, dcat:theme could be at odds with the
Simple Transformation From Existing Catalog Data requirement. For example a dataset publisher may know that the dataset is about "Berlin, Germany" ... but they would have some work to do to figure
out what URI to use with dct:spatial. Similarly they may know that a dataset is published by the National Aeronautics and Space Administration, but they will have to do some work to use a linkeddata friendly URI like <http://dbpedia.org/resource/NASA>. - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-37 (nonLiterals): How should dcat publishers figure out good URIs for properties with non-literal ranges? [dcat] (from richard@cyganiak.de on 2010-06-10)
- ISSUE-37 (nonLiterals): How should dcat publishers figure out good URIs for properties with non-literal ranges? [dcat] (from sysbot+tracker@w3.org on 2010-05-27)
Related notes:
The following related comment was made by Stuart Williams in an off-list exchange:
"I also think that we need to establish some practice as to whether literal or object values are expected for some of the ranges. eg. dcat:keyword on the one hand seems like a property that would have a literal value which would probably need to be scoped by a dcat:dataDictionary. OTOH if the keywords are formed as SKOS concepts then they (potentially) bring with them their membership of a SKOS ConceptScheme, metadata (inc. labels) for the 'keyword' and in anycase having a URI name disambiguates between similarly named concepts (ie. with common local names - whether '#' or '/' namespaces are being used)."
Transferred to GLD system where it is now Issue 6
https://www.w3.org/2011/gld/track/issues/6
Display change log
