- From: <Patrick.Stickler@nokia.com>
- Date: Wed, 7 Nov 2001 15:08:11 +0200
- To: Graham.Klyne@MIMEsweeper.com, bwm@hplb.hpl.hp.com
- Cc: w3c-rdfcore-wg@w3.org
Thanks for the info. This actually makes the example of the size property even more meaningful, as it shows the ambiguity even more clearly. Since there is no single derived type "responsible" for disambiguation, there is no explicit means to decide *which* range should be used to interpret the non-locally typed literal. Patrick > -----Original Message----- > From: ext Graham Klyne [mailto:Graham.Klyne@MIMEsweeper.com] > Sent: 07 November, 2001 14:13 > To: Stickler Patrick (NRC/Tampere); Brian McBride > Cc: RDF core WG > Subject: RE: incomplete datatyping (was: Re: datatypes and MT) > > > At 01:12 PM 11/7/01 +0200, you wrote: > > > Suppose that in addition to: > > > > > > monthOfBirth rdfs:range xxd:EnglishCalendarMonth . > > > > > > we can also presume: > > > > > > monthOfBirth rdfs:range xxd:decimalInteger . > > > > > > (this being legit RDF) ... might the allow us to write: > > > >But a property may only have one range. Right? So this isn't > >legit RDF. Or has that changed? > > It's changed. > > See "Decisions" in: > > http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2001Aug/att > -0058/01-Overview.html > > But I note that this isn't reflected in the issue tracking > document at: > http://www.w3.org/2000/03/rdf-tracking/#rdfs-domain-and-range > (Brian: is this an administrative glitch, or is there a good reason?) > > #g > > > ------------------------------------------------------------ > Graham Klyne MIMEsweeper Group > Strategic Research <http://www.mimesweeper.com> > <Graham.Klyne@MIMEsweeper.com> > ------------------------------------------------------------ >
Received on Wednesday, 7 November 2001 08:08:23 UTC