AX and Artifact Binding Charter Proposal

John Bradley john.bradley at wingaa.com
Sat Nov 14 01:26:04 UTC 2009


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)

-------------- 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/4137f810/attachment.bin>


More information about the specs mailing list