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

Re: For JOS: another entailment example. Re: Test respository; work remaining.

From: Jos De_Roo <jos.deroo.jd@belgium.agfa.com>
Date: Sun, 14 Apr 2002 02:11:48 +0200
To: "Jan Grant <Jan.Grant" <Jan.Grant@bristol.ac.uk>
Cc: "RDFCore Working Group <w3c-rdfcore-wg" <w3c-rdfcore-wg@w3.org>
Message-ID: <OF3C05D9CD.F2307881-ONC1256B9A.00725E65@agfa.be>

> > - entailment tests and manifest files.
> Jos, in the directory
>    http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfs-domain-and-range/
> there is another Manifest.rdf that describes both parser and entailment
> tests for your conjunctive range/domain issue.
> Hopefully this provides sufficient examples to describe your other
> entailment work; I'm writing words for all of this RSN.

[wondering what RSN might mean...]

you've made up a good test vocabulary Jan !!
I'm trying to adapt our running code for that
and for the moment it uses NT/N3 documents, so
I have to do conversions using ARP and/or CWM

for the .../rdfs-domain-and-range/Manifest.rdf
I get some errors like

   http://jena.hpl.hp.com/arp/not/a/real/uri/[20:125]: {E201} Syntax
   error when processing attribute rdf:resource.
   Cannot have attribute rdf:resource in this context.

so I've (*) added a couple of rdf:parseType="Resource" attributes
(as well as test:NT-Document elements for the PositiveEntailmentTest)
and that worked for ARP as well as for with CWM

what I'm going to do is:
  o assert .../rdfs-domain-and-range/Manifest.nt
  o prove .../rdfs-domain-and-range/Manifest.nt
    but in the mean time also create/setup new engines per
      eee a ts:PositiveEntailmentTest .
      eee ts:premiseDocument [ ts:NT-Document aaa ] .
      eee ts:entailmentRules [ ts:NT-Document bbb ] .
      eee ts:conclusionDocument [ ts:NT-Document ccc ] .
    so that we can also prove the entailments at the end

[coming back later]


(*) (See attached file: Manifest.rdf)

Received on Saturday, 13 April 2002 20:13:11 UTC

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