- From: Karl Dubost <karl@w3.org>
- Date: Wed, 18 Feb 2004 15:07:36 -0500
- To: <www-rdf-interest@w3.org> <www-rdf-interest@w3.org> <www-rdf-interest@w3.org>
Le 17 févr. 2004, à 07:11, Patrick Stickler a écrit : > One problem with using URIrefs with fragment identifiers is that > alot (even most?) HTTP software agents presume that the fragment > identifier is relevant *exclusively* within the context of > processing/intepreting a representation by some client (and I > actually agree) and so any HTTP requests with URIrefs having Unfortunately true. See CUAP and fragment identifier[1] """URI1 has a fragment identifier #frag, then the new target that the user agent should be trying to reach would be URI2#frag. If URI2 already has a fragment identifier, then #frag must not be appended and the new target is URI2.""" [1] http://www.w3.org/TR/cuap#cp-fragment -- Karl Dubost - http://www.w3.org/People/karl/ W3C Conformance Manager *** Be Strict To Be Cool ***
Received on Wednesday, 18 February 2004 22:59:57 UTC