W3C home > Mailing lists > Public > www-rdf-interest@w3.org > October 2001

Re: RDFCore Update

From: Thomas B. Passin <tpassin@home.com>
Date: Thu, 18 Oct 2001 23:49:36 -0400
Message-ID: <00ab01c15851$127901c0$7cac1218@cj64132b>
To: <www-rdf-interest@w3.org>
[Brian McBride]

> One major area of focus for the WG at the moment is datatyping, e.g. using
> schema datatypes in RDF.  Now would be a good time to let us have your
> and ideas on this.
 Some of the other posts on this subject have dived right into the XML RDF
syntax.  I suggest getting clear on what the appropriate triples (or
subgraph) would be like, before moving on to the syntax.

To me it seems clear that if you relate a value to a subject by using a
property, you then would want to (optionally) be able to hang an arc off
that value node that attaches some datatype to it.  This takes us back to
the discussion about whether you should be able to do that or not, or
instead model the value with an anonymous resource node that you can hang
the value and datatype onto.  I suggest that some of the other proposals to
encode the typing into a URI should be considered to be equivalent

(some_subject)---(hasValue)--->( 25.2 )----(datatype)----->(xsd:float)

(some_subject)---(hasValue)--->(  )----(datatype)----->(xsd:float)


Given the vagaries of rendering with various fonts, I'm not sure the second
example will display right for everyone, but it is meant to show an
anonymous node with both a datatype and a value arc attached to it.

Now if we take this approach, we can use RDF to assert the range and domain
of the datatype, but if we encode the type into a URI that would be much

In any event, let's get clear on the model before we start churning out
alternative XML interchange syntax.

This approach would let you plug in other datatypes just by using their
namespace instead of the xsd: (or whatever) namespace (yes, I know the
namespace is really the URI, not the prefix!)


Tom P
Received on Thursday, 18 October 2001 23:44:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:38 UTC