Great!<br><br><div class="gmail_quote">On Wed, Jul 15, 2009 at 12:09 PM, John Bradley <span dir="ltr"><<a href="mailto:john.bradley@wingaa.com">john.bradley@wingaa.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I have done some work on the proposal.<div class="im"><br>
<a href="http://wiki.openid.net/ProposalForAURLSchemaRegistry" target="_blank">http://wiki.openid.net/ProposalForAURLSchemaRegistry</a><br>
<br></div>
I will fill in my proposal for the the process by the weekend.<br>
<br>
There would be a open list for people to make formal registry requests.<br>
<br>
The WG would have a list for people who have joined and made there IPR declaration.<br>
The proposal would have 4 weeks to get at-least three +1 votes.<br>
If it receives no -1 it would pass.<br>
<br>
If there are -1 votes then the chair of the WG would hold a vote on the list.<br>
Two thirds of the cast votes must be +1 to pass.<br>
<br>
There will be an experimental status using <a href="http://experimental.openid.net" target="_blank">http://experimental.openid.net</a>.<br>
People will need to specify if they are applying regular or Experimental.<br>
The Bar would be lower for experimental but the applicant would need to reapply yearly to keep it in the registry.<br>
<br>
John B.<div><div></div><div class="h5"><br>
<br>
On 14-Jul-09, at 2:05 PM, Breno de Medeiros wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ping.<br>
<br>
On Fri, Jul 10, 2009 at 11:41 AM, John Bradley<<a href="mailto:john.bradley@wingaa.com" target="_blank">john.bradley@wingaa.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Breno,<br>
<br>
It's on my list for this weekend.<br>
<br>
I think Andrew's idea is a interesting solution.<br>
<br>
I don't think that overloading the <Type> attribute is a good long term<br>
solution.<br>
<br>
I hope we could do something better for XRD 1.0 discovery to describe the<br>
features of a OP.<br>
<br>
In the short term overloading <Type> is something we can do.<br>
<br>
The other pressing issues for AX are:<br>
1 Registering a <Type> for discovering the RP privacy policy<br>
2 Registering a <Type> for discovering the RP Terms of Service.<br>
3 Having a way for the RP to know if the OP supports if_available.<br>
<br>
The last one is important to deal with the fact that some OP ignore<br>
if_available in requests and only give the user the choice to return the<br>
attributes that are requested as "REQUIRED".<br>
<br>
All the OPs could agree on a single way to interpret AX requests but that is<br>
a touch optimistic:)<br>
<br>
Having a way for a RP to differentiate between OPs operating on different<br>
theories would be good for RPs.<br>
<br>
John B.<br>
On 10-Jul-09, at 1:35 PM, <a href="mailto:general-request@openid.net" target="_blank">general-request@openid.net</a> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Date: Fri, 10 Jul 2009 10:00:05 -0700<br>
From: Breno de Medeiros <<a href="mailto:breno@google.com" target="_blank">breno@google.com</a>><br>
Subject: Re: [OpenID] Why use SREG instead of AX?<br>
To: Andrew Arnott <<a href="mailto:andrewarnott@gmail.com" target="_blank">andrewarnott@gmail.com</a>><br>
Cc: <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
Message-ID:<br>
<<a href="mailto:29fb00360907101000n77f57032wdd0635a60b660ff@mail.gmail.com" target="_blank">29fb00360907101000n77f57032wdd0635a60b660ff@mail.gmail.com</a>><br>
Content-Type: multipart/alternative;<br>
boundary=0016369205b372e192046e5ce7b4<br>
<br>
--0016369205b372e192046e5ce7b4<br>
Content-Type: text/plain; charset=ISO-8859-1<br>
Content-Transfer-Encoding: 7bit<br>
<br>
For one, it would be interesting if someone with expertise on how to<br>
create<br>
lightweight processes for registration would clarify the language in that<br>
wiki document. Hopefully, it would be possible to define a process that<br>
exempts the OIDF from the burden of having to impose the current IPR<br>
policy<br>
on each contributor. (I had hoped JBradley would take that on, but he has<br>
plenty on his hands at this point).<br>
Once that wiki page is in good shape we could spam specs@ to bless it and<br>
then we can get started right away. There is even an initial understanding<br>
to use the domain name <a href="http://schemas.openid.net" target="_blank">schemas.openid.net</a> and to host each registered URL<br>
at that domain with a description of the wire format for the attribute. So<br>
once this is up, I think progress could be made quickly.<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
<br>
-- <br>
--Breno<br>
<br>
+1 (650) 214-1007 desk<br>
+1 (408) 212-0135 (Grand Central)<br>
MTV-41-3 : 383-A<br>
PST (GMT-8) / PDT(GMT-7)<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>--Breno<br><br>+1 (650) 214-1007 desk<br>+1 (408) 212-0135 (Grand Central)<br>MTV-41-3 : 383-A <br>PST (GMT-8) / PDT(GMT-7)<br>