W3C home > Mailing lists > Public > public-egov-ig@w3.org > May 2010

ISSUE-37 (nonLiterals): How should dcat publishers figure out good URIs for properties with non-literal ranges? [dcat]

From: eGovernment Interest Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 27 May 2010 14:41:16 +0000 (GMT)
To: public-egov-ig@w3.org
Message-Id: <20100527144116.E61A5C06B@nelson.w3.org>

ISSUE-37 (nonLiterals): How should dcat publishers figure out good URIs for properties with non-literal ranges? [dcat]

http://www.w3.org/egov/IG/track/issues/37

Raised by: Ed Summers
On product: dcat

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>.
Received on Thursday, 27 May 2010 14:41:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 27 May 2010 14:41:18 GMT