W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > November 2001

Re: Proposal to drop S from consideration

From: Dan Connolly <connolly@w3.org>
Date: Mon, 26 Nov 2001 11:39:11 -0600
Message-ID: <3C027E3F.3697EEA7@w3.org>
To: Graham Klyne <Graham.Klyne@MIMEsweeper.com>
CC: Jeremy Carroll <jjc@hplb.hpl.hp.com>, Patrick.Stickler@nokia.com, w3c-rdfcore-wg@w3.org
Graham Klyne wrote:
> At 08:36 AM 11/26/01 -0600, Dan Connolly wrote:
> >Note that it'sn not the XML parser that type converts "40", but
> >the application that knows about <age>. The analagous situation
> >in RDF is: the object of <age> is a string, and the range
> >of the age property is a numeral, not a number. [this
> >is the case in S]
> Er, I'm missing something here.  I thought it was precisely this that the S
> proposal does not allow.  Indeed, I thought the only proposals to allow
> this are P/P++.

The P/P++ proposals are about writing <age>10</age>
and having the value be a number -- the 10th integer --
not a numeral -- the two character string '1' followed by '0'.

In S, all* literals denote strings. The only way to
express a number is ala "the number whose decimal
representation is '10'".

In CC/PP-as-written, the instance data says <age>10</age>
and the schema says
	age range integer.

The P/P++ proposal makes sense of CC/PP-as-written-style instances
and schemas (at an unacceptable cost, to me: the
denotation of literals is all mucked up).

To use S, you'd either have to change the CC/PP-style schemas
to say
	age range integerNumeral
to match <age>10</age> or
or change the instance to say
	<age dt:integer="10"/>.
to match age range integer.

* all except the parseType="Literal" ones, which
denote structured XML thingies, to me; but that's
another issue altogether.

Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Monday, 26 November 2001 12:40:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:06 UTC