AX and Artifact Binding Charter Proposal

John Bradley john.bradley at wingaa.com
Sat Nov 14 02:40:33 UTC 2009


We could do a template for lang and jurisdiction.

The other way of dealing with lang is is via content negotiation or  
links in the HTML documents.

I don't know that it is worth complicating the simple case with  
templates.

Having different elements is also a path to madness.

Is this a feature that OP would use?

John B.
On 2009-11-13, at 11:30 PM, Allen Tom wrote:

> Keeping the request size small and having RPs implement discovery  
> are both good things.
>
> Also privacy policies, as well as other RP metadata (icons,  
> descriptions) all make sense to put into discovery.
>
> If the RP is behind a firewall and isn't accessible to the OP, then  
> hopefully OPs that care about RP metadata can just indicate to the  
> user that the metadata was not found.
>
> The proposed XRDS schema looks reasonable. We might want to have  
> different urls for different languages/jurisdictions, although  
> that's probably overkill.
>
> Allen
>
>
> John Bradley wrote:
>> See folks spec work can be fun:)
>>
>> John B.
>> On 2009-11-13, at 10:29 PM, Breno de Medeiros wrote:
>>
>>> Going once, going twice ...
>>>
>>> On Fri, Nov 13, 2009 at 5:26 PM, John Bradley <john.bradley at wingaa.com 
>>> > wrote:
>>>> Any preference for a namespace?
>>>>
>>>> We could reuse the openid one that we have for openID 1.1 delegate.
>>>>
>>>> xmlns:openid="http://openid.net/xmlns/1.0"
>>>>
>>>> <Service>
>>>> <Type>http://specs.openid.net/auth/2.0/return_to</Type>
>>>> <URI>http://consumer.example.com/return</URI>
>>>> <openid:Policy_url>http://example.com/privacy-policy.html</ 
>>>> openid:Policy_url>
>>>> <openid:TOS>http://example.com/terms-of-service.html</openid:TOS>
>>>> </Service>
>>>>
>>>> I should note that this wont work for RP's behind a firewall  
>>>> being accessed
>>>> from a LAN or VPN.
>>>>
>>>> I am going to observe that if you are all ready on the LAN the  
>>>> privacy
>>>> policy can be dealt with out of band if necessary.
>>>>
>>>> I am not emotionally attached to the namespace or element names  
>>>> if someone
>>>> has something else they like.
>>>>
>>>> John B.
>>>> On 2009-11-13, at 9:51 PM, Breno de Medeiros wrote:
>>>>
>>>>>>
>>>>>> While we are at it do we want to also publish a TOS URI?
>>>>>>
>>>>>
>>>>> Don't see why not.
>>>>>
>>>>> -- 
>>>>> --Breno
>>>>>
>>>>> +1 (650) 214-1007 desk
>>>>> +1 (408) 212-0135 (Grand Central)
>>>>> MTV-41-3 : 383-A
>>>>> PST (GMT-8) / PDT(GMT-7)
>>>>
>>>>
>>>
>>>
>>>
>>> -- 
>>> --Breno
>>>
>>> +1 (650) 214-1007 desk
>>> +1 (408) 212-0135 (Grand Central)
>>> MTV-41-3 : 383-A
>>> PST (GMT-8) / PDT(GMT-7)
>>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2486 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20091113/ef59a08e/attachment-0001.bin>


More information about the specs mailing list