EARL results for RDFLib against data-r2/graph/manifest.ttl

Attached is a test report documenting an RDFLib run against the
data-r2/graph/manifest.ttl tests.  It passes all the
data-r2/graph/graph*.rq tests.  I followed the testing convention we are
using in the GRDDL WG of including DOAP RDF statements about the test
subject (RDFLib in this case) as well as FOAF RDF statements about the
tester (myself).  I've attached both Turtle and RDF/XML serializations
of the test run.  There was one test that seemed malformed (below).

## graph-02 ##

SELECT * { ?s ?p ?o }

There are two triples in the named graph
(http://www.w3.org/2001/sw/DataAccess/tests/data-r2/graph/data-g1.ttl)
and there is *no* default graph.  Is this dataset well-formed? Section 8
(RDF Dataset) says: "an RDF Dataset *always* contains one default
graph").

So, it is not immediately clear to me what the BGP is matching against
(i.e., what is the 'active' graph), especially when 8.3 (Querying the
Dataset) says: "Outside the use of GRAPH, the default graph is matched
by basic graph patterns." - however, there is no default graph in this
dataset.  Unless the interpretation is that the default graph is an
empty graph.

-- 
Chimezie Ogbuji
Lead Systems Analyst
Thoracic and Cardiovascular Surgery
Cleveland Clinic Foundation
9500 Euclid Avenue/ W26
Cleveland, Ohio 44195
Office: (216)444-8593
ogbujic@ccf.org


===================================




Cleveland Clinic is ranked one of the top 3 hospitals in
America by U.S.News & World Report. Visit us online at
http://www.clevelandclinic.org for a complete listing of
our services, staff and locations.


Confidentiality Note:  This message is intended for use
only by the individual or entity to which it is addressed
and may contain information that is privileged,
confidential, and exempt from disclosure under applicable
law.  If the reader of this message is not the intended
recipient or the employee or agent responsible for
delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If
you have received this communication in error,  please
contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy.  Thank you.

Received on Monday, 9 July 2007 11:48:10 UTC