[OpenID] host-meta and "acct:"

[Will Norris]

We're not hiding anything.  Non-whitespace characters are required to  
make the meaning of a particular value unambiguous.  Keep in mind that  
the goal of making the <Subject> element optional is not to  
necessarily allow for "Anonymous XRDs"... the goal is to allow the  
subject of the XRD to be identified by means other than the <Subject>  
element.  I'm not completely sure what to make of an XRD that does not  
identify its subject (by the <Subject> element or otherwise).  There  
may be a use case for it, but nothing immediately comes to mind.

-will

On Nov 4, 2009, at 7:45 AM, Santosh Rajan wrote:

> Maybe thats a problem with the XRD Spec you guys really need to  
> reconsider.
>
> How long are you guys going to keep hiding behind such logic?
>
>
> On Wed, Nov 4, 2009 at 9:11 PM, Will Norris <will at willnorris.com>  
> wrote:
>
>>
>> On Nov 4, 2009, at 7:28 AM, SitG Admin wrote:
>>
>> If you really want to do that, why don't you allow for an  
>> "Anonymous XRD"
>>>> who's Subject is empty?
>>>>
>>>
>>> Why require all XRD's to have a Subject field, if it can be empty?  
>>> Can't
>>> it just be omitted entirely, saving bandwidth from transmitting an  
>>> extra 19
>>> (plus whitespace) bytes?
>>>
>>> If it can be empty, it can be omitted - as I've said before, the  
>>> lack of a
>>> field can implicitly be taken as the emptiness of a field.
>>>
>>
>>
>> you cannot have an empty subject.  See section 1.5.2:
>>
>> Unless otherwise noted in this specification or particular  
>> profiles, all
>>> URIs in XRD documents MUST consist of at least one non-whitespace  
>>> character.
>>>
>>
>> -will
>> _______________________________________________
>> general mailing list
>> general at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-general
>>
>
>
>
> -- 
> http://hi.im/santosh