W3C home > Mailing lists > Public > public-gld-wg@w3.org > March 2013

Re: DCAT Last Call issues: range of dct:language

From: Richard Cyganiak <richard@cyganiak.de>
Date: Mon, 25 Mar 2013 18:01:32 +0000
Cc: "Public GLD WG" <public-gld-wg@w3.org>
Message-Id: <85874636-E9A1-44BA-AEE6-0A56DEA1C77B@cyganiak.de>
To: "Makx Dekkers" <makx@makxdekkers.com>
On 25 Mar 2013, at 16:03, "Makx Dekkers" <makx@makxdekkers.com> wrote:
> Property dct:language (http://www.w3.org/TR/2013/WD-vocab-dcat-20130312/#Property:catalog_language,  http://www.w3.org/TR/2013/WD-vocab-dcat-20130312/#Property:dataset_language) is defined with range rdfs:Resource, while athttp://dublincore.org/documents/dcmi-terms/#terms-language, the range is defined as dct:LinguisticSystem. Shouldn’t DCAT inherit the (narrower) range as defined by DCMI?

If we specify the range that way, Then people will get scared because the LoC URIs whose use we recommend are not typed as dct:LinguisticSystem. Lots of RDF users don't understand that classes may be overlapping, and that rdfs:range is descriptive rather than prescriptive.

Given that rdfs:Resource is pretty much the set of everything, the statement that dct:language has range rdfs:Resource is trivially correct.

IMHO it would be better to drop the rdfs:Resource range, and leave only the LoC recommendation in the range box, than saying that the range is dct:LinguisticSystem.

Best,
Richard



>  
> Makx.
>  
>  
> Makx Dekkers
> makx@makxdekkers.com
> +34 639 26 11 46
>  
>  
Received on Monday, 25 March 2013 18:01:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:52:06 UTC