W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2004

DAWG test manifests need classes for encoding file formats

From: Dave Beckett <dave.beckett@bristol.ac.uk>
Date: Tue, 2 Nov 2004 10:36:52 +0000
To: DAWG public list <public-rdf-dawg@w3.org>
Message-Id: <20041102103652.63d96770@hoth.ilrt.bris.ac.uk>

While trying out Alberto's source tests (still doing that)
I met the problem I expected I'd get, you have to look at the URIs
to choose a parser.  We need to encode that in the manifests now
as RDF Core did for tests - see http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/

I mean, please add X rdf:type XYZ triples to things like:

        mf:action
            [ qt:query  <source-query-001> ;
              qt:data   <source-data-01.n3> ;
              qt:metadata   <source-metadata-01.n3> ] ;

from Alberto's
  http://www.rdfstore.org/dawg-testcases/data/source-simple2/manifest.n3

to such as:
        mf:action
            [ qt:query  <source-query-001>, a mf:QueryFIle ;
              qt:data   <source-data-01.n3>,. a mf:RDFXMLFile ;
              qt:metadata   <source-metadata-01.n3>, a mf:TurtleFile ] ;

(or n3 file ;)

and add the classes somewhere, I chose mf: here as the namespace.

This lets apps reading the manifest use the rdf to see what parser to use
You cannot rely on mime types since these must run locally with no protocol,
can be local files and SPARQL or Turtle/n3 could both be text/plain.

Dave
Received on Tuesday, 2 November 2004 10:39:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:21 GMT