W3C home > Mailing lists > Public > www-rdf-comments@w3.org > January to March 2003

Re: Comments on informal meaning of the RDFS vocabulary

From: Brian McBride <bwm@hplb.hpl.hp.com>
Date: Wed, 29 Jan 2003 19:49:54 +0000
Message-Id: <5.1.0.14.0.20030129192311.00a967a8@localhost>
To: "Peter F. Patel-Schneider" <pfps@research.bell-labs.com>
Cc: www-rdf-comments@w3.org

At 08:42 29/01/2003 -0500, Peter F. Patel-Schneider wrote:

[...]


>Well, if one really believed RDF Schema, then the model-theoretic behaviour
>of RDF should abide by whatever is said in rdfs:comment value.  For
>example,

The following example clarifies the question very well.  Thanks.


>         ex:Cretan rdf:subClassOf ex:Person .
>         ex:Cretan rdfs:comment "All Cretans are liars" .
>
>would mean that the model theoretic consequences of
>
>         ex:John rdf:type ex:Cretan .

The text in:

   http://www.w3.org/TR/rdf-schema/#ch_comment

is:

[[
A triple of the form:

R rdfs:comment L

states that L is a human readable description of R.

]]

What text suggests that there is any *model theoretic* consequences of the 
natural language interpretation of L?

[...]

>So, an implementor who looks to Schema for guidance on how to build an RDF
>system is going to get the impression that there is no difference in import
>between the meanings given to rdf:type and rdfs:label.  The implementor may
>decide that the only suitable way of presenting resources to users is via
>values of their rdfs:label properties.

We seem to have switched to rdfs:label.  The text at:

   http://www.w3.org/TR/rdf-schema/#ch_label

is

[[
rdfs:label is an instance of rdf:Property that is used to provide a 
human-readable version of a resource's name.

A triple of the form:

R rdfs:label L

states that L is a human readable label for R.
]]

Right, that could be tidied up:

[[rdfs:label is an instance of rdf:Property that may be used to provide a 
human-readable version of a resource's name.]]

Would that be better?


>The implementor may decide that RDF
>lists have unique firsts and rests and write an RDF system accordingly.  The
>user may believe that RDF lists must always have unique firsts and rests.

That is clearly the design centre.  What text in the schema doc is incorrect.

Brian
Received on Wednesday, 29 January 2003 14:48:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 21 September 2012 14:16:31 GMT