W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > December 2001

RE: The Problems with Fragments

From: Jeremy Carroll <jjc@hplb.hpl.hp.com>
Date: Mon, 10 Dec 2001 10:13:26 -0000
To: "Aaron Swartz" <me@aaronsw.com>, "RDF Core" <w3c-rdfcore-wg@w3.org>
Message-ID: <JAEBJCLMIFLKLOJGMELDMEKHCCAA.jjc@hplb.hpl.hp.com>

I find Aaron's arguments both substantive and somehow unpersuasive.

So there are issues with fragments - is the RDF specs the right place to
address them, or should they be addressed elsewhere.

>  They're not URIs

Fix RFC 2396

> Their semantics only work in the context of a single representation

Fix RFC 2396

> They don't integrate well with the HTTP Web

Fix HTTP defns to allow these features

> Fragments don't allow redirects


> Fragments aren't consistent across content-negotiation

I am not sure where this should be fixed.

> Some fragments break even when you change the document:
(xe.g. #xpointer(id("reasons")/li[3]) )

Fix users! :-) This fragment is fairly broken, but that doesn't damn the

As we expand the demands we are making on URIs it is inevitable that we make
new requirements that haven't previously been addressed. While we have to be
confident that we can get by with the current versions of the standards
(RFC2396 and HTTP defn, wherever that is), it doesn't have to be perfect. At
the next rev of these things we have some input.

Received on Monday, 10 December 2001 05:16:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:54 UTC