Hi Dan, Sorry for a slow reply.
Strictly speaking, we should not be talking the technical details in [email protected], but it should be done in specx-*[email protected], because the later is IPR protected while the former is not. Not all the lists are active. Here is my shot in describing the tech related lists: > specs OpenID Specifications Discussions This is primarily the list for Working Group charter discussion. Anybody can speak here means it is not IPR protected and causes IPR contamination. Thus, even if somebody give a great idea here, it cannot be incorporated in any spec. > Openid-specs-ab Artifact Binding 1.0 Working Group This working group was formed to address the needs of mobile as well as higher security use cases. It is a chartered working group, so you can talk about technical details. (You have to write an IPR Contribution Agreement to join this list.) FYI, spec home repository is http://bitbucket.org/openid/ab/ and I have set up a sample implementation site (I needed it to test how the coding goes) at https://openid4.us (read it as "OpenID for us".) Although it aimed at mobile and higher security scenarios, it ended up to be much simpler than OpenID Authentication 2.0. It is quite close to spec freeze. I intend to do it by the end of May so that it will go into 45 days public review period. List Activity: Medium. > Openid-specs-ax Attribute Exchange 1.1 Working Group This working group was formed to make a small change to the AX1.0 so that it will fulfill all the functionality of SREG1.1. Specifically, it will define some basic mandatory profile parameters, privacy url, and fetch parameters. It is more like an errata. It should be finished in the same time-frame as in AB. This is a chartered working group. List activity: Low. > specs-council Specifications Council This list is only for specification council members. It is used to discuss if it would be a violation of IPR etc., when a working group is being formed. > Specs-cx Contract Exchange for dynamic exchange of legal contract > among the parties. This working group is set to define a way to create multi-party signed contract document that can be used as a token for data exchange as well as one of the proofing material at the court when needed. Since it has multi-party capability, user may be able to make attribute exchange among multiple parties at once, instead of going through the permission ceremony multiple time. It improves the usability as well as the level of protection for the user. This is a chartered working group. List Activity: Medium > specs-pape PAPE specification mailing list This is a chartered working group, but the work has finished and produced PAPE1.0 specification. > Specs-ui User Interface Working Group Specs list It is a working group that deals with the user experience improvement. This is a chartered working group. Did it help? =nat On Mon, May 17, 2010 at 7:54 PM, Dan Brickley <[email protected]> wrote: > On Mon, May 17, 2010 at 11:42 AM, Nat Sakimura <[email protected]> wrote: >> So, while David's "OpenID Connect" straw man has bunch of interesting >> properties, there has been substantial work done in parallel in OpenID >> Foundation's own >> Working Group. > > Great to see all this new work. I'd joined this openid-specs list > expecting it to be the place where such things happen, ... looking at > http://lists.openid.net/mailman/listinfo I see a pile of others > including I now notice Openid-specs-ab. > > Would it be possible for OpenID insiders to give a quick run-through > of these lists, ... which ones are active, where the work splits up > between them, the kinds of participation you're looking for, etc? > > For technical members of the wider 'social Web' community, concerned > to help with the evolution of OpenID, which of the following should we > be tracking or participating in? > > From http://lists.openid.net/mailman/listinfo -- > > Openid-adoption Committee to coordinate adoption, usability and > marketing strategies > board [no description available] > Code [no description available] > eu General OpenID discussions relating to Europe > general OpenID General Discussion > Openid-government Committee to Coordinate with National and Regional > Governments > legal Legal discussion around OpenID > marketing OpenID marketing > security Discussion around security and anti-phishing tactics > specs OpenID Specifications Discussions > Openid-specs-ab Artifact Binding 1.0 Working Group > Openid-specs-ax Attribute Exchange 1.1 Working Group > specs-council Specifications Council > Specs-cx Contract Exchange for dynamic exchange of legal contract > among the parties. > specs-pape PAPE specification mailing list > Specs-ui User Interface Working Group Specs list > user-experience OpenID user experience > votes DEPRECATED - Community and board votes happen here > > > cheers, > > Dan > -- Nat Sakimura (=nat) http://www.sakimura.org/en/ http://twitter.com/_nat_en _______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
