[OpenID] Open Challenge to webfinger and XRD

[John Bradley]

The point is that a URI can name anything.  If you want to start  
assigning semantic significance to them you open up a big can of worms.

 From the point of view of the XRD the Subject is a URI,  any valid  
absolute URI.

If you don't want the URI that you are fetching the XRD from then  
assign another, that's why there is a <Subject>!

You can use any URI scheme you like, you can add fragments to  
distinguish them if you want,

You can even paint it red for Drummond.

The way you tell what a XRD is about is by looking at the <Type>  
elements not trying to parse the URI in the subject.

If the subject of Drummond's host-meta is http://drummond.com/#red and  
John Panzer's is http://panzer.com/#blue  it shouldn't make any  
difference to XRD, or anything that uses XRD unless they are trying to  
do an exact match for some reason.

The webfinger folks may have a different opinion, but the discussion  
of Colour representation is no more silly than the one about what to  
name the XRD.

The resource owner names the XRD.  They can name it with any valid  
URI  they like as long as it suites there purpose and it's signature  
verifies according to some trust profile.

John B.

On 2009-10-21, at 8:16 PM, SitG Admin wrote:

>> You guys crack me up :)
>> who says standards groups don't have a sense of humor.
>
> Anyone who understands the interconnectedness of what we're saying?
>
> I'm just a poor developer, inferior to Peter even, who has no clue  
> about XRD and no idea how any of this color stuff relates to it -  
> but I will trust that, if I contribute from my own area(s) of  
> expertise, others will work out how to make it help with XRD :)
>
> -Shade
> _______________________________________________
> general mailing list
> general at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-general

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2468 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20091021/453c000a/attachment.bin>