Request for consideration of AX 2.0 Working Group Charter Proposal
Henrik Biering
hb at netamia.com
Mon Jan 26 01:35:20 UTC 2009
Agree!
If the range of SReg attributes is expanded, however, I would suggest to
add phone number (incl. quality as suggested for email) and possibly
street+city address line(s). That would make it possible to fill in a
somewhat larger part of typical registration forms.
Iname: =henrik
Allen Tom wrote:
> Can we extend the scope to include patching SReg to include avatar
> image, and also details about the quality of the user's email address?
>
> AX also needs to be updated to allow RPs to pass the url of their
> privacy policy to the OP, this is equivalent to SReg's
> openid.sreg.policy_url.
>
> Because SReg does seem to be a bit more widely used, perhaps SReg can
> be positioned as a lightweight version of AX.
>
> Allen
>
> David Recordon wrote:
>> 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. :)
>>
>> --David
>>
>> ----- "Nat Sakimura" <sakimura at gmail.com> wrote:
>> >
>> >
>> >
>> > On Sat, Jan 24, 2009 at 4:02 AM, Breno de Medeiros
>> <breno at google.com <mailto:breno at google.com>> wrote:
>> >
>>
>> Unfortunately, not much to report except that most appear to agree in
>> > your last suggestion, which I parse as:
>> >
>> > Allow type.<alias> = type_schema_url to define a 'type
>> namespace'.
>> > Within that namespace it would then be possible to create an
>> > extensible schema based on plain string key-value pairs.
>> >
>> > We need to:
>> >
>> > 1. Get the blessing of specs council to form a WG. I believe we
>> have
>> > addressed all concerns raised in threads in the Wiki proposal
>> and I am
>> > not sure why I have not heard from specs council back. How do
>> we call
>> > for a vote on the WG formation?
>>
>>
>> > Right. I will kick the specs council for this one also.
>> > The board is aware that specs council has not been effective and
>> > starting to fix it. (There will be a board voting to start the
>> ammendment
>> > to the OpenID process shortly.)
>> >
>> > Guys, please raise your voices also from the community side.
>> >
>> > Dick, I think you still are a spec council member, so please start
>> > pinging other specs council members from inside.
>> >
>> > Process-wise, there are four more steps involved in startgin this WG.
>> >
>> > 1) Specs council's recommendation
>> > 2) Membership vote to form WG.
>> > 3) Contributors submitting IPR agreements for this WG.
>> > 4) OIDF to provide the post restricted ML and SVN repository for
>> the WG.
>> >
>> > Additionally, it would be good if OIDF could supply "write controlled"
>> > wiki just like OASIS Open does.
>> >
>> >
>> >
>>
>>
>> >
>> > 2. Start writing this spec, in particular hash out the parts
>> that are
>> > in agreement so that people can start cranking on this. :)
>>
>>
>> > Yes!
>> >
>> >
>>
>>
>> >
>> >
>> >
>> >
>> > On Fri, Jan 23, 2009 at 10:54 AM, Dick Hardt
>> <dick.hardt at gmail.com <mailto:dick.hardt at gmail.com>> wrote:
>> > > Hey Everyone
>> > > I dropped off the planet for a bit moving and getting my
>> world setup. Have
>> > > missed all the email threads on this.
>> > > What have I missed out on? :-)
>> > > I plan on participating heavy in the AX 2.0 spec myself.
>> > > -- Dick
>> > >
>> > > On Tue, Dec 23, 2008 at 12:12 PM, Allen Tom
>> <atom at yahoo-inc.com <mailto:atom at yahoo-inc.com>> wrote:
>> > >>
>> > >> I believe that one of the goals of AX 2.0 should be to maintain
>> > >> backwards compatible with AX 1.0 whenever possible.
>> > >>
>> > >> Allen
>> > >>
>> > >>
>> > >> Mike Jones wrote:
>> > >> > Can you add a clear statement to the draft charter that
>> implementations
>> > >> > already using AX 1.0 will remain compatible with the
>> output of this working
>> > >> > group? Or is backwards-compatibility with existing AX
>> implementations not a
>> > >> > goal of this work?
>> > >> >
>> > >> > -- Mike
>> > >> >
>> > >> > -----Original Message-----
>> > >> > From: specs-bounces at openid.net
>> <mailto:specs-bounces at openid.net>
>> [mailto:specs-bounces at openid.net
>> <mailto:specs-bounces at openid.net>] On
>> > >> > Behalf Of Breno de Medeiros
>> > >> > Sent: Thursday, December 18, 2008 6:18 PM
>> > >> > To: OpenID Specs Mailing List
>> > >> > Cc: dick at skip.com <mailto:dick at skip.com>;
>> hdknr at ic-tact.co.jp <mailto:hdknr at ic-tact.co.jp>;
>> mgraves at janrain.com <mailto:mgraves at janrain.com>
>> > >> > Subject: Request for consideration of Working Group
>> Charter Proposal
>> > >> >
>> > >> > I would like to submit the following proposal for a new
>> Working Group
>> > >> > charter to your consideration, following the OpenID IPR
>> process:
>> > >> >
>> > >> > The proposal charter is also available at:
>> > >> > http://wiki.openid.net/Working_Groups:AX_2.0
>> > >> >
>> > >> > OpenID Attribute Exchange 2.0 Working Group (AX 2.0)
>> > >> >
>> > >> >
>> > >> > Charter Proposal
>> > >> >
>> > >> > In accordance with the OpenID Foundation IPR policies and
>> procedures
>> > >> > this note proposes the formation of a new working group
>> chartered to
>> > >> > produce an OpenID specification. As per Section 4.1 of the
>> Policies,
>> > >> > the proposed charter is below (still liable to change
>> during this
>> > >> > feedback period).
>> > >> >
>> > >> >
>> > >> > I. Name
>> > >> >
>> > >> > Attribute Exchange Extension Working Group (AX)
>> > >> >
>> > >> >
>> > >> > II. Statement of Purpose
>> > >> >
>> > >> > Produce an updated version of the Attribute Exchange
>> Extension.
>> > >> >
>> > >> >
>> > >> > III. Scope
>> > >> >
>> > >> > Update the Attribute Exchange Extension to include support for
>> > >> > identified needs. Currently identified needs:
>> > >> >
>> > >> > * Provide mechanisms for RP to require, and the OP to
>> assert,
>> > >> > claims about the quality of the attributes.
>> > >> > * Create an extensible registry of claim types, such as
>> > >> > axschema.org <http://axschema.org> for attribute types.
>> The registry should also provide
>> > >> > non-normative guidance on how claims can be validated,
>> which will
>> > >> > depend on the nature of attribute type as well as claim type.
>> > >> > * Introduce a new request/response mode which, unlike
>> fetch and
>> > >> > store, allows for both transmittal of some values and
>> request of
>> > >> > others. The transmittal not necessarily has the
>> significance of a
>> > >> > "store" request (could be informative, or for requesting
>> validation).
>> > >> > * Introduce a direct communication method in both
>> directions
>> > >> > (OP<->RP), supported via discovery, for bulk exchange of
>> attributes
>> > >> > about (potentially) multiple users.
>> > >> >
>> > >> >
>> > >> > IV. Specifications
>> > >> >
>> > >> > OpenID Attribute Exchange 2.0
>> > >> >
>> > >> >
>> > >> > V. Anticipated audience
>> > >> >
>> > >> > All those interested in the obtaining attributes about users
>> > >> > authenticated via OpenID.
>> > >> >
>> > >> >
>> > >> > VI. Language of business
>> > >> >
>> > >> > English.
>> > >> >
>> > >> >
>> > >> > VII. Method of work
>> > >> >
>> > >> > Mailing list discussion. Posting of intermediate drafts in
>> the OpenID
>> > >> > Wiki. Virtual conferencing on an ad-hoc basis.
>> > >> >
>> > >> >
>> > >> > VIII. Basis for completion of the activity
>> > >> >
>> > >> > The Attribute Exchange 2.0 spec final draft is delivered
>> and the form
>> > >> > of management and maintenance of the registry is established.
>> > >> >
>> > >> >
>> > >> > Background Information
>> > >> > I. Related Work
>> > >> >
>> > >> > Attribute Exchange (1.0), and Simple Registration.
>> > >> > II. Initial Membership
>> > >> >
>> > >> > * Tom Allen, atom at yahoo-inc.com
>> <mailto:atom at yahoo-inc.com>. Yahoo! Inc (editor)
>> > >> > * Mike Graves, mgraves at janrain.com
>> <mailto:mgraves at janrain.com>, JanRain, Inc.
>> > >> > * Dick Hardt, dick at skip.com <mailto:dick at skip.com>.
>> Sxip Identity.
>> > >> > * Breno de Medeiros, breno at google.com
>> <mailto:breno at google.com>. Google, Inc. (editor)
>> > >> > * Hideki Nara, hdknr at ic-tact.co.jp
>> <mailto:hdknr at ic-tact.co.jp>, Tact Communications
>> > >> > * Nat Sakimura, n-sakimura at nri.co.jp
>> <mailto:n-sakimura at nri.co.jp> (editor)
>> > >> >
>> > >> >
>> > >> >
>> > >> >
>> > >> > --
>> > >> > --Breno
>> > >> >
>> > >> > +1 (650) 214-1007 desk
>> > >> > +1 (408) 212-0135 (Grand Central)
>> > >> > MTV-41-3 : 383-A
>> > >> > PST (GMT-8) / PDT(GMT-7)
>> > >> > _______________________________________________
>> > >> > specs mailing list
>> > >> > specs at openid.net <mailto:specs at openid.net>
>> > >> > http://openid.net/mailman/listinfo/specs
>> > >> >
>> > >> > _______________________________________________
>> > >> > specs mailing list
>> > >> > specs at openid.net <mailto:specs at openid.net>
>> > >> > http://openid.net/mailman/listinfo/specs
>> > >> >
>> > >>
>> > >> _______________________________________________
>> > >> specs mailing list
>> > >> specs at openid.net <mailto:specs at openid.net>
>> > >> http://openid.net/mailman/listinfo/specs
>> > >
>> > >
>> >
>> >
>> >
>> >
>> --
>> >
>> > --Breno
>> >
>> > +1 (650) 214-1007 desk
>> > +1 (408) 212-0135 (Grand Central)
>> > MTV-41-3 : 383-A
>> > PST (GMT-8) / PDT(GMT-7)
>> > _______________________________________________
>> > specs mailing list
>> > specs at openid.net <mailto:specs at openid.net>
>> > http://openid.net/mailman/listinfo/specs
>> >
>>
>>
>> >
>>
>> > --
>> > Nat Sakimura (=nat)
>> > http://www.sakimura.org/en/
>> >
>> > _______________________________________________ specs mailing list
>> specs at openid.net http://openid.net/mailman/listinfo/specs
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> specs mailing list
>> specs at openid.net
>> http://openid.net/mailman/listinfo/specs
>>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> specs mailing list
> specs at openid.net
> http://openid.net/mailman/listinfo/specs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20090126/9d91bd31/attachment-0002.htm>
More information about the specs
mailing list