>> =drummond.reed wrote:
>>
>> As Martin has pointed out, the purpose of the CanonicalID element in XRDS
is
>> to support reassignable-to-persistent identifier mapping. Although this
is a
>> native function of XRI resolution (because XRI architecture was
explicitly
>> designed to address the reas
Hi Drummond,
On 5-Jun-07, at 9:44 AM, =drummond.reed wrote:
> I see no reason we can't add the rules for
> reassignable-URL-to-persistent-URL mapping as well, since it's
> simply a
> matter of the RP confirming that the persistent identifier is also
> authoritative for the XRDS.
>
> If we appro
=drummond.reed wrote:
>
> As Martin has pointed out, the purpose of the CanonicalID element in XRDS is
> to support reassignable-to-persistent identifier mapping. Although this is a
> native function of XRI resolution (because XRI architecture was explicitly
> designed to address the reassignable-
>David Recordon wrote:
>
>
>I don't want to say that I have the answers here, since I don't think I
>do. I do however see the following possible solutions:
>
>1) The core specification only talks about fragments in relation to
>Relying Parties, to the extent that they should be stripped from dis
