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 <[email protected]> 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 accessedfrom a LAN or VPN.I am going to observe that if you are all ready on the LAN the privacypolicy can be dealt with out of band if necessary.I am not emotionally attached to the namespace or element names if someonehas 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)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
