<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>This has been on my list to kick to the specs council but I've also been waiting for Dick to reengage since he's been such a core driver of the AX spec in the past. :)<br><br>--David<br><br>----- "Nat Sakimura" <sakimura@gmail.com> wrote:
<br>> <br>> <br>> <div class="gmail_quote">> On Sat, Jan 24, 2009 at 4:02 AM, Breno de Medeiros <span dir="ltr"><<a href="mailto:breno@google.com" target="_blank">breno@google.com</a>></span> wrote:<br>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Unfortunately, not much to report except that most appear to agree in<br>>
your last suggestion, which I parse as:<br>>
<br>>
Allow type.<alias> = type_schema_url to define a 'type namespace'.<br>>
Within that namespace it would then be possible to create an<br>>
extensible schema based on plain string key-value pairs.<br>>
<br>>
We need to:<br>>
<br>>
1. Get the blessing of specs council to form a WG. I believe we have<br>>
addressed all concerns raised in threads in the Wiki proposal and I am<br>>
not sure why I have not heard from specs council back. How do we call<br>>
for a vote on the WG formation?</blockquote><div><br>> Right. I will kick the specs council for this one also. <br>> The board is aware that specs council has not been effective and <br>> starting to fix it. (There will be a board voting to start the ammendment <br>>
to the OpenID process shortly.) <br>> <br>> Guys, please raise your voices also from the community side. <br>> <br>> Dick, I think you still are a spec council member, so please start <br>> pinging other specs council members from inside. <br>>
<br>> Process-wise, there are four more steps involved in startgin this WG. <br>> <br>> 1) Specs council's recommendation<br>> 2) Membership vote to form WG. <br>> 3) Contributors submitting IPR agreements for this WG. <br>> 4) OIDF to provide the post restricted ML and SVN repository for the WG. <br>>
<br>> Additionally, it would be good if OIDF could supply "write controlled" <br>> wiki just like OASIS Open does. <br>> <br>> <br>> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>>
<br>>
2. Start writing this spec, in particular hash out the parts that are<br>>
in agreement so that people can start cranking on this. :)</blockquote><div><br>> Yes!<br>> <br>> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>>
<div><div></div><div class="Wj3C7c">> <br>>
<br>>
<br>>
On Fri, Jan 23, 2009 at 10:54 AM, Dick Hardt <<a href="mailto:dick.hardt@gmail.com" target="_blank">dick.hardt@gmail.com</a>> wrote:<br>>
> Hey Everyone<br>>
> I dropped off the planet for a bit moving and getting my world setup. Have<br>>
> missed all the email threads on this.<br>>
> What have I missed out on? :-)<br>>
> I plan on participating heavy in the AX 2.0 spec myself.<br>>
> -- Dick<br>>
><br>>
> On Tue, Dec 23, 2008 at 12:12 PM, Allen Tom <<a href="mailto:atom@yahoo-inc.com" target="_blank">atom@yahoo-inc.com</a>> wrote:<br>>
>><br>>
>> I believe that one of the goals of AX 2.0 should be to maintain<br>>
>> backwards compatible with AX 1.0 whenever possible.<br>>
>><br>>
>> Allen<br>>
>><br>>
>><br>>
>> Mike Jones wrote:<br>>
>> > Can you add a clear statement to the draft charter that implementations<br>>
>> > already using AX 1.0 will remain compatible with the output of this working<br>>
>> > group? Or is backwards-compatibility with existing AX implementations not a<br>>
>> > goal of this work?<br>>
>> ><br>>
>> > -- Mike<br>>
>> ><br>>
>> > -----Original Message-----<br>>
>> > From: <a href="mailto:specs-bounces@openid.net" target="_blank">specs-bounces@openid.net</a> [mailto:<a href="mailto:specs-bounces@openid.net" target="_blank">specs-bounces@openid.net</a>] On<br>>
>> > Behalf Of Breno de Medeiros<br>>
>> > Sent: Thursday, December 18, 2008 6:18 PM<br>>
>> > To: OpenID Specs Mailing List<br>>
>> > Cc: <a href="mailto:dick@skip.com" target="_blank">dick@skip.com</a>; <a href="mailto:hdknr@ic-tact.co.jp" target="_blank">hdknr@ic-tact.co.jp</a>; <a href="mailto:mgraves@janrain.com" target="_blank">mgraves@janrain.com</a><br>>
>> > Subject: Request for consideration of Working Group Charter Proposal<br>>
>> ><br>>
>> > I would like to submit the following proposal for a new Working Group<br>>
>> > charter to your consideration, following the OpenID IPR process:<br>>
>> ><br>>
>> > The proposal charter is also available at:<br>>
>> > <a href="http://wiki.openid.net/Working_Groups:AX_2.0" target="_blank">http://wiki.openid.net/Working_Groups:AX_2.0</a><br>>
>> ><br>>
>> > OpenID Attribute Exchange 2.0 Working Group (AX 2.0)<br>>
>> ><br>>
>> ><br>>
>> > Charter Proposal<br>>
>> ><br>>
>> > In accordance with the OpenID Foundation IPR policies and procedures<br>>
>> > this note proposes the formation of a new working group chartered to<br>>
>> > produce an OpenID specification. As per Section 4.1 of the Policies,<br>>
>> > the proposed charter is below (still liable to change during this<br>>
>> > feedback period).<br>>
>> ><br>>
>> ><br>>
>> > I. Name<br>>
>> ><br>>
>> > Attribute Exchange Extension Working Group (AX)<br>>
>> ><br>>
>> ><br>>
>> > II. Statement of Purpose<br>>
>> ><br>>
>> > Produce an updated version of the Attribute Exchange Extension.<br>>
>> ><br>>
>> ><br>>
>> > III. Scope<br>>
>> ><br>>
>> > Update the Attribute Exchange Extension to include support for<br>>
>> > identified needs. Currently identified needs:<br>>
>> ><br>>
>> > * Provide mechanisms for RP to require, and the OP to assert,<br>>
>> > claims about the quality of the attributes.<br>>
>> > * Create an extensible registry of claim types, such as<br>>
>> > <a href="http://axschema.org" target="_blank">axschema.org</a> for attribute types. The registry should also provide<br>>
>> > non-normative guidance on how claims can be validated, which will<br>>
>> > depend on the nature of attribute type as well as claim type.<br>>
>> > * Introduce a new request/response mode which, unlike fetch and<br>>
>> > store, allows for both transmittal of some values and request of<br>>
>> > others. The transmittal not necessarily has the significance of a<br>>
>> > "store" request (could be informative, or for requesting validation).<br>>
>> > * Introduce a direct communication method in both directions<br>>
>> > (OP<->RP), supported via discovery, for bulk exchange of attributes<br>>
>> > about (potentially) multiple users.<br>>
>> ><br>>
>> ><br>>
>> > IV. Specifications<br>>
>> ><br>>
>> > OpenID Attribute Exchange 2.0<br>>
>> ><br>>
>> ><br>>
>> > V. Anticipated audience<br>>
>> ><br>>
>> > All those interested in the obtaining attributes about users<br>>
>> > authenticated via OpenID.<br>>
>> ><br>>
>> ><br>>
>> > VI. Language of business<br>>
>> ><br>>
>> > English.<br>>
>> ><br>>
>> ><br>>
>> > VII. Method of work<br>>
>> ><br>>
>> > Mailing list discussion. Posting of intermediate drafts in the OpenID<br>>
>> > Wiki. Virtual conferencing on an ad-hoc basis.<br>>
>> ><br>>
>> ><br>>
>> > VIII. Basis for completion of the activity<br>>
>> ><br>>
>> > The Attribute Exchange 2.0 spec final draft is delivered and the form<br>>
>> > of management and maintenance of the registry is established.<br>>
>> ><br>>
>> ><br>>
>> > Background Information<br>>
>> > I. Related Work<br>>
>> ><br>>
>> > Attribute Exchange (1.0), and Simple Registration.<br>>
>> > II. Initial Membership<br>>
>> ><br>>
>> > * Tom Allen, <a href="mailto:atom@yahoo-inc.com" target="_blank">atom@yahoo-inc.com</a>. Yahoo! Inc (editor)<br>>
>> > * Mike Graves, <a href="mailto:mgraves@janrain.com" target="_blank">mgraves@janrain.com</a>, JanRain, Inc.<br>>
>> > * Dick Hardt, <a href="mailto:dick@skip.com" target="_blank">dick@skip.com</a>. Sxip Identity.<br>>
>> > * Breno de Medeiros, <a href="mailto:breno@google.com" target="_blank">breno@google.com</a>. Google, Inc. (editor)<br>>
>> > * Hideki Nara, <a href="mailto:hdknr@ic-tact.co.jp" target="_blank">hdknr@ic-tact.co.jp</a>, Tact Communications<br>>
>> > * Nat Sakimura, <a href="mailto:n-sakimura@nri.co.jp" target="_blank">n-sakimura@nri.co.jp</a> (editor)<br>>
>> ><br>>
>> ><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>>
>> > _______________________________________________<br>>
>> > specs mailing list<br>>
>> > <a href="mailto:specs@openid.net" target="_blank">specs@openid.net</a><br>>
>> > <a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>>
>> ><br>>
>> > _______________________________________________<br>>
>> > specs mailing list<br>>
>> > <a href="mailto:specs@openid.net" target="_blank">specs@openid.net</a><br>>
>> > <a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>>
>> ><br>>
>><br>>
>> _______________________________________________<br>>
>> specs mailing list<br>>
>> <a href="mailto:specs@openid.net" target="_blank">specs@openid.net</a><br>>
>> <a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>>
><br>>
><br>>
<br>>
<br>>
<br>>
</div></div>--<br>>
<div><div></div><div class="Wj3C7c">> --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>>
_______________________________________________<br>>
specs mailing list<br>>
<a href="mailto:specs@openid.net" target="_blank">specs@openid.net</a><br>>
<a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>>
</div></div></blockquote></div><br>> <br clear="all"><br>> -- <br>> Nat Sakimura (=nat)<br>> <a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>>
<br>> _______________________________________________
specs mailing list
specs@openid.net
http://openid.net/mailman/listinfo/specs
</div></body></html>