W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > September 2005

Re: Example Errors (sections 8, 9, 10)

From: Ryan Levering <RRLevering@yahoo.com>
Date: Wed, 7 Sep 2005 16:49:03 -0400
To: <public-rdf-dawg-comments@w3.org>
Message-ID: <97C9F8341808C244BFF39DCB6EDD5AD71116F1@server.home.ryan.levering.name>

>> In section 9.3, the default graph should actually be a named graph with
>> the uri http://example.org/dft.ttl.
>> In section 9.1, the default graph should actually be a named graph with
>> the uri http://example.org/foaf/aliceFoaf.

> Could you say more here?  Reading a graph from a location does not
> automatically give it a name.  That woudl eb FROM NAMED.  This is
> for FROM because there can be several FROM clauses and the default graph
> be formed using all these (e.g. the RDF merge)

> FROM <graph1>
> FROM <graph2>

> In the example in section 9.3, the default graph is formed given the
> IRI <http://example.org/dft.ttl> but that isn't also a naming operation.

> For 9.1 and 9.3, I could add a note to say that the default graph is read
> these locations but not named (that would be done if it were FROM NAMED).

My apologies on my lack of clarity.  The query is fine in both cases, but in
the data listing, the header on the default graphs is "# Default graph",
which isn't nearly as clear as, for instance 9.3: "# Named graph:
http://example.org/dft.ttl" which is what the query actually uses for it's
default dataset.  The point of FROM is that you're using a named graph to
specify a default/background graph, so it would be clearer to actually have
a name on that graph listing.

Ryan Levering
Received on Wednesday, 7 September 2005 20:53:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:01:21 UTC