It is probably not good form to start using URI under http://schemas.opeinid.net
without permission.
Brenno and I are putting together a WG proposal for a registry of such
things including AX attributes.
We can put them in xrdstype.net but that is more informational than
official.
I don't have anything against those URI though they may be better as
part of the AX uri than as separate privacy ones.
John B.
On 2-Jul-09, at 7:53 PM, Joseph A Holsten wrote:
On 1-Jul-09, at 5:21 PM, Breno de Medeiros wrote:
Even much easier is to define a <Type> that can be discovered in
the XRDS document, and requires no changes to AX libraries.
On Jul 1, 2009, at 10:13 PM, John Bradley wrote:
I think we agree. It is another URL for the registry:)
OK, what should those type URLs be? PAPE uses XRDS type like <http://schemas.openid.net/pape/policies/2007/06/phishing-resistant
>, so how about these two:
http://schemas.openid.net/privacy/policies/2009/07/privacy
http://schemas.openid.net/privacy/policies/2009/07/terms
Is there existing language defining the semantics of these URI
types? Is it necessary to write this from scratch?
Where do we need to document this information? Is someone running <http://xrdstype.net
>? Would it be enough to just put these there?
Is there anything else that needs to get to document this behaviour
for implementors?
http://josephholsten.com
_______________________________________________
specs mailing list
[email protected]
http://openid.net/mailman/listinfo/specs
