- From: Jos De_Roo <jos.deroo.jd@belgium.agfa.com>
- Date: Wed, 7 Aug 2002 11:51:58 +0200
- To: Patrick.Stickler@nokia.com
- Cc: Graham.Klyne@MIMEsweeper.com, jjc@hplb.hpl.hp.com, w3c-rdfcore-wg@w3.org
> > >Are the two documents descriptions of the same graph?
> > >
> > ><rdf:RDF>
> > > <rdf:Description>
> > > <eg:prop xsi:type="xsd:decimal">2.0</eg:prop>
> > > </rdf:Description>
> > ></rdf:RDF>
> > >
> > >
> > >
> > ><rdf:RDF>
> > > <rdf:Description>
> > > <eg:prop xsi:type="xsd:decimal">2.00</eg:prop>
> > > </rdf:Description>
> > ></rdf:RDF>
> > >
> > >I think I heard yes.
> >
> > If the literal is intended to be a number, then I think yes.
>
> A few questions:
>
> 1. What triples are generated from the above?
for
<rdf:RDF>
<rdf:Description>
<eg:prop xsi:type="xsd:decimal">2.0</eg:prop>
</rdf:Description>
</rdf:RDF>
I'm still tempted to say (in NTriples)
_:aaa eg:prop _:bbb .
_:bbb xsd:decimal "2.0" .
but I guess one wants to see
_:aaa eg:prop xsd:decimal"2.0" .
(I'm not yet "more comfortable with it as each day goes by")
> 2. Will this work with non-XML Schema datatypes?
I guess so
> 3. Will this work with arbitrarily/user defined primitive types?
I guess so
> 4. How does this relate to defining datatype ranges of properties?
well I guess global range constraints
could be used to detect inconsistencies, no?
(too much guesses I guess)
-- ,
Jos De Roo, AGFA http://www.agfa.com/w3c/jdroo/
Received on Wednesday, 7 August 2002 06:03:13 UTC