Re: fragment identifiers

On Thu, Jul 25, 2002 at 05:08:42PM -0700, Roy T. Fielding wrote:
> The #foo doesn't leave the client when performing an interaction
> between components within the WWW architecture.  By definition,
> information that stays within a component when performing an
> interaction is not a data element for that interaction.  Since the
> whole architecture is based on the premise of interacting with
> resources that are identified by the data element of an interaction
> request, it is not reasonable to label both as resources.

I want to emphasize the importance of this point.  

As a company that builds HTTP intermediaries, and is planning to use
RDF, we are *very* concerned about the pervasive use of fragment
identifiers in RDF.  Our intermediaries don't see the fragment id, and
therefore cannot take action based upon the resource being accessed.

I see that Aaron talked about this in Sean's message about EARL;

http://lists.w3.org/Archives/Public/www-rdf-interest/2002Apr/0134

MB
-- 
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com

Received on Thursday, 25 July 2002 20:42:06 UTC