W3C home > Mailing lists > Public > public-rdf-wg@w3.org > July 2011

RDF-ISSUE-69 (fragments): Handling of fragment identifiers in RDF Concepts

From: RDF Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 21 Jul 2011 08:40:51 +0000
To: public-rdf-wg@w3.org
Message-Id: <E1QjooN-0007Mz-H5@stu.w3.org>

RDF-ISSUE-69 (fragments): Handling of fragment identifiers in RDF Concepts


Raised by: Richard Cyganiak
On product: 

This is part of the effort of making RDF Concepts independent from a particular serialization format (RDF/XML).

The RDF Concepts section on “Fragment Identifiers” treats the RDF/XML media type as canonical for establishing the referent of IRIs that include fragment identifier. But today we have many different media types that can carry RDF graphs, and HTTP content negotiation is more common, so this treatment doesn't work anymore.

Also, the problem addressed in the section (context-dependence of fragment identifiers) has to some extent gone away when RFC 2396 was replaced by RFC 3986. The latter states that the same fragment should be used for the same thing in resources that have multiple representations (Section 3.5).

So it might be sufficient to:

1. state that IRIs with fragIDs in RDF graphs can name things external to the graph
2. point to RFC 3986, Section 3.5
3. point out that fragIDs in RDF should be used in a way that's consistent with non-RDF representations; for example, if #foo is a document section in an HTML representation, then it should be treated as naming that document section in any RDF statements; but if #bar is undefined in an HTML representation, then it could name anything in an RDF graph.

This would also answer ISSUE-37.
Received on Thursday, 21 July 2011 08:40:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:04:07 UTC