W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > August 2002

Re: What the #@&*$(!@ is going on here?! (was RE: N-Triples for proposed xsi:type [was Re: xsi:type test case ]

From: Jan Grant <Jan.Grant@bristol.ac.uk>
Date: Wed, 7 Aug 2002 12:39:11 +0100 (BST)
To: Dave Beckett <dave.beckett@bristol.ac.uk>
cc: "Patrick.Stickler" <Patrick.Stickler@nokia.com>, w3c-rdfcore-wg <w3c-rdfcore-wg@w3.org>, "Graham.Klyne" <Graham.Klyne@MIMEsweeper.com>, jjc <jjc@hplb.hpl.hp.com>
Message-ID: <Pine.GSO.4.44.0208071224290.3661-100000@mail.ilrt.bris.ac.uk>

On Wed, 7 Aug 2002, Dave Beckett wrote:

> >>>"Patrick.Stickler" said:
> > [lots]
> Don't read into a proposed N-Triples syntax change more than I wrote.
> I could have put it has datatype(decimal, "2.0") or somesuch.
> Specifically don't read that as qnames but evocative of how XSD is
> used in XML; similar how the xsi:type is being used in this RDF/XML -
> a special attribute.
> But I'm still waiting for the triples for these RDF/XML + xsi:type
> examples.  Which is hard to do if they have no n-triples syntax.
> I'll create a better N-triples if needed when I'm clear what (if
> anything) has changed in the graph.  Catch 22.

What's changed in the graph is that the space of "literals" has
expanded; that is that

	jenny age "10" .


	jenny age number(10) .

are distinct triples, but that

	jenny age number(10) .
	bob age number(10) .

indicates that jenny and bob really do have the same age.

As to how much it has expanded: this proposal seems to be capable of
going two ways:

1. the space of literals is expanded by a small set of other literal
types to provide a sufficient foundation for datatyping to be built
upon. That a small set can be sufficient is indicated by the success
people have in using RDBM systems, I suppose. This proposal would then
need guidelines as to what to do with other "datatypes": eg: factor out
units in property values; use uri-labelled resources for enumerations
and taxons; use graph-structure to express compound types.

This reading means that the RDF parser must have a transform from some
serialised form to the appropriate value, but that the values are what
are present in the graph. In this case, the "hook" for that transorf is
the xsi:type attribute. The space of literals is not extnsible by third

Presumably for datatyping and range constraints, etc, rdf:Literal
(rdfs:Literal? I forget) is subclassed into numbers (or ints and reals),
strings, langstrings, whatever.

That literals are essentially self-denoting entities is obvious in this

2. the space of literals is arbitrarily expandable by users, and literal
nodes in the graph are of the form <type, thing> where a "thing" may or
may ont be a lexical form. Treatment of compound, union, intersection of
types is unclear in this system.

In this case the proposal is effectively "drawing a circle" around the
construct from one of the other datatyping proposals that uses
node-and-arc constructs, and calling the whole contents of that circle
"the literal"

jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk
Lambda calculus? I hardly know 'er!
Received on Wednesday, 7 August 2002 07:40:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:59 UTC