- From: Jos De_Roo <jos.deroo.jd@belgium.agfa.com>
- Date: Mon, 23 Sep 2002 09:35:54 +0200
- To: jjc@hpl.hp.com
- Cc: www-archive@w3.org
Jeremy, I actually wonder if you ever got this mail
as I don't yet see it at www-archive@w3.org
(and I sent it last saturday morning)
-- ,
Jos De Roo, AGFA http://www.agfa.com/w3c/jdroo/
----- Forwarded by Jos De_Roo/AMDUS/MOR/Agfa-NV/BE/BAYER on 2002-09-23
09:31 AM -----
Jos De_Roo
To: Jeremy Carroll <jjc@hpl.hp.com>@AGFADMZ@AGFASMTP
2002-09-21 10:29 cc: jjc@hplb.hpl.hp.com, www-archive@w3.org
AM Subject: Re: OWL test cases(Document link: Jos De_Roo)
Hi Jeremy,
> I've progressed somewhat, and wanted to share with you where i had got
to; and
> then if you're happy, I will send a message giving the rest of the group
a
> heads up.
that is looking very well and I'm happy as I was able
to test it on my machine
> So:
>
> I have a version of my old document that now generates the triples and
does
> some checking on the test cases.
> This is found:
>
> http://sealpc09.cnuce.cnr.it:8080/wowg/jsp/main.jsp
>
> I also attach a static copy, just in case tomcat dies.
> (Note the refresh and caching is a bit muddled, so don't expect it to
show the
> very latest updates).
right, on my machine, I checked it out, compiled it
and just got
[[[
C:\w3ccvs\WWW\2002\03owlt\editors-draft\WEB-INF\classes\wowg>javac
-classpath \w3ccvs\WWW\2002\03owl
t\editors-draft\WEB-INF\lib\icu4j.jar;
\w3ccvs\WWW\2002\03owlt\editors-draft\WEB-INF\lib\jena.jar;\w3
ccvs\WWW\2002\03owlt\editors-draft\WEB-INF\lib\tidy.jar;
\w3ccvs\WWW\2002\03owlt\editors-draft\WEB-IN
F\lib\xerces.jar;C:\w3ccvs\WWW\2002\03owlt\editors-draft\WEB-INF\classes
*.java
Zipper.java:8: package javax.servlet.http does not exist
import javax.servlet.http.*;
^
Zipper.java:21: cannot resolve symbol
symbol : class HttpServletRequest
location: class wowg.Zipper
static public String getParameter(HttpServletRequest req, String nm) {
^
Zipper.java:39: cannot resolve symbol
symbol : class HttpServletRequest
location: class wowg.Zipper
public Zipper(HttpServletRequest request) {
^
Note: Zipper.java uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
]]]
but was able to run
http://vam969.roam.agfa.be:8080/w3ccvs/WWW/2002/03owlt/editors-draft/jsp/main.jsp
and got the nice document with the following server log
[[[
[INFO] Registry - -Loading registry information
[INFO] Registry - -Creating new Registry instance
[INFO] Registry - -Creating MBeanServer
[INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.10
[INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080
[INFO] ChannelSocket - -JK2: ajp13 listening on tcp port 8009
[INFO] JkMain - -Jk running ID=0 time=0/110 config=C:
\jakarta-tomcat-4.1.10\conf\jk2.properties
Loading: http://www.w3.org/2002/07/owl#
Loading: http://www.w3.org/2002/03owlt/I4.1/Manifest
Loading: http://www.w3.org/2002/03owlt/FunctionalProperty/Manifest
Loading: http://www.w3.org/2002/03owlt/testOntology
Loading: http://www.w3.org/2000/10/rdf-tests/rdfcore/testSchema
line 335 column 1 - Error: <table> missing '>' for end of tag
line 362 column 1 - Error: <table> missing '>' for end of tag
line 384 column 1 - Error: <table> missing '>' for end of tag
line 406 column 1 - Error: <table> missing '>' for end of tag
line 445 column 1 - Error: <table> missing '>' for end of tag
line 465 column 1 - Error: <table> missing '>' for end of tag
line 486 column 1 - Error: <table> missing '>' for end of tag
This document has errors that must be fixed before
using HTML Tidy to generate a tidied up version.
http://www.w3.org/2002/03owlt/testOntology#NotOwlFeatureTest ==>
NotOwlFeatureTest
http://www.w3.org/2002/03owlt/testOntology#PositiveEntailmentTest ==>
PositiveEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#NegativeEntailmentTest ==>
NegativeEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#NegativeEntailmentTest ==>
NegativeEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#PositiveEntailmentTest ==>
PositiveEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#PositiveEntailmentTest ==>
PositiveEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#NotOwlFeatureTest ==>
NotOwlFeatureTest
http://www.w3.org/2002/03owlt/testOntology#PositiveEntailmentTest ==>
PositiveEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#NegativeEntailmentTest ==>
NegativeEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#NegativeEntailmentTest ==>
NegativeEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#PositiveEntailmentTest ==>
PositiveEntailmentTest
http://www.w3.org/2002/03owlt/testOntology#PositiveEntailmentTest ==>
PositiveEntailmentTest
]]]
> I also have created a web form for the creation and zipping of test
cases.
> This is here:
>
> http://sealpc09.cnuce.cnr.it:8080/wowg/jsp/edit.jsp
>
> (Again a non-functional static copy is attached).
>
> The validate button is a no-op, and the zip button doesn't work the
second
> time if you press it twice successively.
> The author drop down list is a mock-up, not really implemented - it will
give
> a list of all dc:creators of current tests, so that you can just pick
your
> name off the list.
>
> Try this, and then press the "Refresh from W3C" button.
> Then maybe add an author and press the zip button.
>
>
http://sealpc09.cnuce.cnr.it:8080/wowg/jsp/edit.jsp?feature=InverseFunctionalProperty
wow, that is fantastic!
> A minor issue is that the tool presupposes a change to the way we handle
> Manifests.
> The old approach was to have one manifest in each dir.
> The tool does one manifest for each *test*, so that a test consists of
either
> two or three files, one of which is the metadata.
>
> The URI of the tests themselves also change:
> old style
> *dir*/Manifest#testNNN
> new style
> *dir*/ManifestNNN#test
>
>
> Advantages of the tool:
>
> - creation of Manifests
> - verification against or avodiance of common problems.
>
> I'll probably try and get the validate working before showing it to the
group.
>
> Once we've done that we should hassle people into producing some tests,
e.g.
> Nothing would be an easy inconsistency test, and would give rise to an
e-mail
> subject line:
> TEST: please do Nothing
fantastic!
as an aside
maybe we should explain somehow
Proof EntailmentTest | Reasoner
-----------------------------------------------------------
Found Positive | OK
Found Negative | NOT OK (unsound)
Not Found Positive | OK for *incomplete* reasoner
Not Found Negative | OK
-- ,
Jos De Roo, AGFA http://www.agfa.com/w3c/jdroo/
Received on Monday, 23 September 2002 03:39:00 UTC