[OpenID] fragment identifiers

[Andrew Tomlinson]

Wasn't part of the problem that fragments were proposed as a solution to
identifier recycling:

See http://openid.net/wiki/index.php/Identifier_Recycling or more
specifically http://openid.net/wiki/index.php/Identifier_Recycling/Fragments

So if fragments are given some additional meaning in an identity url e.g.
#me vs #notme then you can't use them for this purpose.

May just have been my confusion and I have entirely the wrong end of the
stick...

Andrew

> ________________________________
>
> From: Story Henry [mailto:henry.story at bblfish.net]
> Sent: Sun 8/5/2007 12:18 PM
> To: Peter Williams
> Cc: general at openid.net
> Subject: Re: fragment identifiers
>
>
>
> Hi Peter,
>
> given that you are having trouble understanding something, bear with
> me if I don't understand your misunderstanding correctly.
> I'll try my best here....
>
> On 5 Aug 2007, at 19:50, Peter Williams wrote:
>
>> I think I now half-understand a thread of discussion that started
>> some while ago: addressing fragment-ids on OpenID URIs, in a FOAF/
>> RDF context. The topic seemed to center on the question: how should
>> the OpenID normalization function handle URI fragments?
>
> Ok so I am not sure what the normalization function is. Assuming you
> mean the process which takes the string entered in an OpenId box on a
> site I want to log into and turns it into a full URL. So I could
> enter openid.sun.com/bblfish and it would transform that, normalize
> it to http://openid.sun.com/bblfish
>
> Next I am not sure how the problem of URI fragments gets involved
> here. I think you are referring to the widely accepted usage that one
> should identify non information resources with URIs ending in
> fragment identifiers in RDF.  [1] This makes it easy to find the
> information about those objects by doing a GET on the URI (http get's
> always remove the hash).
>
...