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

Again I support Richard's argument; I think that changing the
suggested range of dct:language to dct:LinguisticSystem would only
confuse the majority of potential adopters at this stage.

Furthermore, at this stage of he game I think any stakeholder
community that is creating apps which care whether the range of
dct:language is dct:LinguisticSystem is (arguably) sophisticated
enough to deal with any ambiguities that may arise if it isn't so
tightly constrained...

On Mon, Mar 25, 2013 at 7:01 PM, Richard Cyganiak <richard@cyganiak.de> wrote:
> 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
>>
>>
>
>



-- 
John S. Erickson, Ph.D.
Director, Web Science Operations
Tetherless World Constellation (RPI)
<http://tw.rpi.edu> <olyerickson@gmail.com>
Twitter & Skype: olyerickson

Received on Monday, 25 March 2013 23:44:30 UTC