- From: <jos.deroo@agfa.com>
- Date: Thu, 11 Nov 2004 20:27:15 +0100
- To: kendall@monkeyfist.com
- Cc: public-rdf-dawg@w3.org, public-rdf-dawg-request@w3.org
Kendall, While reading your draft (which I more than enjoy!) I was wondering how it would look for the cases we use daily.. (although I could do this myself, I thought your help would be better :)) For example, we use (on intranet) http://josd.he.agfa.be:8081/euler.EulerRunner?doProof=http://josd.he.agfa.be:8081/2004/04rm/refGuidelines/pregnancyProtectionFetus.n3 http://www.agfa.com/w3c/euler/rdfs-rules.n3 --nope --think --query http://josd.he.agfa.be:8081/2004/04rm/refGuidelines/pregnancyProtectionFetusQ.n3 This is not url-encoded (but the browsers and http clients that I use are happy with it) and basically indicates that service http://josd.he.agfa.be:8081/euler.EulerRunner is given the command line arguments that we use for euler proof mechanism i.e. given graphs http://josd.he.agfa.be:8081/2004/04rm/refGuidelines/pregnancyProtectionFetus.n3 http://www.agfa.com/w3c/euler/rdfs-rules.n3 and modi --nope i.e. "no proof explanation" --think i.e. "find all proofs" return the answers for --query http://josd.he.agfa.be:8081/2004/04rm/refGuidelines/pregnancyProtectionFetusQ.n3 and then we get back :An :mustHave :confirmationOfNonPregnancy. hope this is not too much of a burden :) thanks -- Jos De Roo, AGFA http://www.agfa.com/w3c/jdroo/ Kendall Clark <kendall@monkeyfist.com> Sent by: public-rdf-dawg-request@w3.org 09/11/2004 15:17 Please respond to kendall To: public-rdf-dawg@w3.org cc: (bcc: Jos De_Roo/AMDUS/MOR/Agfa-NV/BE/BAYER) Subject: protocol draft available Les Chiens, I'm relieved (!) to say that I've finally got a protocol draft that I'm willing to publicly share, in the event anyone's still interested. You can find it at http://monkeyfist.com/kendall/sparql-protocol/ but that should be considered a temporary location, I suspect. If the primary consideration was that it fit on one sheet of paper, then either I was the wrong person to work on this or it's just more complex than that. Or both. :> I worked really hard to describe an abstract protocol that could be realized in the Unix command-line environment, SOAP, HTTP, BEEP, and other diverse environments, and that took a great deal of time. I biased that abstract description in favor of HTTP, when things were otherwise tricky, but I hope not too much. It probably doesn't need to be said, but this is a draft, it's full of warts, bugs, and outright errors. I will continue to work on it pretty much all the time, which means now that I'm sharing it, I'll add some date/time/RCS-markers, so that changes are easier to detect. I hope that it helps, at the very least, focus our discussion and move us toward CR status with all deliberate speed. Best, Kendall Clark -- Sometimes it's appropriate, even patriotic, to be ashamed of your country. -- James Howard Kunstler
Received on Thursday, 11 November 2004 19:27:56 UTC