Re: draft question: option C

I'm a little unclear on proposal C... in
particular, what does it say about what
folks can put in schemas to constrain
an age propoerty to be/look-like decimals?


The 6Sep minutes
http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Sep/0081.html
cite a 29Aug proposal
http://www-nrc.nokia.com/sw/rdf-datatyping.html
which says "The RDF class extension of an rdfs:Datatype
is its value space."

I want to be sure that whatever spec we come up with,
I can continue to use the datatype property idiom...
    <k:Thursday r:about="#_thu10">
        <dt:date>2002-10-10</dt:date>
    </k:Thursday>
	-- http://www.w3.org/2002/10dc-uk/itin3.rdf

So far, our (published WD) specs have been consistent
with a view that classes and properties are disjoint. (In
SWAD, we use that assumption for lint-style checking.)
The 6Sep decision seems to conflict with the
use of the datatype property idioim under
the disjointness-of-properties-and-classes
assumption.


On Thu, 2002-10-10 at 15:50, Brian McBride wrote:
> 
> Draft option C question for discussion at Friday's telecon
> 
> This WG resolves
> 
> that:
> 
>    <a> <b> "10" .
>    <c> <d> "10" .
> 
> entails
> 
>    <a> <b> _:l .
>    <c> <d> _:l .
> 
> [[ Possible additions to the resolution
> 
> that it reaffirms it previous decision that datatype values can be 
> represented in the following form:
> 
>    <rdf:Description>
>      <foo:bar rdf:datatype="datatype">10</foo:bar>
>    </rdf:Description>
> 
> which is translated into (the final syntax not having been agreed) as:
> 
>    _:a foo:bar datatype"10" .
> 
> that:
> 
>    <a> <b> "10" .
>    <c> <d> xsd:integer"10" .
> 
> does not entail:
> 
>    <a> <b> _:v .
>    <c> <d> _:v .
> 
> that:
> 
>    <a> <b> "10" .
>    <b> rdfs:range xsd:integer"10" .
> 
> has no interpretations.
> 
> ]]
-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/

Received on Friday, 11 October 2002 09:52:19 UTC