- From: <Patrick.Stickler@nokia.com>
- Date: Fri, 5 Sep 2003 14:42:04 +0300
- To: <jjc@hplb.hpl.hp.com>
- Cc: <bwm@hplb.hpl.hp.com>, <w3c-rdfcore-wg@w3.org>, <Patrick.Stickler@nokia.com>
Thanks. Patrick > -----Original Message----- > From: ext Jeremy Carroll [mailto:jjc@hplb.hpl.hp.com] > Sent: 05 September, 2003 13:59 > To: Stickler Patrick (NMP/Tampere) > Cc: bwm@hplb.hpl.hp.com; w3c-rdfcore-wg@w3.org > Subject: Re: Agenda for RDFCore WG Telecon 2003-09-05 > > > > Dave Reynold's original comment: > http://lists.w3.org/Archives/Public/www-rdf-comments/2003JulSe > p/0076.html > > [[ > PositiveEntailmentTest > xmlsch-02/Manifest.rdf#whitespace-facet-3 - FAIL > This tests bNode introduction - that a typed literal > entails a graph > with a bNode of type rdf:Literal. We have deliberately omitted the > bNode introduction rules from the reasoner config on the > grounds that > this is not the way an RDF API should do it - users can query the > nodes themselves for type information and creating virtual triples > for this would be wrong from an API perspective. > > ** Failures - could fix: > NegativeEntailmentTest > xmlsch-02/Manifest.rdf#whitespace-facet-2 - FAIL > NegativeEntailmentTest > xmlsch-02/Manifest.rdf#whitespace-facet-1 - FAIL > These test non-mutual entailment of a valid literal with an invalid > literal that differs only by whitespace. Unfortunately our XSD > handling library is happy with the whitespace and doesn't > treat " 3 " as an invalid int. > This could be fixed if that is indeed how XSD is supposed to work, > though the current behaviour seems more useful in practice. > ]] > > Patrick.Stickler@nokia.com wrote: > > > Could someone please provide a pointer to the actual comment... > > > > Thanks, > > > > Patrick > > > > > > >
Received on Friday, 5 September 2003 07:42:08 UTC