Re: Test cases: format of input and output(uri/node/resource/entity too)

Isn't this a question of what the RDF parser is supposed to do,
of what the RDF abstract syntax is?  I imagined that the abstract
syntax was triples of absolute URIs and strings. So to test a parser
you have to make sure that it can produce those.

Using xml Base does make sense.  Also, it makes sense to
build systems which operate on web resources while keeping
a local catalog of previous (direct or indirect) web experience.
I'm inclined to build this into my python code, I'd love it if
it were built into python or into the OS.

A solution Dan uses is to run a local proxy, so that the caching
stuff is all in a separate procxess out of the way.
Any of these ways of working would mean different folks
could do the same thing to the same test data and produce
the same absolute URIs, online or offline.

Tim

----- Original Message -----
From: "Aaron Swartz" <aswartz@upclink.com>
To: "Brian McBride" <bwm@hplb.hpl.hp.com>; "Dan Connolly" <connolly@w3.org>
Cc: "Jan Grant" <Jan.Grant@bristol.ac.uk>; <timbl@w3.org>; "RDFCore Working
Group" <w3c-rdfcore-wg@w3.org>
Sent: Thursday, May 31, 2001 11:46 AM
Subject: Re: Test cases: format of input and output(uri/node/resource/entity
too)


> Brian McBride <bwm@hplb.hpl.hp.com> wrote:
>
> >> We've got terms of the form
> >>         _:name          for "anonymous" terms
> >>         <absURIref>     for URIs
> >>         "lskdjf"        for string literals.
> >
> > How would we handle relative URI's, e.g.:
> >
> > <rdf:Description rdf:ID='foo'/>
>
>
> I'd suggest just using relative URIs e.g.:
>
>     <#foo>
>
> Alternately, we could define a base URI:
>
>     <http://rdf.example.org/tests/t923#foo>
>
> --
> [ "Aaron Swartz" ; <mailto:me@aaronsw.com> ; <http://www.aaronsw.com> ]
>
>

Received on Friday, 1 June 2001 09:29:21 UTC