IdCommons - User contributions [en]

Claims Agent Charter

2011-02-02T17:39:26Z

DrummondReed: /* Current Membership */

'''Version 1.6'''
=== Status ===
* 16-Jan-2011: v1.6: ptrevithick: added a link to the new claims-agent mailing list
* 13-Jan-2011: v1.5: ptrevithick: added a mention that anyone can login with any OpenID and add their names to the participants list
* 10-Jan-2011: v1.4: craigwi: incorporated feedback from conference call
* 09-Jan-2011: v1.3: craigwi: incorporate feedback from early reviewers
* 07-Jan-2011: v1.2: craigwi: added initial scenarios; reworked language around components .vs. active client; other clarifications.
* 04-Jan-2011: v1.1: ptrevithick: renamed from Claims Broker to Claims Agent
* 30-Dec-2010: v1.0: ptrevithick: charter circulated for discussion period within Stewards Council

=== Name ===

Claims Agent Working Group

=== Purpose ===

The purpose of this working group is to (i) create a forum for the development of standards-based, interoperable, verified claims agent implementations (which would include both open source and commercial components), to (ii) initially focus on specific scenarios that the community and customers work together to implement and deploy end-to-end and (iii) provide funding and other incentives for the development of open source components.
A verified claims agent is a set of software components that allows the user to utilize claim-sets from different sources at relying parties (RPs) of their choosing, under their control, using technology that helps to protect their privacy and helps to ensure the security of the system end to end. Verified claims come from sources that do the verification and digitally sign the claims-sets; the agent itself does not do the verification and does not re-sign the claims or sets. The agent has the following characteristics:
* MUST be able to be used with an unmodified browser (includes all types of desktop and mobile devices; support for specific platforms and browsers TBD); this capability would be supported by a “cloud hosted” agent and would support many, but not all of the possible privacy and security features.
* MUST be possible to configure the system to prevent claims providers from being able to trivially track the use of a claims-set. MUST also be possible to configure the system to prevent trivial correlation of claims-sets delivered to different recipients. Both of these capabilities can be achieved by so-called minimal disclosure technologies based on zero knowledge cryptographic techniques or equivalent techniques.
* MUST provide mechanisms to mitigate the theft or lending of claims sets; e.g., claims sets could be cryptographically bound to a device such as a TPM chip, smart card, or phone.
* MAY include components downloaded to the user’s desktop or mobile device (e.g., a browser extension) to provide additional privacy and security features; e.g., used to invoke the agent service while reducing the phishing attack surface; store information local to the device; prevent the agent service from observing the flow of claims from provider to RP.
* Components downloaded to the user’s desktop or mobile device MAY also enhance the user experience, but MUST remain aligned and conceptually compatible with the user experience provided by the agent service.
* Architecture MUST support applications on a desktop or mobile device other than a browser; initial development efforts MAY not.
* MAY support existing specifications and protocols such as WS-Federation, OpenID, SAML and IMI
* MAY be used to provide claims used for authentication
* MAY include the ability to provide current or past claims (and convey which is which)
* MUST enable the exchange of variable claims which means that in some scenarios the process of retrieving claims-sets includes additional parameters that indicate something about the context of the request

=== Overall Scope ===

* To create a verified claims agent development community that includes open source, research and commercial efforts.
* To build liason relationships with related efforts at OpenID Artifact Binding WG, IETF (e.g., OAuth), Kantara (e.g. ULX and CI), Mozilla (e.g. Account Manager) and W3C (new initiatives being considered). Where possible to work with these organizations on their respective specs, rather than creating new specs.
* To build and test together at least one complete implementation of all claims agent components, including multiple cloud hosted agents and components for a wide range of desktop and mobile devices (specific systems and versions support TBD). May be a mix of open source and commercial components. The binaries of the commercially developed components must be available under RANDZ terms. All desktop and mobile device components must be compatible with all of the cloud agent instances.
* To fund one complete, open source claims agent implementation including a cloud agent (e.g., in Java, or .NET, or other suitable language) and components for desktop and mobile devices. All open source code will be licensed under TBD license (most likely Apache 2.0) and resulting components must be interoperable with any commercially developed components.
* To support and fund interoperability testing of claims agent components developed by the working group
* To participate in discussions on: Trust frameworks that support the verified claims agent; relevant changes in laws and regulations; feedback from members of the privacy community.
* Ensure that the architecture and all components developed enable expansion of the initial target scenarios to include commercial sources of claims, claims orchestration and aggregation, and claims marketplaces (where there may be transaction costs per claims exchange).
* Consider how the architecture and components developed can enable value added services on both the cloud agent and the desktop and mobile devices.

=== Initial Target Scenario Characteristics ===

* Claims come from government, health and education sources and are verified by some source-dependent means.
* The expectation is that there is no cost to the citizen to use the claims and very limited cost, if any, to the organizations who consume them.
* Supported RPs include those at the same institutions that provided the claims, different agencies at different levels of governments and across national borders, as well as commercial organizations.
* Claims are exchanged in a way that helps protect the privacy of the citizen and security requirements of the claims provider (specific mechanisms employed depend on the scenario).
* Support for authentication would be limited to pre-allocated identifiers such as email (i.e., not dynamically allocated pseudonyms)

=== Principles ===

See Identity Commons [[Purpose And Principles]]

=== Practices ===

* We plan to collaborate using an Identity Commons-hosted mailing list
* We plan to contribute source code to a common repository. This repository will likely be a new repository in a larger effort such as [http://www.outercurve.org/ Outercurve Foundation] or [http://www.eclipse.org Eclipse].
* We plan to collaborate with the Identity Commons OSIS WG for interoperability testing.
* Specifications to be standardized would be submitted to standards groups such as OASIS, W3C, IETF and OpenID.
* We plan to seek corporate funding for the open source code and interoperability phases of this work. As Identity Commons evolves to support directed funding, this funding will eventually be to Identity Commons and, after an overhead fee is extracted, the balance pass to this working group.

=== Requirements of Participation and How to Join ===

To show interest in joining after this WG is approved by the Identity Commons Stewards Council, just add your name to the list below. This WG will be open to all.

=== Licenses and/or Restrictions on Usage of Work Product ===
* Open Web Foundation for specs
* TBD: likely Apache 2.0 for code

=== Current Deliverables and Milestones ===

To be determined.

=== Current Meeting Schedule ===

To be determined.

=== Current Membership ===
This group has been proposed by Paul Trevithick. The following people have indicated interest in participating.

* Mikaël Ates
* John Bradley
* Ariel Gordon (Microsoft)
* Iain Henderson (Mydex)
* Rainer Hörbe
* Mike McIntosh (Azigo)
* Susan Morrow (Avoco)
* Andrew Nash
* Axel Nennker
* Søren Peter Nielsen (DK Govt)
* Dale Olds (Novell)
* Sandy Porter (Avoco)
* Drummond Reed (Data Portability, OASIS XDI TC)
* Domenico Rotondi (TXT e-solutions SpA)
* Mary Ruddy (Meristic)
* RJ Schlecht (Booz Allen Hamilton)
* Don Thibeau (OIDF, OIX)
* Owen Thomas (Clique Space)
* Paul Trevithick (Azigo)
* Michael Versace
* Colin Wallis (NZ Govt)
* David Wasley (InCommon)
* Peter Watkins (Province of British Columbia)
* Craig Wittenberg (Microsoft)

====To join====
# Add your name above (alphabetic by last name) if you'd like to participate. You can log in with any OpenID to this wiki.
# Join the [http://lists.idcommons.net/lists/info/claims-agent claims-agent list]

=== Current Stewards Council Representative and Alternate ===

The stewards council representative will be selected by the members of the working group.

=== Current Links ===

None at present.

=== Related Groups ===

* OpenID Artifact Binding Working Group
* [http://kantarainitiative.org/confluence/display/ulx/Home Kantara ULX WG] and [http://kantarainitiative.org/confluence/display/wgci Consumer Identity WG]
* [https://mozillalabs.com/blog/2010/03/account-manager/ Mozilla Account Manager]
* [http://code.google.com/p/openinfocard/ OpenInfoCard]
* [http://www.fc2-consortium.org/ FC2]
* [http://wiki.eclipse.org/Cloud_Selector_1.1 Higgins Cloud Selector]
* [http://wiki.eclipse.org/Active_Client_Overview Higgins Active Client]

=== History ===

This is where the group can share about how/why the group was founded and where will be where quarterly reports will be linked to.

Personal Data Ecosystem Charter

2011-01-03T18:07:07Z

DrummondReed: turned Related Group entries into links

=== Name ===

Personal Data Ecosystem Collaborative Consortium

=== Purpose ===

To get this emerging personal data ecosystem to work for all, there are many interests that need to be brought forward, and different interests that need to be balanced. These include individuals, businesses, governments, advocacy groups, standards bodies, developers, personal data store service providers, government regulators, media, and others.

The purpose of The Personal Data Ecosystem Collaborative Consortium (PDECC) is to support all these interests being brought forward and to define the emergent market models, convergence around technical standards for personal data services and the policies that support them.

=== Principles ===

IC Principles:

# '''Self-Organization.''' Enable any working group to self-organize at any time, on any scale, in any form, around any activity consistent with the Purpose and Principles.
# '''Transparency.''' Fully and transparently disclose the Purpose and Principles of each working group, any requirement of participation, and any license or restriction of usage of its work product.
# '''Inclusion.''' Conduct deliberations and make decisions by bodies and methods that reasonably represent all relevant and affected parties.
# '''Empowerment.''' Vest authority, perform functions, and use resources in the smallest or most local part that includes all relevant and affected parties.
# '''Collaboration.''' Resolve conflict without resort to economic, legal, or other duress.
# '''Openness.''' Conduct, publish, and archive communications in a manner that facilitates open and trusted interactions within and across all working groups and the public Internet.
# '''Dogfooding.''' When feasible and appropriate, employ the work product of Identity Commons working groups to facilitate the operation and interaction of Identity Commons itself.

Additional Principles:

=== Practices ===

PDECC fulfills its purpose via:
* Convening multi-stakeholder conversations:
** Via the Podcast
** at industry events
** online in existing fora
*** blogs
*** mailing lists
** online in fora it develops for this purpose

* Providing knowledge resources for companies, users, and policy makers
** Being a public repository of information in the emerging market place to help bring clarity

* Providing cooperation space that brings coherence and common practices in order for the ecosystem to work for everyone.
** Fostring key dialogues around critical issues like market models and legal frameworks.

=== Requirements of Participation and How to Join ===

* General Mailing list.

* The initial mailing list is going to be about standardization and open to those who are actually implementing.

* The mailing blog is re-publishing work from around the web that focuses on this area.

* We are working on a community governance/belonging model.

=== Licenses and/or Restrictions on Usage of Work Product ===

Public output of the community is by default licensed as Creative Commons with Attribution.

=== Current Deliverables and Milestones ===

* Key Conversations around critical issues in the community.
* Podcasts
* Hub of Who's Who and which companies are working on what

=== Current Meeting Schedule ===

* IIW in May

=== Current Membership ===

Individuals who work in Industry
* Kaliya Hamlin
* Iain Henderson
* Mary Hodder
* Phil Windley
* William Heath
* Drummond Reed

Startup Companies
* Mydex

Public Companies
* ?

=== Current Stewards Council Representative and Alternate ===

Kaliya Hamlin
Alternate: Iain Henderson

=== Current Links ===

* [http://www.personaldataecosystem.org Personal Data Ecosystem]
* [http://wiki.idcommons.net/Personal_Data_Ecosystem Wiki Space]

=== Related Groups ===

* [http://kantarainitiative.org/confluence/display/infosharing/Home Volunteered Personal Information at Kantara]
* [http://projectvrm.org Project VRM]
* [http://www.openidentityexchange.org/ OIX (Open Identity Exchange)]
* [http://www.oasis-open.org/committees/xdi/ OASIS XRI Technical Committee]
* [http://www.oasis-open.org/committees/xdi/ OASIS XDI Technical Committee]

=== History ===

User-Centric Health Charter

2009-01-07T19:14:47Z

DrummondReed: /* Related Groups (Suggested) */

=== Name ===

User-Centric Health

=== Purpose ===

This group is designed to develop a set of patterns for enabling user-centric health platforms and applications that enable a person to have control of their health information in a way that promotes an ecosystem including providers, payers, and team.

=== Principles ===

This working group will operate by the Identity Commons principles.

=== Practices ===

This group will use Identity Commons-hosted mailing lists and wiki resources, as well as Google Docs for spreadsheets, presentations, and documents.

This group uses public Identity Commons-hosted mailing list and all its meeting notes will be publically published on posts to that list.

Meeting notes from first meeting 12/18/2008: [http://docs.google.com/Doc?id=dfk7n8fk_88hf8b58g9 12/18 kickoff notes]

=== Requirements of Participation and How to Join ===

There are no requirements for participation. To join the group, edit the wiki and put your name on the list below, and sign up for the mailing list provided
http://lists.idcommons.net/lists/info/usercentrichealth

=== Licenses and/or Restrictions on Usage of Work Product ===

There is no current licenses or restrictions on the work product of this group.

=== Current Deliverables and Milestones ===

Aggregating discussion amongst those thinking about user-centric identity tools and their role in health care systems.

Develop description of a User-Centric Health software scenario to reduce to set of use cases and implementations [http://docs.google.com/Presentation?id=dfk7n8fk_86c339nnc2 Use Case Summary]

Build scenario information matrix for detailing different classes of health information in an individuals ecosystem and what implications are [http://spreadsheets.google.com/ccc?key=ppYIEWbB3w4c4O2JxKK-7YA Example Information Sharing Matrix]

Map out basic components (software, standards, working groups) to include in technology recommendation

Complete economic proposal for [[Health ID Trust]] Slides: [http://docs.google.com/Presentation?id=dfk7n8fk_48c62vd6ft Slides from IIW]

=== Current Meeting Schedule ===

First meeting for the group will be in December 18th at 10:00 A.M. Pacific

Topic: User Centric Health
Date: Thursday, December 18, 2008
Time: 10:00 am, Pacific Standard Time (GMT -08:00, San Francisco)
Meeting Number: 575 130 394
Meeting Password: blueDot1

-------------------------------------------------------
To join the online meeting
-------------------------------------------------------
1. Go to https://polka.webex.com/polka/j.php?ED=115776877&UID=0&PW=7f2f5bd7dd5900141620054d46
2. Enter your name and email address.
3. Enter the meeting password: blueDot1
4. Click "Join Now".

-------------------------------------------------------
To join the teleconference only
-------------------------------------------------------
Provide your phone number when you join the meeting to receive a call back. Or, call the number below and enter the meeting number.
Call-in toll-free number (US/Canada): 866-469-3239
Call-in toll number (US/Canada): 1-650-429-3300
Global call-in numbers: https://polka.webex.com/polka/globalcallin.php?serviceType=MC&ED=115776877&tollFree=1
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

'''AGENDA FOR FIRST MEETING'''

1) Confirm practices and procedures for becoming a group in ID Commons

2) Discuss initial charter definition, use case, projects, and roles (including steward representatives, contributors, observers)

3) Define first use case and outline architecture to test against scenario presented. Am hoping this step can set a goal of working set of user examples to model end-to-end package to describe the opportunities for deployment and other works

4) How to best learn from and work with other User Centric Health groups in the industry like the DataPortability, Liberty Alliance, ANSI and OASIS groups which are also dedicated to this same topic (it may not be called "user centric" in each instance but it is basically the same topic in each instance).

After that, we expect monthly meetings, this will be decided at the first meeting.

=== Current Membership ===

* Mike Kirkwood, Polka
* Paul Trevithick, Parity
* J. Trent Adams, DataPortability Project HCTF
* Joseph Cerro, DataPortability.org Health Care Task Force
* Drummond Reed, Cordance, Parity, OASIS XRI & XDI TCs

Sign up for the mailing list provided by ID Commons
http://lists.idcommons.net/lists/info/usercentrichealth

=== Current Stewards Council Representative and Alternate ===

Stewards Representative - Mike Kirkwood

Alternate Representative - TBD

=== Current Links ===
[[User-Centric Health]]

=== Related Groups (Suggested) ===

[http://openid.net/ Open ID Foundation]

[http://informationcard.net/ Information Card Foundation]

[http://www.projectvrm.org Project VRM]

[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xdi OASIS XDI Technical Committee] and [[XDI Commons Charter|XDI Commons]]

[http://accelerator.editme.com/ Health 2.0 Accelerator]

[http://wiki.dataportability.org/display/dpmain/2008/11/14/Initial+Healthcare+Task+Force+Teleconference Data Portability Healthcare Task Force]

[http://www.astm.org/COMMIT/COMMITTEE/E31.htm ASTM E 31]

[http://www.projectliberty.org/ Liberty Alliance]

[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep OASIS ebXML RR]

=== History ===

Health is a unique use case of the internet identity, it has special because of the privacy and sharing requirements of the data.

Many individuals have a keen interest in how Health plays out using the internet and the web. Mike Kirkwood has been attending the IIW and Data Sharing Summits to get grounded in the identity space. After attending Health 2.0, and becoming part of the Health 2.0 Accelrator, he started this group to merge the concepts of user-centric-identity and Health information.

This group was started to focus on taking the document and data standards of the Health community and packaging them on behalf of a user in their user-centric identity, and create a working stack to share with the community and evolve as group.

User-Centric Health Charter

2008-12-09T20:32:01Z

DrummondReed: /* Related Groups (Suggested) */

=== Name ===

User-Centric Health

=== Purpose ===

This group is designed to develop a set of patterns for enabling user-centric health platforms and applications that enable a person to have control of their health information in a way that promotes an ecosystem including providers, payers, and team.

=== Principles ===

This working group will operate by the Identity Commons principles.

=== Practices ===

This group will use Identity Commons-hosted mailing lists and wiki resources, as well as Google Docs for spreadsheets, presentations, and documents.

This group uses public Identity Commons-hosted mailing list and all its meeting notes will be publically published on posts to that list.

=== Requirements of Participation and How to Join ===

There are no requirements for participation. To join the group, edit the wiki and put your name on the list.

=== Licenses and/or Restrictions on Usage of Work Product ===

There is no current licenses or restrictions on the work product of this group.

=== Current Deliverables and Milestones ===

Aggregating discussion amongst those thinking about user-centric identity tools and their role in health care systems.

Working on the Formation of a economic proposal for a [[Health ID Trust]]
Working on a description of a User-Centric Health software stack
Working on a information matrix for detailing different classes of health information in an individuals ecosystem

=== Current Meeting Schedule ===

First meeting for the group will be in December 18th at 10:00 A.M. Pacific

Topic: User Centric Health
Date: Thursday, December 18, 2008
Time: 10:00 am, Pacific Standard Time (GMT -08:00, San Francisco)
Meeting Number: 575 130 394
Meeting Password: blueDot1

-------------------------------------------------------
To join the online meeting
-------------------------------------------------------
1. Go to https://polka.webex.com/polka/j.php?ED=115776877&UID=0&PW=7f2f5bd7dd5900141620054d46
2. Enter your name and email address.
3. Enter the meeting password: blueDot1
4. Click "Join Now".

-------------------------------------------------------
To join the teleconference only
-------------------------------------------------------
Provide your phone number when you join the meeting to receive a call back. Or, call the number below and enter the meeting number.
Call-in toll-free number (US/Canada): 866-469-3239
Call-in toll number (US/Canada): 1-650-429-3300
Global call-in numbers: https://polka.webex.com/polka/globalcallin.php?serviceType=MC&ED=115776877&tollFree=1
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

'''AGENDA FOR FIRST MEETING'''

1) Confirm practices and procedures for becoming a group in ID Commons

2) Discuss initial charter definition, use case, projects, and roles (including steward representatives, contributors, observers)

3) Define first use case and outline architecture to test against scenario presented. Am hoping this step can set a goal of working set of user examples to model end-to-end package to describe the opportunities for deployment and other works

4) How to best learn from and work with other User Centric Health groups in the industry like the DataPortability, Liberty Alliance, ANSI and OASIS groups which are also dedicated to this same topic (it may not be called "user centric" in each instance but it is basically the same topic in each instance).

After that, we expect monthly meetings, this will be decided at the first meeting.

=== Current Membership ===

* Mike Kirkwood, Polka
* Paul Trevithick, Parity
* J. Trent Adams, DataPortability Project HCTF
* Drummond Reed, Cordance, Parity, OASIS XRI & XDI TCs

Also, sign up for the mailing list provided by ID Commons
http://lists.idcommons.net/lists/info/usercentrichealth

=== Current Stewards Council Representative and Alternate ===

Stewards Representative - Mike Kirkwood

Alternate Representative - TBD

=== Current Links ===
[[User-Centric Health]]

=== Related Groups (Suggested) ===

[http://openid.net/ Open ID Foundation]

[http://informationcard.net/ Information Card Foundation]

[http://www.projectvrm.org Project VRM]

[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xdi OASIS XDI Technical Committee]

[http://accelerator.editme.com/ Health 2.0 Accelerator]

[http://wiki.dataportability.org/display/dpmain/2008/11/14/Initial+Healthcare+Task+Force+Teleconference Data Portability Healthcare Task Force]

[http://www.astm.org/COMMIT/COMMITTEE/E31.htm ASTM E 31]

[http://www.projectliberty.org/ Liberty Alliance]

[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep OASIS ebXML RR]

=== History ===

Health is a unique use case of the internet identity, it has special because of the privacy and sharing requirements of the data.

Many individuals have a keen interest in how Health plays out using the internet and the web. Mike Kirkwood has been attending the IIW and Data Sharing Summits to get grounded in the identity space. After attending Health 2.0, and becoming part of the Health 2.0 Accelrator, he started this group to merge the concepts of user-centric-identity and Health information.

This group was started to focus on taking the document and data standards of the Health community and packaging them on behalf of a user in their user-centric identity, and create a working stack to share with the community and evolve as group.

User-Centric Health Charter

2008-12-09T20:31:24Z

DrummondReed: /* Current Membership */

=== Name ===

User-Centric Health

=== Purpose ===

This group is designed to develop a set of patterns for enabling user-centric health platforms and applications that enable a person to have control of their health information in a way that promotes an ecosystem including providers, payers, and team.

=== Principles ===

This working group will operate by the Identity Commons principles.

=== Practices ===

This group will use Identity Commons-hosted mailing lists and wiki resources, as well as Google Docs for spreadsheets, presentations, and documents.

This group uses public Identity Commons-hosted mailing list and all its meeting notes will be publically published on posts to that list.

=== Requirements of Participation and How to Join ===

There are no requirements for participation. To join the group, edit the wiki and put your name on the list.

=== Licenses and/or Restrictions on Usage of Work Product ===

There is no current licenses or restrictions on the work product of this group.

=== Current Deliverables and Milestones ===

Aggregating discussion amongst those thinking about user-centric identity tools and their role in health care systems.

Working on the Formation of a economic proposal for a [[Health ID Trust]]
Working on a description of a User-Centric Health software stack
Working on a information matrix for detailing different classes of health information in an individuals ecosystem

=== Current Meeting Schedule ===

First meeting for the group will be in December 18th at 10:00 A.M. Pacific

Topic: User Centric Health
Date: Thursday, December 18, 2008
Time: 10:00 am, Pacific Standard Time (GMT -08:00, San Francisco)
Meeting Number: 575 130 394
Meeting Password: blueDot1

-------------------------------------------------------
To join the online meeting
-------------------------------------------------------
1. Go to https://polka.webex.com/polka/j.php?ED=115776877&UID=0&PW=7f2f5bd7dd5900141620054d46
2. Enter your name and email address.
3. Enter the meeting password: blueDot1
4. Click "Join Now".

-------------------------------------------------------
To join the teleconference only
-------------------------------------------------------
Provide your phone number when you join the meeting to receive a call back. Or, call the number below and enter the meeting number.
Call-in toll-free number (US/Canada): 866-469-3239
Call-in toll number (US/Canada): 1-650-429-3300
Global call-in numbers: https://polka.webex.com/polka/globalcallin.php?serviceType=MC&ED=115776877&tollFree=1
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

'''AGENDA FOR FIRST MEETING'''

1) Confirm practices and procedures for becoming a group in ID Commons

2) Discuss initial charter definition, use case, projects, and roles (including steward representatives, contributors, observers)

3) Define first use case and outline architecture to test against scenario presented. Am hoping this step can set a goal of working set of user examples to model end-to-end package to describe the opportunities for deployment and other works

4) How to best learn from and work with other User Centric Health groups in the industry like the DataPortability, Liberty Alliance, ANSI and OASIS groups which are also dedicated to this same topic (it may not be called "user centric" in each instance but it is basically the same topic in each instance).

After that, we expect monthly meetings, this will be decided at the first meeting.

=== Current Membership ===

* Mike Kirkwood, Polka
* Paul Trevithick, Parity
* J. Trent Adams, DataPortability Project HCTF
* Drummond Reed, Cordance, Parity, OASIS XRI & XDI TCs

Also, sign up for the mailing list provided by ID Commons
http://lists.idcommons.net/lists/info/usercentrichealth

=== Current Stewards Council Representative and Alternate ===

Stewards Representative - Mike Kirkwood

Alternate Representative - TBD

=== Current Links ===
[[User-Centric Health]]

=== Related Groups (Suggested) ===

[http://openid.net/ Open ID Foundation]

[http://informationcard.net/ Information Card Foundation]

[http://www.projectvrm.org Project VRM]

[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xdi XDI Oasis TC]

[http://accelerator.editme.com/ Health 2.0 Accelerator]

[http://wiki.dataportability.org/display/dpmain/2008/11/14/Initial+Healthcare+Task+Force+Teleconference Data Portability Healthcare Task Force]

[http://www.astm.org/COMMIT/COMMITTEE/E31.htm ASTM E 31]

[http://www.projectliberty.org/ Liberty Alliance]

[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep OASIS ebXML RR]

=== History ===

Health is a unique use case of the internet identity, it has special because of the privacy and sharing requirements of the data.

Many individuals have a keen interest in how Health plays out using the internet and the web. Mike Kirkwood has been attending the IIW and Data Sharing Summits to get grounded in the identity space. After attending Health 2.0, and becoming part of the Health 2.0 Accelrator, he started this group to merge the concepts of user-centric-identity and Health information.

This group was started to focus on taking the document and data standards of the Health community and packaging them on behalf of a user in their user-centric identity, and create a working stack to share with the community and evolve as group.

2008 Q3 Report XDIorg

2008-11-04T22:57:12Z

DrummondReed:

== Successes ==
* Held several board meetings to discuss how governance of the XDI.org global XRI registries can be further integrated with ICANN, IANA, and other existing Internet infrastructure.
* Discussed the participation of XDI.org in IDTBD if it comes to fruition.

== Breakdowns ==
''None.''

== Requests ==
* XDI.org is interested in further feedback from Identity Commons communities regarding the best means for further integrating XRI global registry governance with other Internet infrastructure.

== Announcements ==
''None at this time.''

2008 Q3 Report XDI Commons

2008-10-16T18:00:48Z

DrummondReed:

=== Successes ===
* The XDI RDF model continues to mature; work on [http://wiki.oasis-open.org/xdi/XdiOneSpecs formal specifications] will begin in Q4.
* The [http://www.eclipse.org/higgins/ Higgins Project] is using XDI for an identity service configuration protocol that will enable identity selectors to be automatically configured for use with OpenID providers and i-card wallet providers.
* Markus Sabadello continues to produce [[http://graceland.parityinc.net/xdi-validator/Other.jsp new XDI utilities] using the [http://wiki.eclipse.org/XDI4j XDI4J] project. His newest is the [http://graceland.parityinc.net/xdi-signer/XDISigner XDI Signer].

=== Breakdowns ===
* The [http://www.equalsdrummond.name/?p=130 breakdown] between the [http://www.oasis-open.org/committees/xri/ OASIS XRI Technical Committee] and the [http://www.w3.org/2001/tag/ W3C TAG (Technical Architecture Group)] in May has led to a long set of discussions between the two groups and appears to be well on the way to a resolution. This is important as the XDI TC has a dependency on the XRI specifications from the XRI TC.

=== Requests ===
* As the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee] commences formal work on the [http://wiki.oasis-open.org/xdi/XdiOneSpecs XDI 1.0 specifications] in the fourth quarter, we invite new members or observers to be directly involved in writing, reviewing, or testing implementations.

=== Announcements ===
* The [http://www.oasis-open.org/committees/xri/ XRI TC], which includes many members of the XDI TC, will be holding a face-to-face meeting on Nov. 13-14 in Mountain View, CA after the [http://iiw.idcommons.net/ Internet Identity Workshop]. Discussion will focus on XRI 3.0 which is central to XDI 1.0. Please contact us if you would like to attend.

XDI Commons Charter

2008-10-03T01:42:33Z

DrummondReed: /* Current Stewards Council Representative and Alternate */

=== Name ===

'''XDI Commons Working Group'''
* Requested Identity Commons mailing list: '''xdi --at-- idcommons.net'''

=== Purpose ===

The purpose of this working group is to advance practical deployment, usage, and best practices for the [http://en.wikipedia.org/wiki/XDI XDI (XRI Data Interchange)] protocol under development by the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee].

=== Principles ===

This working group will function according to the Identity Commons Principles (see [[Purpose And Principles]]).

=== Requirements of Participation and How to Join ===

Membership in this working group is open to any individual or organization interested in the advancement of XDI. To join, just add your name and OpenID-verifiable identifier to the member section below and also join the [http://groups.google.com/group/xdi-commons XDI Commons mailing list at Google Groups].

=== Licenses and/or Restrictions on Usage of Work Product ===

All XDI Commons work products will be open, public, royalty-free with no restrictions on usage. Any open source code developed under the auspices of the working group will also be available under popular open source licenses.

=== Current Deliverables and Milestones ===

* One initial focus will be on development and interoperation testing of implementations of the XDI RDF and XDI ATI models as described on the [http://wiki.oasis-open.org/xdi/ XDI TC wiki].
* Another initial focus will be on how [http://www.oasis-open.org/committees/download.php/25531/xdi-rdf-model-v7.pdf XDI RDF] documents can provide i-tags functionality as described on the [http://www.itags.net/ i-tags wiki]. Note that the XDI Commons charter replaces the former I-Tags working group charter.
* Further deliverables will be scheduled as necessary.

=== Current Meeting Schedule ===

There is not presently a regular meeting schedule. Discussion of XDI implementations, interoperability, best practices, etc. will takes place directly among working group members and on the XDI Commons mailing list as soon as it is available. Telecons or face-to-face meetings will be announced via this list.

=== Current Membership ===

* Mary Hodder (http://xri.net/=mary.hodder)
* Kaliya Hamlin (http://xri.net/=kaliya)
* Drummond Reed (http://xri.net/=drummond.reed)
* Andy Dale (http://xri.net/=andy.dale)
* Daniel Perry (http://xri.net/=dan.perry)
* Bill Barnhill (http://xri.net/=bill.barnhill)
* John Bradley (http://xri.net/=jbradley)
* Victor Grey (http://xri.net/=victor.grey)
* Kermit Snelson (http://xri.net/=kermit)
* Markus Sabadello (http://xri.net/=markus)
* Fen Labalme (http://xri.net/=fen)
* Paul Trevithick (http://xri.net/=paul.trevithick)
* Robert O'Brien (http://xri.net/=robert)

=== Current Stewards Council Representative and Alternate ===

* Representative: Drummond Reed
* Alternate: Andy Dale

=== Current Links ===

* [http://wiki.oasis-open.org/xdi/ OASIS XDI Technical Committee wiki]
** [http://wiki.oasis-open.org/xdi/XdiRdfModel XDI TC wiki page on the XDI RDF Model and X3 Format]
* [http://en.wikipedia.org/wiki/XDI Wikipedia page on XDI]
* [http://groups.google.com/group/xdi-commons XDI Commons mailing list hosted by Google Groups]
* [http://www.itags.net I-Tags wiki] - Note that i-tags functionality has been subsumed by XDI document using the [http://wiki.oasis-open.org/xdi/XdiRdfModel XDI RDF Model].

=== History ===

Approved by the [[Stewards Council]] on February 8, 2008.

* [[2008 Q1 Report XDI Commons]]
* [[2008 Q2 Report XDI Commons]]

Stewards Council Telecon: 2008 September 3

2008-08-30T21:11:52Z

DrummondReed: /* Agenda */

Call in number:
1-605-475-4333 access code: 181783

= Attending =

= Agenda =

'''Review of agenda '''

'''Volunteer to take notes'''

'''Updates on action items from last call'''

# DAN to renew DNS registrations using PayPal.
# MARY to clarify how we update our policy about:
## Spending for non-budget items.
## Only requiring notification of charter changes.
# MARY, DRUMMOND, KALIYA to send email to IDTBD list introducing themselves as official representatives of the Identity Commons Stewards Council.

'''Vote(s) in process.'''
# Dissolving working groups
# Adding the proposed groups (that are ready for the vote.)
# Changing Working Groups to Action Groups.

'''New Items'''
# Report on IDTBD discussions (MARY, KALIYA, DRUMMOND)

Stewards Council Telecons

2008-08-30T21:10:48Z

DrummondReed: fixed errors

All members of the Identity Commons community are welcome and encouraged to participate in [[Stewards Council]] telecons. However, only active Stewards may vote on voting matters. For more on this, see [[Organizational Structure]].

== Schedule ==

Next Stewards Council conference call will be on Wednesday, Sept. 3 at 9am PT / 12pm ET.

The remaining calls in 2008:

* Wednesday, October 1, 2008
* Wednesday, November 5, 2008
* Wednesday, December 3, 2008

== Dial-In Info ==

IdCommons on FreeConference.com:

1-605-475-4333
access code: 181783

=== Back Channel ===

[irc://irc.freenode.net/#idcommons #idcommons at irc.freenode.net]

== Agenda / Minutes ==
* [[Stewards Council Telecon: 2008 September 3]]
* [[Stewards Council Telecon: 2008 August 6]]
* [[Stewards Council Telecon: 2008 July 2]]
* [[Stewards Council Telecon: 2008 June 4]]
* [[Stewards Council Telecon: 2008 May 7]]
* [[Stewards Council Telecon: 2008 April 2]]
* [[Stewards Council Telecon: 2008 March 5]]
* [[Stewards Council Telecon: 2008 February 6]]
* [[Stewards Council Telecon: 2008 January 23]]
* [[Stewards Council Telecon: 2007 November 28]]
* [[Stewards Council Telecon: 2007 October 17]]

Community Dictionary Service

2008-08-13T20:21:29Z

DrummondReed: /* Links to XDI Technical Info */ updated reference and removed old material

This is the home page for the Community Dictionary Service (CDS), a project of the Identity Schemas Working Group.

== Motivations ==

There are two problems in large-scale data sharing that a CDS can solve.

=== Establishing Consensus ===

So far the hardest problem in wide-area data sharing has been reaching consensus about schemas/vocabularies. It has proven impossible, even among the narrower communities that drove X.500 and LDAP directory standards.

Taking an open community dictionary approach solves this problem the same way human language does: it recognizes that the problem is beyond the scope of any single authority or standards body and instead focuses on a mechanism for the community as a whole to harmonize on actual practice. It is the Internet equivalent of "vote with your feet" (we might call it "vote with your feed".) This is precisely the approach Wikipedia has taken and why it has been such a success.

=== Achieving Transport-Protocol Independence ===

There is a second even deeper problem to be solved. In theory, a data sharing language can be be independent of the underlying protocol used to transfer the data (e.g., HTTP, WS-Trust, OpenID Attribute Exchange, etc.) However the deeper you get into the problem, the harder this becomes to achieve.

The reason is that unless the actors at the transport protocol level (digital subjects, RPs, identity agents) can identify and describe themselves and their own actions/authorizations directly in the data sharing language, you end up with an artifical dichotomy between the language used for the control layer (identification, authentication, authorization, access control) and the language used to describe the data. From a human language perspective, this would be the equivalent of people using one language – say Latin – for all their basic grammatical constructs and a different language – say English – for all the nouns and verbs they actually want to talk about. Over time the two languages would be forced together just for efficiency and ease of use.

The same convergence is imminent -- and highly desirable – for the emergence of a large-scale Internet data sharing network. For this reason ''their needs to be a data sharing protocol that speaks the same language as the dictionaries used to define the language.'' This is essentially the equivalent of saying that a dictionary of the English language should be written, described, and communicated by English-speaking people (vs. Yiddish, Russion, Japanese, etc.)

== About XDI ==

XDI (XRI Data Interchange) was developed to solve this problem. It is both a simple RDF-based data description format and an "abstract" data sharing protocol that uses this format. This ability to be self-describing, to interleave control and content, makes it especially appropriate to the CDS. However because XDI is an RDF graph model, the CDS can generate dictionary definitions in other data description formats (e.g., RDF/OWL/HOWL, Schemat, OpenID AX Metadata, etc.)

=== Schemas vs. Dictionaries ===

In standard XML architecture, data is described using a ''schema'' written in a ''schema description language'' such as W3C XML Schema (WSD), RelaxNG (RNG), etc. This schema description language has its own small vocabulary for describing a ''grammar'', i.e., rules for defining relationships between elements and attributes. This grammar vocabulary is typically independent of and not reused in the resulting schemas.

Again, this introduces an artificial separation between "control" vocabulary (grammar) and "content" vocabulary (everything else) that does not exist in human language. While it is true that the fewer terms in a language that a machine needs to understand, the easier it is for developers to implement the language, it does not follow that the machine-understandable terms and human-understandable terms need to be in different languages. As with human languages, the grammar of the language can be encoded in a relatively small number of terms that enable the definition, understanding, and usage of all the other terms in the same language.

This is the approach taken with XDI. Since it combines control and content in one language, its base level of definition is not a schema but a '''dictionary''' where, just like human language, each term in the language is defined using the same language. This does not prevent the definition of higher-level semantic constructs such as schemas, forms, templates, queries, etc., just as those same constructs are supported by human languages. But it establishes a common lower layer of semantic consensus that can now be shared across all these constructs rather than redefined separately for each of them.

=== Links to XDI Technical Info ===

XDI is still a young open standards effort, with no formal specifications published yet. What has been developed by the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee] is a very simple graph model and RDF-based data interchange format. This is written up in the [http://wiki.oasis-open.org/xdi/XdiRdfModel The XDI RDF Model]. The initial CDS implementation is based on this model.

== CDS Use Cases, Feature Requests, and Roadmap ==
* [[CDS Use Cases and Requirements]] is the home page for capturing use cases for the CDS.
* [[CDS Design]] describes the basic design goals and principles.
* [[CDS Feature Requests]] is for tracking requests for new features and enhancements.
* [[CDS Roadmap]] is for painting the big picture of where the CDS is going.

== CDS Code, Documentation, and Operation ==
* An initial alpha implementation of the CDS in Java is operational at http://cds.idschemas.idcommons.net.
* [[CDS Code]] is for documenting code availability.
* [[CDS Documentation]] is the home page for documentation of the CDS.
* [[CDS Operation]] is for documenting operational/logistical information.

== CDS Policies and Governance ==
* [[CDS Policies]] discusses and documents specific technical and operational policies for the CDS.
* [[CDS Governance]] discusses the larger governance questions for a "Wikipedia for machines"

== See Also ==
* [[Identity Schemas]]

Stewards Council Telecon: 2008 August 6

2008-08-06T18:53:18Z

DrummondReed: + Chris's text

Call in number:
1-605-475-4333 access code: 181783

= Attending =
* Bob Blakley
* Mary Ruddy
* Fen LaBalme
* Drummond Reed
* Dean Landsman
* Chris Allen
* Brett McDowell
* Dan Perry
* Dale Olds
* Paul Trevithick
* Chris Reynolds
* Charles Andres

= Agenda =

'''Review of agenda '''

'''Volunteer to take notes'''

'''Updates on action items from last call'''

* Chris R. Budget proposal - update for how things should work with small items
* Eugene - update on working with Dan on getting PayPal set up so we can pay for Electric Embers hosting
* Mary - update on outsource nonprofit service provider options for the organization. Need more clarity on what services should be outsourced to core outsourced services provider [http://wiki.idcommons.net/index.php/Outsourcing]
* Changing charters should be brought up for a vote - are there any in process?
* Patrick Reilly with Kaliya's help - update on collecting IPR best practices from other groups. On hold to focus on fundraising.
* Static Website - Next steps.
** need to figure out how to have a diagram of our community that is understandable and clickable
* Kaliya, Mary and Eugene - update on working on some best practices for mentoring new groups into the community
* Kaliya - Update on collecting Stewards contact information for Media call tree, etc. - on hold pending PayPal

* Eugene is holding three votes
# Dissolving the Standards, Identity Mashups and Collaboration working groups.
# Adding the proposed groups (that are ready for the vote.)
# Changing Working Groups to Action Groups.

* Next round of voting will be for
# Elect new Stewards Chair
# Adding proposed working groups

'''New item(s)'''

* Discussion of proposal to change frequency of quarterly reports to semi-annually.
* DNS updates
** identitycommons.{com,net,org} expire 29 August 2008 - $45 to renew at gandi.net
** idcommons.{com,net,org} expire 24 September 2008 - $45 to renew at gandi.net

'''Services Discussion Topic'''
There has been an ongoing discussions about the desirability for the community to provide more services to action groups. [[Services Brainstorm]]. Last time we started to brainstorm some on this call & talk about highest priorities.

= Meeting Notes =
Drummond volunteered to take notes.

== PayPal and Donate Button ==
Dan gave an update about having a donate budget. Dan was finally able to persuade PayPal to give us a donate button. He has emailed Eugene the code. Dan will take care of renewing our DNS updates via Gandi.com. (That takes care of the DNS agenda item.)

== Outsourced Service Providers ==
Mary reported on outsourcing of accounting services. Currently the most requested core services are IT infrastructure and accounting services. She has investigated a number of options for this.

Dan suggested that the accounting organization might be able to provide a discount for IC-related accounting biz.

== Changing Charters ==
Mary explained that the Stewards Council is currently supposed to approve charter changes just as it approves new charters. Dan explained that this could possibly have the effect of bringing more liability to IC. There was consensus that we didn’t want this.

Drummond suggested that the requirement so that groups are only required to notify the Stewards Council of changes (via an email to the Community list). The Stewards Council would not be required to approve any changes, and would only need to act to disassociate the group. There was consensus that this should be our policy. Mary will pursue how this will be memorialized.

Chris A. also asked about Collaboration closing – one effect is that this means there will not be a Steward from Collaboration.

== Budget for Small Expenses ==
Chris R. said that how we are handling this now is fine. He consulted with some very experienced accounting folks. The two rules are:

# You can’t spend money you don’t have. The rule is that if the non-budgeted expense is less than 15% of the money you have in the bank, it should be okay.
# You don’t have to report the non-budgeted expense immediately, but the faster you report it, the better.

Chris R’s recommendations:
# We establish a budget for the period between every IIW conference (six months).
# We report expenses at least quarterly, which means the each conference the treasurer will report on the last two quarters.
# Each non-budgeted expense that looks like it may recur should be included in the next budget.

''Note: Following is the exact text from Chris' email on this subject:''

''I have connected with colleagues on other boards and committees regarding spending guidelines for ad hoc expenses that are necessary but not yet budgeted. One example of such a purchase was some signage / printing for the last IIW 2008a gathering. It turns out that once we corrected for terminology, there was a clear consensus. Most people were saying nearly the same thing. They key points:''

''(a) The necessity of making unbudgeted purchases arises regularly, especially in volunteer and incipient enterprises. So we are not doing anything wrong in having such expenses pop up.''

''(b) The paramount guidelines are: (1) If the amount to be spent is less than 15% of the funds in the bank, then it is OK to go ahead. This step simply prevents spending money we don’t have. (2) Making an ad hoc expenditure does not relieve the executive making the purchase from the obligation to report and justify the expense to the Stewards (or the budget committee) later, using conventional reports. Rather, it simply allows the expense to be made right away to meet an exigent need and have the budget reporting occur afterwards, but not never. This step is believed to be critical to preventing such purchases from fostering an actual or apparent lack of discipline or looseness with money that would lead to problems with fundraising, proper budgeting for mainstream purchasing, etc.''

== Change in Frequency for Quarterly Reports ==
It has been proposed that the frequency be changed to semi-annually. In discussion it was realized that the real driver for production of reports is the audience of both peers and newbies at IIW.

The consensus of the group was:
# Provide notification a month before IIW to all Stewards of the need to file their semi-annual report.
# Establish a deadline for filing the report two weeks before IIW.
# Have a standard session at IIW for each group to present their report.

== IDTBD ("NewOrg") ==
Brett reported that the discussion about NewOrg that he had brought up several months ago has progressed to the point where there is now a strawman proposal and an open mailing list. It has been given the codename IDTBD (ID To Be Determined – suggested by Bob). The Google Group is located at:

http://groups.google.com/group/idtbd?lnk=srg

Fen, having briefly reviewed the IDTBD home page at Google Groups, asked how it was different from Identity Commons. Bob provided the following pithy summary:

# Less vendor- and enterprise-focused than Liberty Alliance.
# Less resource-constrained that Identity Commons.
# As an umbrella organization, it would enable all partipants in the overall ecosystem to lower their investment in organizational overhead while increasing the trend towards harmonization and interoperability.

Brett is representing the Liberty Alliance in this effort. He explained that while a number of individuals who are also IC Stewards are already engaged individually in the discussion, he suggested that if Identity Commons is interested, it would be good for the Stewards Council to have official representation in the discussion so that Identity Commons has a direct and clear voice.

Drummond agreed that this made sense because it would help distinguish between individual participation and formal Identity Commons participation. Bob further agreed that the latter voice is needed at the table to help speak directly to the Identity Commons purpose and principles and how this has been worked out in its organizational structure.

Paul nominated Mary and Drummond to serve as representative of the Stewards Council in the IDTBD discussion. Drummond and Mary accepted but felt the need for additional representation. Bob nominated Kaliya (providing she is willing) to serve as an additional representative (and also Eugene if he wants to do it).

Brett invited these Stewards Council representatives to send a message to the IDTBD list identifying themselves as speaking for IC.

= Action Items =
# DAN to renew DNS registrations using PayPal.
# MARY to clarify how we update our policy about:
## Spending for non-budget items.
## Only requiring notification of charter changes.
# MARY, DRUMMOND, KALIYA to send email to IDTBD list introducing themselves as official representatives of the Identity Commons Stewards Council.

Stewards Council Telecon: 2008 August 6

2008-08-06T18:40:51Z

DrummondReed:

Call in number:
1-605-475-4333 access code: 181783

= Attending =
* Bob Blakley
* Mary Ruddy
* Fen LaBalme
* Drummond Reed
* Dean Landsman
* Chris Allen
* Brett McDowell
* Dan Perry
* Dale Olds
* Paul Trevithick
* Chris Reynolds
* Charles Andres

= Agenda =

'''Review of agenda '''

'''Volunteer to take notes'''

'''Updates on action items from last call'''

* Chris R. Budget proposal - update for how things should work with small items
* Eugene - update on working with Dan on getting PayPal set up so we can pay for Electric Embers hosting
* Mary - update on outsource nonprofit service provider options for the organization. Need more clarity on what services should be outsourced to core outsourced services provider [http://wiki.idcommons.net/index.php/Outsourcing]
* Changing charters should be brought up for a vote - are there any in process?
* Patrick Reilly with Kaliya's help - update on collecting IPR best practices from other groups. On hold to focus on fundraising.
* Static Website - Next steps.
** need to figure out how to have a diagram of our community that is understandable and clickable
* Kaliya, Mary and Eugene - update on working on some best practices for mentoring new groups into the community
* Kaliya - Update on collecting Stewards contact information for Media call tree, etc. - on hold pending PayPal

* Eugene is holding three votes
# Dissolving the Standards, Identity Mashups and Collaboration working groups.
# Adding the proposed groups (that are ready for the vote.)
# Changing Working Groups to Action Groups.

* Next round of voting will be for
# Elect new Stewards Chair
# Adding proposed working groups

'''New item(s)'''

* Discussion of proposal to change frequency of quarterly reports to semi-annually.
* DNS updates
** identitycommons.{com,net,org} expire 29 August 2008 - $45 to renew at gandi.net
** idcommons.{com,net,org} expire 24 September 2008 - $45 to renew at gandi.net

'''Services Discussion Topic'''
There has been an ongoing discussions about the desirability for the community to provide more services to action groups. [[Services Brainstorm]]. Last time we started to brainstorm some on this call & talk about highest priorities.

= Meeting Notes =
Drummond volunteered to take notes.

== PayPal and Donate Button ==
Dan gave an update about having a donate budget. Dan was finally able to persuade PayPal to give us a donate button. He has emailed Eugene the code. Dan will take care of renewing our DNS updates via Gandi.com. (That takes care of the DNS agenda item.)

== Outsourced Service Providers ==
Mary reported on outsourcing of accounting services. Currently the most requested core services are IT infrastructure and accounting services. She has investigated a number of options for this.

Dan suggested that the accounting organization might be able to provide a discount for IC-related accounting biz.

== Changing Charters ==
Mary explained that the Stewards Council is currently supposed to approve charter changes just as it approves new charters. Dan explained that this could possibly have the effect of bringing more liability to IC. There was consensus that we didn’t want this.

Drummond suggested that the requirement so that groups are only required to notify the Stewards Council of changes (via an email to the Community list). The Stewards Council would not be required to approve any changes, and would only need to act to disassociate the group. There was consensus that this should be our policy. Mary will pursue how this will be memorialized.

Chris A. also asked about Collaboration closing – one effect is that this means there will not be a Steward from Collaboration.

== Budget for Small Expenses ==
Chris R. said that how we are handling this now is fine. He consulted with some very experienced accounting folks. The two rules are:

# You can’t spend money you don’t have. The rule is that if the non-budgeted expense is less than 15% of the money you have in the bank, it should be okay.
# You don’t have to report the non-budgeted expense immediately, but the faster you report it, the better.

Chris R’s recommendations:
# We establish a budget for the period between every IIW conference (six months).
# We report expenses at least quarterly, which means the each conference the treasurer will report on the last two quarters.
# Each non-budgeted expense that looks like it may recur should be included in the next budget.

== Change in Frequency for Quarterly Reports ==
It has been proposed that the frequency be changed to semi-annually. In discussion it was realized that the real driver for production of reports is the audience of both peers and newbies at IIW.

The consensus of the group was:
# Provide notification a month before IIW to all Stewards of the need to file their semi-annual report.
# Establish a deadline for filing the report two weeks before IIW.
# Have a standard session at IIW for each group to present their report.

== IDTBD ("NewOrg") ==
Brett reported that the discussion about NewOrg that he had brought up several months ago has progressed to the point where there is now a strawman proposal and an open mailing list. It has been given the codename IDTBD (ID To Be Determined – suggested by Bob). The Google Group is located at:

http://groups.google.com/group/idtbd?lnk=srg

Fen, having briefly reviewed the IDTBD home page at Google Groups, asked how it was different from Identity Commons. Bob provided the following pithy summary:

# Less vendor- and enterprise-focused than Liberty Alliance.
# Less resource-constrained that Identity Commons.
# As an umbrella organization, it would enable all partipants in the overall ecosystem to lower their investment in organizational overhead while increasing the trend towards harmonization and interoperability.

Brett is representing the Liberty Alliance in this effort. He explained that while a number of individuals who are also IC Stewards are already engaged individually in the discussion, he suggested that if Identity Commons is interested, it would be good for the Stewards Council to have official representation in the discussion so that Identity Commons has a direct and clear voice.

Drummond agreed that this made sense because it would help distinguish between individual participation and formal Identity Commons participation. Bob further agreed that the latter voice is needed at the table to help speak directly to the Identity Commons purpose and principles and how this has been worked out in its organizational structure.

Paul nominated Mary and Drummond to serve as representative of the Stewards Council in the IDTBD discussion. Drummond and Mary accepted but felt the need for additional representation. Bob nominated Kaliya (providing she is willing) to serve as an additional representative (and also Eugene if he wants to do it).

Brett invited these Stewards Council representatives to send a message to the IDTBD list identifying themselves as speaking for IC.

= Action Items =
# DAN to renew DNS registrations using PayPal.
# MARY to clarify how we update our policy about:
## Spending for non-budget items.
## Only requiring notification of charter changes.
# MARY, DRUMMOND, KALIYA to send email to IDTBD list introducing themselves as official representatives of the Identity Commons Stewards Council.

Stewards Council Telecon: 2008 August 6

2008-08-06T18:40:21Z

DrummondReed: + notes from the meeting

Call in number:
1-605-475-4333 access code: 181783

= Attending =
* Bob Blakley
* Mary Ruddy
* Fen LaBalme
* Drummond Reed
* Dean Landsman
* Chris Allen
* Brett McDowell
* Dan Perry
* Dale Olds
* Paul Trevithick
* Chris Reynolds
* Charles Andres

= Agenda =

'''Review of agenda '''

'''Volunteer to take notes'''

'''Updates on action items from last call'''

* Chris R. Budget proposal - update for how things should work with small items
* Eugene - update on working with Dan on getting PayPal set up so we can pay for Electric Embers hosting
* Mary - update on outsource nonprofit service provider options for the organization. Need more clarity on what services should be outsourced to core outsourced services provider [http://wiki.idcommons.net/index.php/Outsourcing]
* Changing charters should be brought up for a vote - are there any in process?
* Patrick Reilly with Kaliya's help - update on collecting IPR best practices from other groups. On hold to focus on fundraising.
* Static Website - Next steps.
** need to figure out how to have a diagram of our community that is understandable and clickable
* Kaliya, Mary and Eugene - update on working on some best practices for mentoring new groups into the community
* Kaliya - Update on collecting Stewards contact information for Media call tree, etc. - on hold pending PayPal

* Eugene is holding three votes
# Dissolving the Standards, Identity Mashups and Collaboration working groups.
# Adding the proposed groups (that are ready for the vote.)
# Changing Working Groups to Action Groups.

* Next round of voting will be for
# Elect new Stewards Chair
# Adding proposed working groups

'''New item(s)'''

* Discussion of proposal to change frequency of quarterly reports to semi-annually.
* DNS updates
** identitycommons.{com,net,org} expire 29 August 2008 - $45 to renew at gandi.net
** idcommons.{com,net,org} expire 24 September 2008 - $45 to renew at gandi.net

'''Services Discussion Topic'''
There has been an ongoing discussions about the desirability for the community to provide more services to action groups. [[Services Brainstorm]]. Last time we started to brainstorm some on this call & talk about highest priorities.

= Meeting Notes =
Drummond volunteered to take notes.

== PayPal and Donate Button ==
Dan gave an update about having a donate budget. Dan was finally able to persuade PayPal to give us a donate button. He has emailed Eugene the code. Dan will take care of renewing our DNS updates via Gandi.com. (That takes care of the DNS agenda item.)

== Outsourced Service Providers ==
Mary reported on outsourcing of accounting services. Currently the most requested core services are IT infrastructure and accounting services. She has investigated a number of options for this.

Dan suggested that the accounting organization might be able to provide a discount for IC-related accounting biz.

== Changing Charters ==
Mary explained that the Stewards Council is currently supposed to approve charter changes just as it approves new charters. Dan explained that this could possibly have the effect of bringing more liability to IC. There was consensus that we didn’t want this.

Drummond suggested that the requirement so that groups are only required to notify the Stewards Council of changes (via an email to the Community list). The Stewards Council would not be required to approve any changes, and would only need to act to disassociate the group. There was consensus that this should be our policy. Mary will pursue how this will be memorialized.

Chris A. also asked about Collaboration closing – one effect is that this means there will not be a Steward from Collaboration.

== Budget for Small Expenses ==
Chris R. said that how we are handling this now is fine. He consulted with some very experienced accounting folks. The two rules are:

# You can’t spend money you don’t have. The rule is that if the non-budgeted expense is less than 15% of the money you have in the bank, it should be okay.
# You don’t have to report the non-budgeted expense immediately, but the faster you report it, the better.

Chris R’s recommendations:
# We establish a budget for the period between every IIW conference (six months).
# We report expenses at least quarterly, which means the each conference the treasurer will report on the last two quarters.
# Each non-budgeted expense that looks like it may recur should be included in the next budget.

== Change in Frequency for Quarterly Reports ==
It has been proposed that the frequency be changed to semi-annually. In discussion it was realized that the real driver for production of reports is the audience of both peers and newbies at IIW.

The consensus of the group was:
# Provide notification a month before IIW to all Stewards of the need to file their semi-annual report.
# Establish a deadline for filing the report two weeks before IIW.
# Have a standard session at IIW for each group to present their report.

== IDTBD ("NewOrg") ==
Brett reported that the discussion about NewOrg that he had brought up several months ago has progressed to the point where there is now a strawman proposal and an open mailing list. It has been given the codename IDTBD (ID To Be Determined – suggested by Bob). The Google Group is located at:

http://groups.google.com/group/idtbd?lnk=srg

Fen, having briefly reviewed the IDTBD home page at Google Groups, asked how it was different from Identity Commons. Bob provided the following pithy summary:

# Less vendor- and enterprise-focused than Liberty Alliance.
# Less resource-constrained that Identity Commons.
# As an umbrella organization, it would enable all partipants in the overall ecosystem to lower their investment in organizational overhead while increasing the trend towards harmonization and interoperability.

Brett is representing the Liberty Alliance in this effort. He explained that while a number of individuals who are also IC Stewards are already engaged individually in the discussion, he suggested that if Identity Commons is interested, it would be good for the Stewards Council to have official representation in the discussion so that Identity Commons has a direct and clear voice.

Drummond agreed that this made sense because it would help distinguish between individual participation and formal Identity Commons participation. Bob further agreed that the latter voice is needed at the table to help speak directly to the Identity Commons purpose and principles and how this has been worked out in its organizational structure.

Paul nominated Mary and Drummond to serve as representative of the Stewards Council in the IDTBD discussion. Drummond and Mary accepted but felt the need for additional representation. Bob nominated Kaliya (providing she is willing) to serve as an additional representative (and also Eugene if he wants to do it).

Brett invited these Stewards Council representatives to send a message to the IDTBD list identifying themselves as speaking for IC.

= Action Items =
# DAN to renew DNS registrations using PayPal.
# MARY to clarify how we update our policy about:
## Spending for non-budget items.
## Only requiring notification of charter changes.
# MARY, DRUMMOND, KALIYA to send email to IDTBD list introducing themselves as official representatives of the Identity Commons Stewards Council.

2008 Q2 Report XDI Commons

2008-07-11T17:10:36Z

DrummondReed:

=== Successes ===
* The [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee]:
** Elected a new co-chair (Bill Barnhill of Booz Allen Hamilton).
** Published [http://wiki.oasis-open.org/xdi/XdiOneSpecs a list of the proposed XDI 1.0 specifications].
* The [http://wiki.eclipse.org/XDI4j XDI4J (XDI For Java)] Project] published several [http://graceland.parityinc.net/xdi-validator/Other.jsp new utilities], including:
** [http://graceland.parityinc.net/xdi-localmessenger/XDILocalMessenger XDI Local Messenger]
** [http://graceland.parityinc.net/xdi-setter/XDISetter XDI Setter]
** [http://graceland.parityinc.net/xdi-signer/XDISigner XDI Signer]

=== Breakdowns ===
* In May, the OASIS Standard vote on XRI 2.0 (on which XDI depends) [http://www.equalsdrummond.name/?p=130 narrowly missed passage] due to opposition from the W3C Technical Architecture Group. The OASIS XRI TC is now in [http://wiki.oasis-open.org/xri/XriTcW3cTag active discussions with the W3C TAG] to address this breakdown.

=== Requests ===
* IC members interested in the implementation of XDI within the [http://www.eclipse.org/higgins/ Higgins Project] should join the Higgins mailing list.

=== Announcements ===
* None

07-16-08 F2F Meeting

2008-07-09T05:18:40Z

DrummondReed:

This is a proposed informal meeting following the VRM Workshop in Boston Morning of July 16th.

Able to ATTEND
* Kaliya Hamlin
* Mary Ruddy
* Chris Reynolds
* Drummond Reed
* Paul Trevithick

''Please add your name here.''

Stewards Council Telecon: 2008 June 4

2008-06-03T16:15:21Z

DrummondReed: reformatting

Call in number:
1-605-475-4333 access code: 181783

= Attending =

= Agenda =

== Community and Action Groups ==
# Process for sunsetting groups. We have two inactive groups (Standards Gang and Identity Mashups).
# Process for moving forward with formally adding new groups.
## Have vote for real on the ones in the cue via e-mail and if needed phone follow up by Kaliya and Mary.
## What is the process how do we actually do this successfully? Do we need a new tool? Kaliya has proposed one - can some people investigate it and other options? Let's discuss it and by next month have something in place.
## Drummond posted a new proposal for streamlining the Action Group approval process.
# Marty Schleiff has raised a question with regard to the proposed Enterprise Architects AG: can membership in working groups be just by individual name and not require corporate affiliation?

== Static Website Makeover Team - 3 Week Effort ==
Over the summer there may be some events where the IC website will be getting attention (there are some announcements that will include references to it). So we want it to look good. Kaliya will be leading a Static Website improvement team for 3 week ACTION effort. Those who are interested in participating will stay on after the Wed call for 30min to divide the content collection effort up, articulate contractor leads and have and set a meeting on Friday and the following Monday morning.
# Week 1 - gather content and solidify site layout (scout contractors)
# Week 2 (starting Wednesday) - they do magic
# Week 3 - put it up - review fix errors.

== IT Infrastructure ==
# Held Infrastructure meeting at IIW. [http://iiw.idcommons.net/index.php/Intrastructure-May-14-2008-notes Meeting notes]
# Move Identity Gang mailing list over to open list with IC mail address.
# Electronic Embers hosting status update (in time for use by new groups and email forwarding cutover).

== Other Community Processes (from informal Stewards meeting at IIW) ==
# Chris's action item on fundraising give/ask wiki page
# Investigation of director's insurance
# Chris's action item on proposed budget committee to approve spending.
# Status of hiring outsourced non-profit services provider.
# Best practices for IPR – this is an opportunity to put forward an option for best practices

= Summary =

Stewards Council Telecon: 2008 June 4

2008-06-03T16:14:49Z

DrummondReed: /* Attending */

Call in number:
1-605-475-4333 access code: 181783

= Attending =

== Community and Action Groups ==
# Process for sunsetting groups. We have two inactive groups (Standards Gang and Identity Mashups).
# Process for moving forward with formally adding new groups.
## Have vote for real on the ones in the cue via e-mail and if needed phone follow up by Kaliya and Mary.
## What is the process how do we actually do this successfully? Do we need a new tool? Kaliya has proposed one - can some people investigate it and other options? Let's discuss it and by next month have something in place.
## Drummond posted a new proposal for streamlining the Action Group approval process.
# Marty Schleiff has raised a question with regard to the proposed Enterprise Architects AG: can membership in working groups be just by individual name and not require corporate affiliation?

== Static Website Makeover Team - 3 Week Effort ==
Over the summer there may be some events where the IC website will be getting attention (there are some announcements that will include references to it). So we want it to look good. Kaliya will be leading a Static Website improvement team for 3 week ACTION effort. Those who are interested in participating will stay on after the Wed call for 30min to divide the content collection effort up, articulate contractor leads and have and set a meeting on Friday and the following Monday morning.
# Week 1 - gather content and solidify site layout (scout contractors)
# Week 2 (starting Wednesday) - they do magic
# Week 3 - put it up - review fix errors.

== IT Infrastructure ==
# Held Infrastructure meeting at IIW. [http://iiw.idcommons.net/index.php/Intrastructure-May-14-2008-notes Meeting notes]
# Move Identity Gang mailing list over to open list with IC mail address.
# Electronic Embers hosting status update (in time for use by new groups and email forwarding cutover).

== Other Community Processes (from informal Stewards meeting at IIW) ==
# Chris's action item on fundraising give/ask wiki page
# Investigation of director's insurance
# Chris's action item on proposed budget committee to approve spending.
# Status of hiring outsourced non-profit services provider.
# Best practices for IPR – this is an opportunity to put forward an option for best practices

= Summary =

Stewards Council Telecon: 2008 June 4

2008-06-03T16:14:11Z

DrummondReed: /* Agenda */ reformatted

Call in number:
1-605-475-4333 access code: 181783

= Attending =

'''Agenda'''

== Community and Action Groups ==
# Process for sunsetting groups. We have two inactive groups (Standards Gang and Identity Mashups).
# Process for moving forward with formally adding new groups.
## Have vote for real on the ones in the cue via e-mail and if needed phone follow up by Kaliya and Mary.
## What is the process how do we actually do this successfully? Do we need a new tool? Kaliya has proposed one - can some people investigate it and other options? Let's discuss it and by next month have something in place.
## Drummond posted a new proposal for streamlining the Action Group approval process.
# Marty Schleiff has raised a question with regard to the proposed Enterprise Architects AG: can membership in working groups be just by individual name and not require corporate affiliation?

== Static Website Makeover Team - 3 Week Effort ==
Over the summer there may be some events where the IC website will be getting attention (there are some announcements that will include references to it). So we want it to look good. Kaliya will be leading a Static Website improvement team for 3 week ACTION effort. Those who are interested in participating will stay on after the Wed call for 30min to divide the content collection effort up, articulate contractor leads and have and set a meeting on Friday and the following Monday morning.
# Week 1 - gather content and solidify site layout (scout contractors)
# Week 2 (starting Wednesday) - they do magic
# Week 3 - put it up - review fix errors.

== IT Infrastructure ==
# Held Infrastructure meeting at IIW. [http://iiw.idcommons.net/index.php/Intrastructure-May-14-2008-notes Meeting notes]
# Move Identity Gang mailing list over to open list with IC mail address.
# Electronic Embers hosting status update (in time for use by new groups and email forwarding cutover).

== Other Community Processes (from informal Stewards meeting at IIW) ==
# Chris's action item on fundraising give/ask wiki page
# Investigation of director's insurance
# Chris's action item on proposed budget committee to approve spending.
# Status of hiring outsourced non-profit services provider.
# Best practices for IPR – this is an opportunity to put forward an option for best practices

= Summary =

Identity Schemas

2008-04-21T18:25:13Z

DrummondReed: /* References */ updated link

=== About ===
This is the home of the Identity Schemas project. It has been chartered as a Working Group under [http://idcommons.net Identity Commons].

NOTE: Paul (others?) is/are in the process of moving content in here from http://idschemas.idcommons.net/ (old MoinMoin wiki)...Work in progress. (all red links below still need to be copied/transcoded) -Paul

=== Process ===
* [[Identity Schemas Charter]]
* [[Guiding Principles]]
* [[Problem Space]]
* IP Policy: (see [[Identity Schemas Charter]])
* Planned [[Deliverables]]

=== Work in Process ===
* [[Community Dictionary Service]] - an open community-maintained dictionary service of attribute definitions and synonyms modeled after [http://www.wikipedia.org/ Wikipedia].
* [[MetaData]] (http://idschemas.idcommons.net/moin.cgi/MetaData ) --draft set of metadata types
* [[List Of Schemas]] (http://idschemas.idcommons.net/moin.cgi/List_Of_Schemas )
* [[Related Work]] (http://idschemas.idcommons.net/moin.cgi/Related_Work )
* http://krl.a.wiki-site.com/index.php/Main_Page - comparison of KR languages suitable for our purposes

=== Mailing Lists ===
* [http://mail.idcommons.net/cgi-bin/mailman/listinfo/idschemas IdSchemas list] --this is the main list (very low volume)
* [http://idcommons.net/cgi-bin/mailman/listinfo/person-ontology person-ontology list] --new list for folks interested in collaborating on a "person/identity" upper ontology

=== References ===
* [http://wiki.oasis-open.org/xdi/XdiRdfModel OASIS XDI Technical Committee overview of the XDI RDF model] including some simple dictionary examples.

=== Reports to Identity Commons ===
* [[2007 Q4 Report Identity Schemas]]

=== Old Notes ===
* [[2006 Oct 6 Call Notes]] (http://idschemas.idcommons.net/moin.cgi/2006-_Oct-6-_Call_Notes)
* [[Early Design/Requirements Discussion]] (http://idschemas.idcommons.net/moin.cgi/Early_Design/Requirements_Discussion) <-- just a bunch of (old and rough) notes slammed in here
* [[Open Issues]] <-- another bunch of rough/old notes

IC Evangelism & Marketing Charter

2008-04-15T16:18:04Z

DrummondReed: /* Licenses and/or Restrictions on Usage of Work Product */

=== Name ===

Identity Commons Evangelism & Marketing

=== Purpose ===

Provide content that will help Identity Commons, its member groups, and individuals more effectively communicate the goals, principles, and messages of Identity Commons. Assist in any evangelism efforts to bring appropriate working groups and individuals to become Identity Commons members.

=== Principles ===

* Communication in Plain English
* Focus on accessible communication and continuous improvement in this area. Being rigorous about the question: Are we making sense to regular people.

=== Practices ===

We plan primarily develop prototype content on the wiki, and host discussions on this topic at the community@idcommons.net list. If the discussions become too noisy for the general list, a new list will be created. Anyone may be contribute to this working group, but you must be signed up below as a working group member to vote. Before any content can be declared official (i.e. moved off of workgroup pages on this wiki onto pages like the Identity Commons home page), it requires rough consensus of working group members to agree to the content. The Working Group Steward must declare if rough consensus has been met. If there are disagreements among the working group members, or if there is a disagreement that rough consensus has been met, the disagreement can be brought by any member to the Stewards Council for their resolution.

=== Requirements of Participation and How to Join ===

To join, add yourself to the list of participants below and subscribe to the community@idcommons.net list. (Since our work is closely intertwined with communicating the wholistic IC message, we will try to avoid setting up a separate mailing list just for this working group.)

=== Licenses and/or Restrictions on Usage of Work Product ===

Any work produced by this group for usage by Identity Commons is copyright and trademark of Identity Commons. It will be licensed under the appropriate [http://creativecommons.org Creative Commons] license for free and open usage.

=== Current Deliverables and Milestones ===

* Complete Charter (in particular, Purpose, Principles & Practices statements)

* Problem Statement -- How is Identity Commons currently perceived vs. how it wants to be perceived? What obstacles or difficulties in explaining Identity Commons to non-members are

* Refined Messages -- Based on the problem statement, how can we refine our messages to more effectively communicate?

* Update to Home Page -- Based on the refined messages, do an update to the home page and other appropriate top-level pages.

=== Current Meeting Schedule ===

No regular meetings are planned at this time -- work will proceed via the current wiki and email discussion list. Teleconference calls are discouraged, but can be scheduled as needed.

=== Current Membership ===

* Christopher Allen
* Kaliya Hamlin
* Drummond Reed

=== Current Stewards Council Representative and Alternate ===

* Christopher Allen (Primary)
* (No alternate yet)

=== Current Links ===

None

=== History ===

[[2008 Q1 Report Evangelism]]

IC Evangelism & Marketing Charter

2008-04-15T16:15:56Z

DrummondReed: /* Current Stewards Council Representative and Alternate */

=== Name ===

Identity Commons Evangelism & Marketing

=== Purpose ===

Provide content that will help Identity Commons, its member groups, and individuals more effectively communicate the goals, principles, and messages of Identity Commons. Assist in any evangelism efforts to bring appropriate working groups and individuals to become Identity Commons members.

=== Principles ===

* Communication in Plain English
* Focus on accessible communication and continuous improvement in this area. Being rigorous about the question: Are we making sense to regular people.

=== Practices ===

We plan primarily develop prototype content on the wiki, and host discussions on this topic at the community@idcommons.net list. If the discussions become too noisy for the general list, a new list will be created. Anyone may be contribute to this working group, but you must be signed up below as a working group member to vote. Before any content can be declared official (i.e. moved off of workgroup pages on this wiki onto pages like the Identity Commons home page), it requires rough consensus of working group members to agree to the content. The Working Group Steward must declare if rough consensus has been met. If there are disagreements among the working group members, or if there is a disagreement that rough consensus has been met, the disagreement can be brought by any member to the Stewards Council for their resolution.

=== Requirements of Participation and How to Join ===

To join, add yourself to the list of participants below and subscribe to the community@idcommons.net list. (Since our work is closely intertwined with communicating the wholistic IC message, we will try to avoid setting up a separate mailing list just for this working group.)

=== Licenses and/or Restrictions on Usage of Work Product ===

Any work produced by this group for usage by Identity Commons is copyright and trademark of Identity Commons,

and thus must follow any IP guidelines established for IP of Identity Commons.

''There are no IP guidelines for IC - each group must have its own. If our primary task is to develop language for general IC material - web and print then we should consider what the license should be for that.''

=== Current Deliverables and Milestones ===

* Complete Charter (in particular, Purpose, Principles & Practices statements)

* Problem Statement -- How is Identity Commons currently perceived vs. how it wants to be perceived? What obstacles or difficulties in explaining Identity Commons to non-members are

* Refined Messages -- Based on the problem statement, how can we refine our messages to more effectively communicate?

* Update to Home Page -- Based on the refined messages, do an update to the home page and other appropriate top-level pages.

=== Current Meeting Schedule ===

No regular meetings are planned at this time -- work will proceed via the current wiki and email discussion list. Teleconference calls are discouraged, but can be scheduled as needed.

=== Current Membership ===

* Christopher Allen
* Kaliya Hamlin
* Drummond Reed

=== Current Stewards Council Representative and Alternate ===

* Christopher Allen (Primary)
* (No alternate yet)

=== Current Links ===

None

=== History ===

[[2008 Q1 Report Evangelism]]

IC Evangelism & Marketing Charter

2008-04-15T16:15:18Z

DrummondReed: /* Current Membership */

=== Name ===

Identity Commons Evangelism & Marketing

=== Purpose ===

Provide content that will help Identity Commons, its member groups, and individuals more effectively communicate the goals, principles, and messages of Identity Commons. Assist in any evangelism efforts to bring appropriate working groups and individuals to become Identity Commons members.

=== Principles ===

* Communication in Plain English
* Focus on accessible communication and continuous improvement in this area. Being rigorous about the question: Are we making sense to regular people.

=== Practices ===

We plan primarily develop prototype content on the wiki, and host discussions on this topic at the community@idcommons.net list. If the discussions become too noisy for the general list, a new list will be created. Anyone may be contribute to this working group, but you must be signed up below as a working group member to vote. Before any content can be declared official (i.e. moved off of workgroup pages on this wiki onto pages like the Identity Commons home page), it requires rough consensus of working group members to agree to the content. The Working Group Steward must declare if rough consensus has been met. If there are disagreements among the working group members, or if there is a disagreement that rough consensus has been met, the disagreement can be brought by any member to the Stewards Council for their resolution.

=== Requirements of Participation and How to Join ===

To join, add yourself to the list of participants below and subscribe to the community@idcommons.net list. (Since our work is closely intertwined with communicating the wholistic IC message, we will try to avoid setting up a separate mailing list just for this working group.)

=== Licenses and/or Restrictions on Usage of Work Product ===

Any work produced by this group for usage by Identity Commons is copyright and trademark of Identity Commons,

and thus must follow any IP guidelines established for IP of Identity Commons.

''There are no IP guidelines for IC - each group must have its own. If our primary task is to develop language for general IC material - web and print then we should consider what the license should be for that.''

=== Current Deliverables and Milestones ===

* Complete Charter (in particular, Purpose, Principles & Practices statements)

* Problem Statement -- How is Identity Commons currently perceived vs. how it wants to be perceived? What obstacles or difficulties in explaining Identity Commons to non-members are

* Refined Messages -- Based on the problem statement, how can we refine our messages to more effectively communicate?

* Update to Home Page -- Based on the refined messages, do an update to the home page and other appropriate top-level pages.

=== Current Meeting Schedule ===

No regular meetings are planned at this time -- work will proceed via the current wiki and email discussion list. Teleconference calls are discouraged, but can be scheduled as needed.

=== Current Membership ===

* Christopher Allen
* Kaliya Hamlin
* Drummond Reed

=== Current Stewards Council Representative and Alternate ===

I would proposed that Christopher Allen be the representative.

=== Current Links ===

None

=== History ===

[[2008 Q1 Report Evangelism]]

2008 Q1 Report XDI Commons

2008-04-04T03:42:44Z

DrummondReed:

=== Successes ===
# the OASIS XDI Technical Committee, which defines the open standards for XDI, completed an [http://wiki.oasis-open.org/xdi/XdiCharter update of its charter and deliverables].
# Markus Sabadello released the first version of [http://wiki.eclipse.org/XDI4j_Solution XDI4J] (XDI for Java).
# The OASIS XRI Technical Committee (XDI is based on XRI) complete the final review of [http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.html XRI Resolution 2.0 Committee Draft 03] so that it can be submitted for an OASIS Standard vote in May.

=== Breakdowns ===
None this quarter.

=== Requests ===
* The XDI TC invites Identity Commons community members who are interested in an open data portability format that supports user-centric control of data sharing (via XDI link contracts) to join the [http://wiki.idcommons.net/index.php/XDI_Commons_Charter XDI Commons working group] or the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee] or both.

=== Announcements ===
* The first release of [http://wiki.eclipse.org/XDI4j_Solution XDI4J] (XDI for Java) was made by Markus Sabadello via the Higgins Project at Eclipse.
* As a key step forward in XRI and XDI infrastructure, the [http://www.xdi.org XDI.org] [http://gss.xdi.org Global Registry Services (GRS)] will be being upgraded to support XRI Resolution 2.0. It will support all key new XRI Resolution 2.0 features including automatic CanonicalID verification and XRDS extension elements by the end of Q2. The XDI.org public XRI proxy resolver at xri.net will also be upgraded to support these features.

XDI Commons Charter

2008-03-17T20:00:47Z

DrummondReed: /* Current Links */

=== Name ===

'''XDI Commons Working Group'''
* Requested Identity Commons mailing list: '''xdi --at-- idcommons.net'''

=== Purpose ===

The purpose of this working group is to advance practical deployment, usage, and best practices for the [http://en.wikipedia.org/wiki/XDI XDI (XRI Data Interchange)] protocol under development by the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee].

=== Principles ===

This working group will function according to the Identity Commons Principles (see [[Purpose And Principles]]).

=== Requirements of Participation and How to Join ===

Membership in this working group is open to any individual or organization interested in the advancement of XDI. To join, just add your name and OpenID-verifiable identifier to the member section below and also join the [http://groups.google.com/group/xdi-commons XDI Commons mailing list at Google Groups].

=== Licenses and/or Restrictions on Usage of Work Product ===

All XDI Commons work products will be open, public, royalty-free with no restrictions on usage. Any open source code developed under the auspices of the working group will also be available under popular open source licenses.

=== Current Deliverables and Milestones ===

* One initial focus will be on development and interoperation testing of implementations of the XDI RDF and XDI ATI models as described on the [http://wiki.oasis-open.org/xdi/ XDI TC wiki].
* Another initial focus will be on how [http://www.oasis-open.org/committees/download.php/25531/xdi-rdf-model-v7.pdf XDI RDF] documents can provide i-tags functionality as described on the [http://www.itags.net/ i-tags wiki]. Note that the XDI Commons charter replaces the former I-Tags working group charter.
* Further deliverables will be scheduled as necessary.

=== Current Meeting Schedule ===

There is not presently a regular meeting schedule. Discussion of XDI implementations, interoperability, best practices, etc. will takes place directly among working group members and on the XDI Commons mailing list as soon as it is available. Telecons or face-to-face meetings will be announced via this list.

=== Current Membership ===

* Mary Hodder (http://xri.net/=mary.hodder)
* Kaliya Hamlin (http://xri.net/=kaliya)
* Drummond Reed (http://xri.net/=drummond.reed)
* Andy Dale (http://xri.net/=andy.dale)
* Daniel Perry (http://xri.net/=dan.perry)
* Bill Barnhill (http://xri.net/=bill.barnhill)
* John Bradley (http://xri.net/=jbradley)
* Victor Grey (http://xri.net/=victor.grey)
* Kermit Snelson (http://xri.net/=kermit)
* Markus Sabadello (http://xri.net/=markus)
* Fen Labalme (http://xri.net/=fen)
* Paul Trevithick (http://xri.net/=paul.trevithick)

=== Current Stewards Council Representative and Alternate ===

* Representative: Andy Dale
* Alternate: Drummond Reed

=== Current Links ===

* [http://wiki.oasis-open.org/xdi/ OASIS XDI Technical Committee wiki]
** [http://wiki.oasis-open.org/xdi/XdiRdfModel XDI TC wiki page on the XDI RDF Model and X3 Format]
* [http://en.wikipedia.org/wiki/XDI Wikipedia page on XDI]
* [http://groups.google.com/group/xdi-commons XDI Commons mailing list hosted by Google Groups]
* [http://www.itags.net I-Tags wiki] - Note that i-tags functionality has been subsumed by XDI document using the [http://wiki.oasis-open.org/xdi/XdiRdfModel XDI RDF Model].

=== History ===

Approved by the [[Stewards Council]] on February 8, 2008.

XDI Commons Charter

2008-03-17T19:56:54Z

DrummondReed: /* Current Deliverables and Milestones */

=== Name ===

'''XDI Commons Working Group'''
* Requested Identity Commons mailing list: '''xdi --at-- idcommons.net'''

=== Purpose ===

The purpose of this working group is to advance practical deployment, usage, and best practices for the [http://en.wikipedia.org/wiki/XDI XDI (XRI Data Interchange)] protocol under development by the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee].

=== Principles ===

This working group will function according to the Identity Commons Principles (see [[Purpose And Principles]]).

=== Requirements of Participation and How to Join ===

Membership in this working group is open to any individual or organization interested in the advancement of XDI. To join, just add your name and OpenID-verifiable identifier to the member section below and also join the [http://groups.google.com/group/xdi-commons XDI Commons mailing list at Google Groups].

=== Licenses and/or Restrictions on Usage of Work Product ===

All XDI Commons work products will be open, public, royalty-free with no restrictions on usage. Any open source code developed under the auspices of the working group will also be available under popular open source licenses.

=== Current Deliverables and Milestones ===

* One initial focus will be on development and interoperation testing of implementations of the XDI RDF and XDI ATI models as described on the [http://wiki.oasis-open.org/xdi/ XDI TC wiki].
* Another initial focus will be on how [http://www.oasis-open.org/committees/download.php/25531/xdi-rdf-model-v7.pdf XDI RDF] documents can provide i-tags functionality as described on the [http://www.itags.net/ i-tags wiki]. Note that the XDI Commons charter replaces the former I-Tags working group charter.
* Further deliverables will be scheduled as necessary.

=== Current Meeting Schedule ===

There is not presently a regular meeting schedule. Discussion of XDI implementations, interoperability, best practices, etc. will takes place directly among working group members and on the XDI Commons mailing list as soon as it is available. Telecons or face-to-face meetings will be announced via this list.

=== Current Membership ===

* Mary Hodder (http://xri.net/=mary.hodder)
* Kaliya Hamlin (http://xri.net/=kaliya)
* Drummond Reed (http://xri.net/=drummond.reed)
* Andy Dale (http://xri.net/=andy.dale)
* Daniel Perry (http://xri.net/=dan.perry)
* Bill Barnhill (http://xri.net/=bill.barnhill)
* John Bradley (http://xri.net/=jbradley)
* Victor Grey (http://xri.net/=victor.grey)
* Kermit Snelson (http://xri.net/=kermit)
* Markus Sabadello (http://xri.net/=markus)
* Fen Labalme (http://xri.net/=fen)
* Paul Trevithick (http://xri.net/=paul.trevithick)

=== Current Stewards Council Representative and Alternate ===

* Representative: Andy Dale
* Alternate: Drummond Reed

=== Current Links ===

* [http://wiki.oasis-open.org/xdi/ OASIS XDI Technical Committee wiki]
* [http://en.wikipedia.org/wiki/XDI Wikipedia page on XDI]
* [http://www.itags.net I-Tags wiki]

=== History ===

Approved by the [[Stewards Council]] on February 8, 2008.

XDI Commons Charter

2008-03-17T19:55:28Z

DrummondReed: /* Requirements of Participation and How to Join */ + Google Groups link

=== Name ===

'''XDI Commons Working Group'''
* Requested Identity Commons mailing list: '''xdi --at-- idcommons.net'''

=== Purpose ===

The purpose of this working group is to advance practical deployment, usage, and best practices for the [http://en.wikipedia.org/wiki/XDI XDI (XRI Data Interchange)] protocol under development by the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee].

=== Principles ===

This working group will function according to the Identity Commons Principles (see [[Purpose And Principles]]).

=== Requirements of Participation and How to Join ===

Membership in this working group is open to any individual or organization interested in the advancement of XDI. To join, just add your name and OpenID-verifiable identifier to the member section below and also join the [http://groups.google.com/group/xdi-commons XDI Commons mailing list at Google Groups].

=== Licenses and/or Restrictions on Usage of Work Product ===

All XDI Commons work products will be open, public, royalty-free with no restrictions on usage. Any open source code developed under the auspices of the working group will also be available under popular open source licenses.

=== Current Deliverables and Milestones ===

* One initial focus will be on development and interoperation testing of implementations of the XDI RDF and XDI ATI models as described on the [http://wiki.oasis-open.org/xdi/ XDI TC wiki].
* Another initial focus will be on how [[http://www.oasis-open.org/committees/download.php/25531/xdi-rdf-model-v7.pdf XDI RDF] documents can provide i-tags functionality as described on the [http://www.itags.net/ i-tags wiki]. The XDI Commons charter replaces the former ItagsCharter.
* Further deliverables will be scheduled as necessary.

=== Current Meeting Schedule ===

There is not presently a regular meeting schedule. Discussion of XDI implementations, interoperability, best practices, etc. will takes place directly among working group members and on the XDI Commons mailing list as soon as it is available. Telecons or face-to-face meetings will be announced via this list.

=== Current Membership ===

* Mary Hodder (http://xri.net/=mary.hodder)
* Kaliya Hamlin (http://xri.net/=kaliya)
* Drummond Reed (http://xri.net/=drummond.reed)
* Andy Dale (http://xri.net/=andy.dale)
* Daniel Perry (http://xri.net/=dan.perry)
* Bill Barnhill (http://xri.net/=bill.barnhill)
* John Bradley (http://xri.net/=jbradley)
* Victor Grey (http://xri.net/=victor.grey)
* Kermit Snelson (http://xri.net/=kermit)
* Markus Sabadello (http://xri.net/=markus)
* Fen Labalme (http://xri.net/=fen)
* Paul Trevithick (http://xri.net/=paul.trevithick)

=== Current Stewards Council Representative and Alternate ===

* Representative: Andy Dale
* Alternate: Drummond Reed

=== Current Links ===

* [http://wiki.oasis-open.org/xdi/ OASIS XDI Technical Committee wiki]
* [http://en.wikipedia.org/wiki/XDI Wikipedia page on XDI]
* [http://www.itags.net I-Tags wiki]

=== History ===

Approved by the [[Stewards Council]] on February 8, 2008.

Organizational Structure

2008-03-17T17:51:45Z

DrummondReed: more wordsmithing

Identity Commons, inspired by the core principles of [http://www.chaordic.org/ Chaordic Commons], consists of [[Working Groups]] and a [[Stewards Council]]. The basic structure has been referred to as an "upside down umbrella" because the vast majority of the activities and decision-making occur within the Working Groups, which have tremendous autonomy -- so much so that a Working Group can be a complete separate legal or social entity whose own charter or incorporation need not make any mention of Identity Commons.

Any group of people and/or organizations who want to work together towards a purpose consistent with the [[Purpose And Principles]] may form a [[Working Group]], which will automatically become part of Identity Commons unless the Stewards Council raises a specific objection (the goal is a culture of inclusion). To form a [[Working Group]], the sponsors:
# Use the [[Working Group Charter Template]] to publish a charter on this wiki describing their purpose, process, requirements for participation, deliverables, and licenses/restrictions on use of their work product.
# Select one representative and one alternate to serve on the Stewards Council.
# Send an email to the [http://mail.idcommons.net/mailman/listinfo/community/ Community Mailing List].

The only purpose of the [[Stewards Council]] is to make organizational decisions for managing resources shared by all [[Working Groups]] in the Commons (such as this wiki). Decisions are made by a vote of the majority. The council consists solely of representatives from each [[Working Group]]. Its deliberative process is totally open and transparent, and anyone may participate. However, only [[Working Group]] representatives may vote on decisions.

Identity Commons is itself a not-for-profit legal entity so that it is able to hold any resources deemed necessary to be in the Commons by [[Working Groups]] that are not themselves structured to be able to hold such resources.

Organizational Structure

2008-03-17T17:44:41Z

DrummondReed: improved formatting

Identity Commons, inspired by the core principles of [http://www.chaordic.org/ Chaordic Commons], consists of [[Working Groups]] and a [[Stewards Council]]. The vast majority of the activities and decision-making occur within the Working Groups, which have a great deal of autonomy.

Any group of people and/or organizations who want to work together towards a purpose consistent with the [[Purpose And Principles]] may form a [[Working Group]], which will automatically become part of Identity Commons unless the Stewards Council raises a specific objection (the goal is a culture of inclusion). To form a [[Working Group]], the sponsors:
# Use the [[Working Group Charter Template]] to publish a charter on this wiki describing their purpose, process, requirements for participation, deliverables, and licenses/restrictions on use of their work product.
# Select one representative and one alternate to serve on the Stewards Council.
# Send an email to the [http://mail.idcommons.net/mailman/listinfo/community/ Community Mailing List].

The only purpose of the Stewards Council is to make organizational decisions for managing resources shared by all [[Working Groups]] in the Commons (such as this wiki). Decisions are made by a vote of the majority. The council consists solely of representatives from each Working Group. Its deliberative process is totally open and transparent, and anyone may participate. However, only Working Group representatives may vote on decisions.

Identity Commons is a not-for-profit legal entity that will hold any resources deemed necessary by working groups that are not themselves structured to be able to do so.

Working Group

2008-03-17T17:39:47Z

DrummondReed: Redirecting to Working Groups

#REDIRECT [[Working Groups]]

Purpose And Principles

2008-03-17T17:32:18Z

DrummondReed: /* Principles */

The following Purpose and Principles are the "core DNA" of Identity Commons as an organization. We use this term since all Identity Commons working groups agree to inherit these, i.e., each one is accomplishing a specialization of this Purpose, and each one is operating in accordance with a specialization of these Principles. See [[Background]] and see [http://wiki.idcommons.net/moin.cgi/IdentityCommonsTwoPurposeAndPrinciples our old Wiki] for more about how we got here. Feel free to leave comments or make suggestions as to how this statement of Purpose and these Principles can be further improved.

= Purpose =

The purpose of Identity Commons is to support, facilitate, and promote the creation of an open identity layer for the Internet, one that maximizes control, convenience, and privacy for the individual while encouraging the development of healthy, interoperable communities.

= Principles =

# '''Self-Organization.''' Enable any working group to self-organize at any time, on any scale, in any form, around any activity consistent with the Purpose and Principles.
# '''Transparency.''' Fully and transparently disclose the Purpose and Principles of each working group, any requirement of participation, and any license or restriction of usage of its work product.
# '''Inclusion.''' Conduct deliberations and make decisions by bodies and methods that reasonably represent all relevant and affected parties.
# '''Empowerment.''' Vest authority, perform functions, and use resources in the smallest or most local part that includes all relevant and affected parties.
# '''Collaboration.''' Resolve conflict without resort to economic, legal, or other duress.
# '''Openness.''' Conduct, publish, and archive communications in a manner that facilitates open and trusted interactions within and across all working groups and the public Internet.
# '''Dogfooding.''' When feasible and appropriate, employ the work product of Identity Commons working groups to facilitate the operation and interaction of Identity Commons itself.

== Short Version ==

# Self-organization
# Transparency
# Inclusion
# Empowerment
# Collaboration
# Openness
# Dogfooding

Organizational Structure

2008-03-08T01:48:38Z

DrummondReed: added reference to Chaordic Commons principles and edited for clarity

Identity Commons, inspired by the core principles of [http://www.chaordic.org/ Chaordic Commons], consists of [[Working Groups]] and a [[Stewards Council]]. The bulk of the activities and decision-making occur within the Working Groups, which have a great deal of autonomy.

Any group of people who want to work together towards a purpose consistent with the [[Purpose And Principles]] may form a [[Working Group]], which will automatically become part of Identity Commons unless the Stewards Council raises a specific objection (the goal is a culture of inclusion). To form a [[Working Group]], the sponsors use the [[Working Group Charter Template]] to publish a charter on this wiki describing their purpose, process, and deliverables. They must also select one representative and one alternate to serve on the Stewards Council.

The only purpose of the Stewards Council is to make organizational decisions for managing resources shared by all [[Working Groups]] in the Commons (such as this wiki). Decisions are made by a vote of the majority. The council consists solely of representatives from each Working Group. Its deliberative process is totally open and transparent, and anyone may participate. However, only Working Group representatives have a vote on decisions.

Identity Commons is a not-for-profit legal entity that will hold any resources deemed necessary by working groups that are not themselves structured to be able to do so.

Working Groups

2008-02-20T20:10:39Z

DrummondReed: moved I-Broker Commons under Social Agreements/Policy, wordsmithing

== About Working Groups ==

Working groups are the fundamental organizational unit of Identity Commons -- see [[Organizational Structure]].

* See [[Working Group Agreement]] for more about the relationship of working groups to Identity Commons.
* To propose a new working group, start with the [[Working Group Charter Template]].

Working Groups must have a charter that is consistent with our [[Purpose And Principles]], and it must appoint a Steward. The Steward serves as the Working Group's representative on the [[Stewards Council]] and has a vote on organizational-wide issues, including approving of new Working Groups. Working Groups are welcome to appoint one alternative to serve on the [[Stewards Council]] when the main Steward is not available to vote.

An individual may be appointed the Steward of multiple WorkingGroups; however, the individual will only get one vote.

== Active Groups ==

The following is a list of active groups. Click on the charter pages for a general description, or go directly to the working group's own home page (often an external website).

{{WGHeader}}
{{WGSection|name=Community, Events and Advocacy}}
|-
|Identity Gang || [[Identity Gang Charter]] || [[Identity Gang]]
|-
|Internet Identity Workshop || [[Internet Identity Workshop Charter]] || http://iiw.idcommons.net
|-
{{WGSection|name=Technology}}
|-
|OSIS || [[OsisCharter|OSIS Charter]] ||[http://wiki.idcommons.net/index.php/OSIS OSIS now on IdCommons.net]
|-
|OpenID || [[OpenID Charter]] || http://www.openid.net
|-
|Identity Schemas || [[Identity Schemas Charter]] || [[Identity Schemas]]
|-
|Higgins Project || [[Higgins Project Charter]] || http://eclipse.org/higgins
|-
|SAML Commons || [[SAML Commons Charter]] ||
|-
|XDI Commons || [[XDI Commons Charter]] ||
|-
{{WGSection|name=Social Agreements, Policy}}
|-
|Identity Rights Agreements || [[Identity Rights Agreements Charter]] || [[Identity Rights Agreements]]
|-
|XDI.org || [[XDI Org Charter]] || http://www.xdi.org
|-
|I-Broker Commons || [[Ibroker Commons Charter]] ||
|-
|Identity Futures Group || [[IdFutures Charter]] || [[Identity Futures]]
|-
|Identity Media Review Group || [[IdMedia Charter]] || [[IdMedia]]
|-
|VRM (Vendor Relationship Management)|| [[VRM Charter]] || http://projectvrm.org
|-
{{WGSection|name=Identity Commons Operations}}
|-
|Identity Commons Collaborative Tools || [[IC Collaborative Tools Charter]] || [[IC Collaborative Tools]]
|}

== In Progress ==

=== NEXT UP for Vote ===
These groups are formed and waiting for discussion and a vote.

{{WGHeader}}
|-
| Newbies4Newbies || [[Newbies4Newbies Charter]] || [[Newbies4Newbies]]
|-
|Enterprise Positioning ||[[Enterprise Positioning Charter]] || [[Enterprise Positioning]]
|-
|Enterprise Identity Architects Group || [[Enterprise Identity Architects Charter]] || [[Enterprise Identity Architects]]
|-
||Identity Commons Evangelism & Marketing || [[IC Evangelism & Marketing Charter]] || [[IC Evangelism & Marketing]]
|-
|Inclusive Initiatives || [[Inclusive Initiatives Charter]] || [[Inclusive Initiatives]]
|-
|Pamela Project || [[Pamela Project Charter]] || http://www.pamelaproject.com
|-
|Bandit Project || [[Bandit Project Charter]] || http://bandit-project.org
|-
| Identity & Trust || [[Identity Trust Charter]] ||
|}

=== Under Development ===
The following groups are ideas that people have for groups they are not ready for a vote:

{{WGHeader}}
|-
|Owen Davis Award || [[Owen Davis Award Charter]] || [[Owen Davis Award]]
|-
|Photo Group || [[Photo Group Charter]] || [[Photo Group]]
|-
|Data Sharing || [[DataSharing Charter]] || http://www.datasharingsummit.com
|-
| Usability of Identity Systems || [[Usability Charter]] || [[User-Centric Usability]]
|}

== Inactive Groups ==
The following is a list of working groups that are no longer active.
{{WGHeader}}
|-
| EUCLId || [http://oldwiki.idcommons.net/moin.cgi/EuclidCharter EuclidCharter] || Merged into the Identity & Trust WG
|-
|Standards Gang || [[Standards Gang Charter]] ||
|-
|I-Tags || [http://oldwiki.idcommons.net/moin.cgi/ItagsCharter Itags Charter] || [http://www.itags.net/ I-Tags] was merged into the XDI Commons WG
|-
|I-Broker Interoperation || [http://oldwiki.idcommons.net/moin.cgi/IbrokerInteroperationCharter Ibroker Interoperation Charter] || Was merged into the I-Broker Commons WG
|-
|XRI Registration Privacy || [http://oldwiki.idcommons.net/moin.cgi/XriRegistrationPrivacyCharter XRI Registration Privacy Charter] || Was merged into the I-Broker Commons WG
|-
|}
.

= Resources =

IdentityCommons WorkingGroups have access to shared resources. Initially, these resources consist of:
* A project page on the IdentityCommons web site
* Mailing list hosting on the IdentityCommons server.

= Quarterly Reports =

[[2007 Q4 Quarterly Reports]]

Working Group Charter Template

2008-02-06T22:42:42Z

DrummondReed: updated with new instructions and examples

''This is a template for an Identity Commons working group charter. To propose a working group, follow the steps below.''

# Copy this template page (hint: use a text editor) and fill it out with the specifics for your new working group.
# Post it as a new page to this wiki by:
## Adding a link to the new page name to the [[Working Groups]] page. The name of this new page should be "Name-Of-Your-Proposed-WG Charter", e.g., [[OSIS Charter]], [[Identity Rights Agreements Charter]], [[XDI Commons Charter]].
## Click on the link to get an editing box for the new page.
## Paste in your new charter text.
## Preview and save the new page.
# Once the charter is posted, send an email to the [http://mail.idcommons.net/mailman/listinfo/community/ Community mailing list] announcing the proposed working group and include a link to the proposed charter.

See the many existing charters listed on the [[Working Groups]] page as examples.

=== Name ===

Proposed-Name-Here Working Group

=== Purpose ===

''This should be a concise summary of the purpose of the working group, similar in function to the summary of Identity Commons itself -- see the PurposeAndPrinciples. Note that the purpose of the working group must be consistent with the overall purpose of Identity Commons.''

=== Principles ===

''Every working group 'inherits' the general principles of Identity Commons itself -- see [[Purpose And Principles]]. This section should list any additional operating principles of the working group -- IF ANY -- i.e., scope limitations, how membership will be managed, how it will be governed, how Stewards Council representatives are chosen, when its work will be considered complete, etc. Note that these working-group-specific principles cannot be in conflict with the general Identity Commons [[Purpose And Principles]]. If there are no working-group specific principles, just say, "This working group will operate by the Identity Commons principles."''

=== Practices ===

''This section should answer the question: How does the working group go about doing its work together?''

''Specifically, this section must state the tools/means by which the group will collaborate, i.e., it will use Identity Commons-hosted mailing lists and wiki resources, or it will use Yahoo Groups/Google Groups/other collaboration tools.''

Examples:
* A group that promotes interoperability of a technology may use Google Groups for mailing and document collaboration, host periodic interoperability events, and have a practice of publicly publishing the results.
* A group might state that it uses public Identity Commons-hosted mailing list and all its meeting notes must be publically published on posts to that list.
* A group might state that it is an open source foundation with annual dues-paying members and all its work will be on a dedicated public wiki.
* A group that hosts community events for which it charges fees to cover costs might have a practice that it contributes 15% of money it earns to general operating costs of Identity Commons.

=== Requirements of Participation and How to Join ===

''Each working group is required by the [[Purpose And Principles]] to state its requirements for participation, if any. It must also provide explicit instructions for how to join the working group.''

=== Licenses and/or Restrictions on Usage of Work Product ===

''Each working group is required by the [[Purpose And Principles]] to state any licenses and/or restrictions that may exist for the usage of its work product.''

=== Current Deliverables and Milestones ===

''List any deliverables planned or proposed by the working group together with the current proposed schedule/milestones.''

=== Current Meeting Schedule ===

''List any regular calls or meetings, if any, plus any special upcoming meetings.''

=== Current Membership ===

''Directly list current participants and participant categories (if any), and keep updated as membership evolves. Or, if the working group is already a formal organization or otherwise maintains its own Web-accessible directory of members, provide a link to that directory.''

=== Current Stewards Council Representative and Alternate ===

''List the active and alternative SC representatives. Describe how reps and alternates are chosen.''

=== Current Links ===

''List links to all Web-accessible resources, i.e., the working group's own wiki front page, website, mailing lists, or other repositories.''

=== Related Groups ===

''List any Identity Commons working group – or any other industry groups – whose work is closely related to the work of this group.''

OSIS

2008-01-14T23:20:50Z

DrummondReed: /* Resources */ + link

OSIS
__NOTOC__
<div style="background: #f0f0f0; text-align: center; padding: 2px;">This site accepts http://www.davidnicol.com/yadis/Yadis-logo-1_0_nicol_Y_16x16.png Yadis, http://signup.mylid.net/images/openid-small.gif OpenID and http://lid.netmesh.org/images/lid.png LID-enabled URLs and i-names. ([[Yadis_Support|More info]])</div>

<div style="text-align: center; background: #e0e0ff; margin: 20px; padding-top: 10px; border: 1px solid #8080ff;"><h1 style="font-size: 24px; border:0;">OSIS: The Open-Source Identity System</h1></div>

== Background ==

OSIS brings together many identity-related open-source [[projects]], and synchronizes and harmonizes the construction of an interoperable identity layer for the internet from open-source parts. Its first deliverable is interoperability with Microsoft CardSpace, although OSIS also encompasses alternate technologies such as OpenID and SAML.

OSIS was [http://wiki.idcommons.net/index.php/OsisCharter chartered] as an Identity Commons working group on September 15, 2006, electing:
* [http://virtualsoul.org Dale Olds], [http://www.bandit-project.org Bandit Project] ([http://www.novell.com Novell]), as its representative to Identity Commons
* Johannes Ernst, [http://netmesh.us/ NetMesh], as alternate.

The OSIS working group was created by [[OSIS Agreement|agreement]] of the involved parties on Monday, Jun 19, 2006. It arose out of discussions since about February 2006 between [http://www.microsoft.com/ Microsoft], [http://netmesh.us/ NetMesh] and [http://www.verisign.com/ Verisign]. OSIS is governed by a [[OSIS Steering Committee]] with broad participation from software vendors and open-source projects. OSIS has also stood for Open Source Identity Selector and Open Source Interoperability System

== Goals ==

Per [[OSIS Agreement]], the OSIS project brings together heads of open-source projects related to digital identity, in order
# to enable those projects to work independently, but aligned, so overlap of work is avoided, and the parts developed by different projects can fit
# to deliver an open-source identity selector as a joint effort of multiple projects, which is intended to be at least as functional, and fully compatible, with Microsoft's CardSpace (formerly known as InfoCard) identity selector that will be shipped with Windows Vista.

== Members ==

* OSIS Working Groups
** [[Interop Working Group]]
** F2F Meetings
* [[OSIS Steering Committee|Steering Committee]]

== Interoperability Resources ==
* [[Interop Wiki]] -- Links to current plans and previous interops. Lists of active interop components. Test Details, Results, Active updates for Interop Working Group
* [http://groups.google.com/group/user-centric-identity-interop Google Group ] -- Discussions, Meeting Minutes, Logistics Interoperability Working Group
* [http://groups.google.com/group/user-centric-identity-interop/web/user-centric-identity-interoperability Landing Page -- At Google Groups ] for non-Wiki resources

== Interop Events ==
==== RSA 2008 San Francisco USA: April 8-9 2008 ====

This is the current interop being conducted:
* [[I3 User-Centric Identity Interop through RSA 2008|User-Centric Identity Interop through RSA in April 2008]]

Planning is now underway. Discussion group is at:
* [[http://groups.google.com/group/user-centric-identity-interop User-Centric Identity Interop Google Group]]

Interop Plan
RSA Conference 2008
* What: RSA 2008 User-Centric Identity Interop Event
* When: April 8-9, 2008
* Where: Room 124 Moscone Convention Center, San Francisco CA USA
* Link: http://www.rsaconference.com/2008/US/Home.aspx
* Goals:
** Complete interoperability testing before conference begins
** Invite public to a demo room showing interoperability
** Host two days of working sessions between Interop participants
** Show continuous video loop to describe what the interop is doing, what you will see
* Logistical Contact: Charles Andres (CAndres@parityinc.net)

==== IIW 2007b Mountain View USA: Dec 2007 ====
OSIS members participated in a discussion of the detailed interop test plans, gathering at the IIW unconference to work together.

==== Catalyst Barcelona (Spain): October, 2007 ====
OSIS members will participate in an Interop in Barcelona, in conjunction with the [http://catalyst.burtongroup.com Burton Group Catalyst conference] there: participation is OPEN, if you are interested, please join the [http://mailman.netmesh.us/mailman/listinfo/osis-general OSIS-general] mailing list and ask for more information.

* [http://osis.netmesh.org/wiki/I2-Barcelona An overview and planning for the OSIS Interop Event 2, Barcelona] (OSIS wiki pages)
* [http://groups.google.com/group/osis-interop-barcelona07 Mailing list for Interop Event 2]
* [http://identityblog.burtongroup.com/bgidps/2007/08/a-call-for-part.html Burton Group call for participation]

==== Catalyst San Francisco USA: June 27, 2007 ====
OSIS members participated in a user-centric Identity Interop sponsored by the Burton Group carried out during the [http://catalyst.burtongroup.com Catalyst Conference], on the evening of June 27, 2007. The event was successful, with a well-attended demonstration at the event.
Further Information:
* [http://www.marketwire.com/mw/release_html_b1?release_id=252047 Press Release]
* [http://identityblog.burtongroup.com/bgidps/2007/08/recapping-the-c.html Burton Group Summary]

Interop Participant [http://osis.netmesh.org/wiki/Private:Catalyst_Interop_2007 Collaboration Page] (these pages are only for participants, you must have a valid OpenID approved by Johnannes Ernst to get to this link).

==== IIW 2007a Mountain View USA: May 2007 ====
OSIS members participated in a 'warm-up' to the Burton group Catalyst conference, gathering at the IIW unconference to work together.

== Recent News ==
* [http://virtualsoul.org/stuff/OSIS-for-IIW2007a.pdf Presentation from IIW 2007a]
* [http://osis.netmesh.org/wiki/Notes_from_IIW_2006b Notes from IIW 2006b]
* [[OSIS and the Open Specification Promise]]
* Microsoft: [http://www.microsoft.com/interop/osp/default.mspx Open Specification Promise]
* ZDNet: [http://blogs.zdnet.com/BTL/index.php?p=3229 OSIS links Internet identity systems] (coverage of the announcement at the Harvard/Berkman Identity Mashup Conference)
* Kim Cameron: [http://www.identityblog.com/?p=484 Open Source Identity Selector Announced]
* OSIS announcement at the Harvard/Berkman Identity Mashup Conference
* News.com: [http://news.com.com/Is+open+source+getting+to+Microsoft/2100-7344_3-6115914.html?tag=nefd.lede Is Open Source Getting to Microsoft?]

== Resources ==
* [http://spwiki.editme.com/InteroperabilitySpace Interoperability Space] --work in progress
* [[Microsoft Reference Materials]]
* [[Technical Insights]]
* Chuck Mortimore's implementation of InfoCard in the browser ([http://xmldap.blogspot.com/2006/05/firefox-identity-selector.html blog post])
* [[InfoCard Overview]] (implementation) by Kim Cameron at IIW
* [[High-level Architecture]]
* [[OSIS Selector Capability Advertisment]]

The following pages are earlier versions of similar pages on the newly expanded Interoperability Section -- link this!
* [[Interoperability Issues]]
* [[Use Cases]]
* [[Interop Use Cases]]
* [[Interoperability demonstrations]]
* [[http://osis.netmesh.org/wiki/Identity_Agent_Features Identity Agent Features]] Note that "Identity Agent" here refers to what is now termed "Identity Selector" or "I-card Selector".

== Mailing Lists ==

* General OSIS discussion ([http://mailman.netmesh.us/mailman/listinfo/osis-general Mailman])
* OSIS Steering Committee discussion ([http://mailman.netmesh.us/mailman/listinfo/osis-steering-committee Mailman])
* User-centric interop ([http://groups.google.com/group/user-centric-identity-interop Google Groups])
mailto: user-centric-identity-interop@googlegroups.com

Previous interop discussion
* Catalyst Barcelona interop preparation / discussion ([http://groups.google.com/group/osis-interop-barcelona07 Google Groups])

OSIS Selector Capability Advertisment

2008-01-14T20:48:12Z

DrummondReed: formatting improvements

The information card community has identified a need for a method where a selector (or selector-selector) can communicate capabilities prior to any transaction taking place. Discussions around the method by which selector data is advertised, the format used to advertise selector data, and the construction and content of the data itself will be summarized here.

== Currently Proposed Formats ==
=== Format 1 ===
Proposed by: A. Nennker

version='urn:osis:infocard:2008-04'; name='urn:osis:infocard:names:openinfocard'; capabilities='+nossl+javascript-issuerpolicy'

== Blog Posts ==
* [[http://feeds.feedburner.com/~r/Ignisvulpis/~3/214470023/id-selector-advertising-reloaded.html A. Nennker]]

== OSIS Meeting Notes ==
When adding new meeting notes, please place the newest notes at the top of this section

=== Meeting: 10 January 2008 (posted by M. Jones) ===
Thanks Pam. Here's a few additions and refinements from my notes.

We agreed that advertizing capabilities is better than advertizing software versions. We agreed that a new http header should be used for capabilities, and that, if optionally present, any software version information should not be in this header, but instead be in the userAgent string.

A desire was expressed that these capabilities should be discoverable on the client side as well.

While URNs were discussed, ultimately a consensus emerged that the HTTP header already provides sufficient scoping information, and so simple strings would do (and would be more bandwidth efficient).

While pluses and minuses were discussed, ultimately we decided to drop pluses because naming a capability without a "-" prefix would be equivalent to naming it with a "+" prefix.

To make this concrete, I believe that we agreed that these header values would be used to represent the capabilities of the software versions following them:

X-IdentitySelector: ISIPv1.0 Windows CardSpace in .NET 3.0
X-IdentitySelector: ISIPv1.0 noSSL Windows CardSpace in .NET 3.5
X-IdentitySelector: ISIPv1.0 -issuerPolicy openinfocard

Descriptions of other selectors are left as an exercise to the reader. ;-)

:-- Mike

=== Meeting: 10 January 2008 (posted by P. Dingle) ===
Identity Selector Capability Advertisement Meeting

Attendees:
:Dale Olds
:Ben Laurie
:Tom Carroll
:Paul Trevithick
:Tony Nadalin
:Mike Jones
:Andy Hodgkinson
:Daniel Sanders
:Drummond Reed
:Mary Ruddy
:Duane Buss
:Axel Nennker
:Pamela Dingle (taking notes, please let me know if anyone sees errors or omissions)

==== IPR ====
It was asked on the call, whether anyone was of the opinion that we
were creating any IPR by defining strings for advertising ID Selector
capabilities: nobody answered that they were concerned - on that
basis the group chose to proceed.

==== String Format ====
Several proposals have been made as to the format of the actual
string
* Tony noted that it may not be possible to know what the correct format is until we know what the string will actually communicate
* Both capabilities and software version information may be in the string
* The group agreed that capabilities are preferable
* The group also agreed that versions may be published but should NEVER be relied on
* Nobody wants to go down the path of lying about software brand or version in advertisements, we've seen where that can go with browser user agent strings.

==== Protocol/Advertisement Mechanism ====
* Some discussion went on around use of a userAgent HTTP Header vs. a new, distinct HTTP header
* Mike asked if anyone knew whether any web servers limited the HTTP Headers available to Relying Parties -- nobody knew of any issues, there are definitely no issues with Apache, people also thought that IIS was also fine.
* Tony noted that although we are talking about HTTP in this meeting, HTTP only addresses browser based scenarios
* Group asked what was appropriate for web-services based advertisement.
* This topic was tabled for now, it was agreed that we could separate the string semantics from the advertisement mechanism, and work on the semantics first.

==== String Content ====
* Group discussed URIs vs. bare strings to represent capabilities
* Concern was raised over the length issues around making every capability a URI
* Axel proposed use of the "osis" namespace, discussed his format, which he [http://ignisvulpis.blogspot.com/2008/01/id-selector-advertising-reloaded.html blogged this example]:

<pre>
version='urn:osis:infocard:2008-04'; name='urn:osis:infocard:names:openinfocard'; capabilities='+nossl+javascript-issuerpolicy'
</pre>

* The group discussed and expressed tentative acceptance of using + to denote explicit support for a capability, and - to denote explicit lack of support for a capability.
* Mike proposed an initial roll-up of capabilities called ISIPv1.0 which correlates to the set of capabilities inherent in the ISIP v1.0 document, plus an additional capability of nossl to denote support for Relying Parties who use HTTP instead of HTTPS for information card transactions.
* Dale noted that ISIP v1.0 as a roll-up is useful, but if subtraction is to be possible, there must be a finite, pre-defined, unchangeable set of capabilities encapsulated by that term, as a later redefinition of that term would become a nightmare from a product development/maintenance standpoint.
* Drummond noted that are we not talking about structured identifiers here? If so, there are already created formats for such things...

==== Capability Discovery ====
* Tony & Paul brought up the possibility that instead of specifying capabilities within the string, a MEX endpoint could be specified, such that the Relying Party could contact the MEX endpoint and discover capabilities.
* Lots of discussion on whether this is necessary or whether simplicity is better.
* Questions on exactly how much an RP will really chIdeange its behavior based on these capabilities.
* Pamela said that as an RP she would never want to incur the extra round trips, but that even in the case where an endpoint was advertised and her code chose not to do the discovery, her base need of detecting presence of a selector was satisfied, which mitigates any heavy objections she might otherwise have.
** Noted that other RPs could want this later.

==== Note for the Record ====
* Paul wanted it noted for the record that there is discomfort around the fact that we are creating capabilities for what he called a 'moving target' -- capabilities based on a proprietary document that community members do not have control over.

Main Page

2008-01-09T01:16:01Z

DrummondReed: /* Get Involved */ fixed broken links & reorganized

''NOTE: We are working on transitioning from the [http://oldwiki.idcommons.net/ old wiki] to this one. Please help us by moving content over!''

== Welcome to the Identity Commons Wiki ==

The purpose of Identity Commons is to support, facilitate, and promote the creation of an open identity layer for the Internet -- one that maximizes control, convenience, and privacy for the individual while encouraging the development of healthy, interoperable communities.

== Get Involved ==

* '''Join one of the [[Working Groups]]''' - Identity Commons is organized as a set of distributed working groups. See the [[Working Groups]] page for more information.
* '''Subscribe to the [http://mail.idcommons.net/mailman/listinfo/community/ IC Community Mailing List]''' - the publicly available list and list archives that accompany this wiki for discussion of topics affecting IC as a whole. Some of the [[Working Groups]] also have their own lists.
* '''Participate in telecons''' - See [[Stewards Council Telecons]] for information about how to participate in our quarterly (and sometimes more) calls, which are open to everyone in the Identity Commons community.
* '''Donate to ID Commons''' - Read [[How To Contribute]] to learn how to make a donation to Identity Commons to help cover basic operating expenses.
* '''Edit the ID Commons Wiki''' - Use your [http://en.wikipedia.org/wiki/Openid OpenID] URL or [http://en.wikipedia.org/wiki/Iname i-name] to login, and follow the instructions. See [[http://meta.wikimedia.org/wiki/Help:Contents Wikimedia Help]] for more information.

== Learn More About the Organization ==

* [[Working Groups]] - List of all Working Groups
* [[Background]] - A brief history. A longer [[History]]
* [[Purpose And Principles]] - The "core DNA" of the Identity Commons (IC).
* [[Organizational Structure]] - A short explanation of how and why IC is structured as an "upside down umbrella".
* [[Stewards Council]] - The coordinating body for IC working groups.
* [[Facilitating Dialogue]] - Explains the role of IC in providing a space for shared conversation.
* [[Working Group Agreement]] - The implied contract between a working group and IC as a whole.
* [[Working Group Charter Template]] - The template any working group sponsor(s) can use to form a working group.
* [[How We Collaborate]] - Information on how participants in IC work together.
* Organizational Details [[Articles Of Incorporation]], [[Bylaws]] [[Identity Commons Brand Transfer]].

== Learn More about the Identity Space ==
* [[Identity Landscape]] is a community-wide project to produce a living "map" of the Internet identity space, including efforts both inside and outside Identity Commons. All community members are invited to contribute.
* [[Identity Gang|The Identity Gang Working Group]] maintains a list of resources for the user-centric identity space.
* [[Lexicon]] is a project of the [[Identity Gang]] to harmonize vocabulary for user-centric identity architecture.

== Archive ==
* [http://oldwiki.idcommons.net/ The Original Identity Commons Wiki (2002-2007)]

Main Page

2007-12-13T07:19:32Z

DrummondReed: /* Archive */

''NOTE: We are working on transitioning from the [http://oldwiki.idcommons.net/ old wiki] to this one. Please help us by moving content over!''

== Welcome to the Identity Commons Wiki ==

The purpose of Identity Commons is to support, facilitate, and promote the creation of an open identity layer for the Internet -- one that maximizes control, convenience, and privacy for the individual while encouraging the development of healthy, interoperable communities.

== Get Involved ==

* '''Edit the ID Commons Wiki''' - Use your [[OpenID]] or [[i-name]] to login, and follow the instructions. Read [[Wiki Tips]] for some helpful wiki shortcuts and [[Help On Editing]] for text formatting tips.
* '''Donate to ID Commons''' - Read [[How To Contribute]] to learn how to make a donation to Identity Commons to help cover basic operating expenses.
* '''Join one of the [[Working Groups]]''' - Identity Commons is organized as a set of distributed working groups. See the [[Working Groups]] page for more information.
* '''Subscribe to the [http://mail.idcommons.net/mailman/listinfo/community/ IC Community Mailing List]''' - the publicly available list and list archives that accompany this wiki for discussion of topics affecting IC as a whole. Some of the [[Working Groups]] also have their own lists.
* '''Participate in telecons''' - See [[Stewards Council Telecons]] for information about how to participate in our quarterly (and sometimes more) calls, which are open to everyone in the Identity Commons community.

== Learn More About the Organization ==

* [[Working Groups]] - List of all Working Groups
* [[Background]] - A brief history. A longer [[History]]
* [[Purpose And Principles]] - The "core DNA" of the Identity Commons (IC).
* [[Organizational Structure]] - A short explanation of how and why IC is structured as an "upside down umbrella".
* [[Stewards Council]] - The coordinating body for IC working groups.
* [[Facilitating Dialogue]] - Explains the role of IC in providing a space for shared conversation.
* [[Working Group Agreement]] - The implied contract between a working group and IC as a whole.
* [[Working Group Charter Template]] - The template any working group sponsor(s) can use to form a working group.
* [[How We Collaborate]] - Information on how participants in IC work together.
* Organizational Details [[Articles Of Incorporation]], [[Bylaws]] [[Identity Commons Brand Transfer]].

== Learn More about the Identity Space ==
* [[Identity Landscape]] is a community-wide project to produce a living "map" of the Internet identity space, including efforts both inside and outside Identity Commons. All community members are invited to contribute.
* [[Identity Gang|The Identity Gang Working Group]] maintains a list of resources for the user-centric identity space.
* [[Lexicon]] is a project of the [[Identity Gang]] to harmonize vocabulary for user-centric identity architecture.

== Archive ==
* [http://oldwiki.idcommons.net/ The Original Identity Commons Wiki (2002-2007)]

XDI Commons Charter

2007-12-13T07:18:20Z

DrummondReed: /* Current Stewards Council Representative and Alternate */

=== Name ===

'''XDI Commons Working Group'''

* Proposed Identity Commons third-level domain: '''xdi.idcommons.net'''
* Requested Identity Commons mailing list: '''xdi --at-- idcommons.net'''

=== Purpose ===

The purpose of this working group is to advance practical deployment, usage, and best practices for the [http://en.wikipedia.org/wiki/XDI XDI (XRI Data Interchange)] protocol under development by the [http://www.oasis-open.org/committees/xdi OASIS XDI Technical Committee].

=== Principles ===

This working group will function according to the Identity Commons Principles (see PurposeAndPrinciples).

=== Requirements of Participation and How to Join ===

Membership in this working group is open to any individual or organization interested in the advancement of XDI. To join, just add your name and OpenID-verifiable identifier to the member section below.

=== Licenses and/or Restrictions on Usage of Work Product ===

All XDI Commons work products will be open, public, royalty-free with no restrictions on usage. Any open source code developed under the auspices of the working group will also be available under popular open source licenses.

=== Current Deliverables and Milestones ===

* One initial focus will be on development and interoperation testing of implementations of the XDI RDF and XDI ATI models as described on the [http://wiki.oasis-open.org/xdi/ XDI TC wiki].
* Another initial focus will be on how [[http://www.oasis-open.org/committees/download.php/25531/xdi-rdf-model-v7.pdf XDI RDF] documents can provide i-tags functionality as described on the [http://www.itags.net/ i-tags wiki]. The XDI Commons charter replaces the former ItagsCharter.
* Further deliverables will be scheduled as necessary.

=== Current Meeting Schedule ===

There is not presently a regular meeting schedule. Discussion of XDI implementations, interoperability, best practices, etc. will takes place directly among working group members and on the XDI Commons mailing list as soon as it is available. Telecons or face-to-face meetings will be announced via this list.

=== Current Membership ===

* Mary Hodder (http://xri.net/=mary.hodder)
* Kaliya Hamlin (http://xri.net/=kaliya)
* Drummond Reed (http://xri.net/=drummond.reed)
* Andy Dale (http://xri.net/=andy.dale)
* Daniel Perry (http://xri.net/=dan.perry)
* Bill Barnhill (http://xri.net/=bill.barnhill)
* John Bradley (http://xri.net/=jbradley)
* Victor Grey (http://xri.net/=victor.grey)
* Kermit Snelson (http://xri.net/=kermit)
* Markus Sabadello (http://xri.net/=markus)
* Fen Labalme (http://xri.net/=fen)

=== Current Stewards Council Representative and Alternate ===

* Representative: Andy Dale
* Alternate: Drummond Reed

=== Current Links ===

* [http://wiki.oasis-open.org/xdi/ OASIS XDI Technical Committee wiki]
* [http://en.wikipedia.org/wiki/XDI Wikipedia page on XDI]
* [http://www.itags.net I-Tags wiki]

Main Page

2007-12-06T20:59:24Z

DrummondReed: cleanup and organization

''NOTE: We are working on transitioning from the [http://oldwiki.idcommons.net/ old wiki] to this one. Please help us by moving content over!''

== Welcome to the Identity Commons Wiki ==

The purpose of Identity Commons is to support, facilitate, and promote the creation of an open identity layer for the Internet -- one that maximizes control, convenience, and privacy for the individual while encouraging the development of healthy, interoperable communities.

== Get Involved ==

* '''Edit the ID Commons Wiki''' - Use your [[OpenID]] or [[i-name]] to login, and follow the instructions. Read [[Wiki Tips]] for some helpful wiki shortcuts and [[Help On Editing]] for text formatting tips.
* '''Donate to ID Commons''' - Read [[How To Contribute]] to learn how to make a donation to Identity Commons to help cover basic operating expenses.
* '''Join one of the [[Working Groups]]''' - Identity Commons is organized as a set of distributed working groups. See the [[Working Groups]] page for more information.
* '''Subscribe to the [http://mail.idcommons.net/mailman/listinfo/community/ IC Community Mailing List]''' - the publicly available list and list archives that accompany this wiki for discussion of topics affecting IC as a whole. Some of the [[Working Groups]] also have their own lists.
* '''Participate in telecons''' - See [[Stewards Council Telecons]] for information about how to participate in our quarterly (and sometimes more) calls, which are open to everyone in the Identity Commons community.

== Learn More About the Organization ==

* [[Working Groups]] - List of all Working Groups
* [[Background]] - A brief history. A longer [[History]]
* [[Purpose And Principles]] - The "core DNA" of the Identity Commons (IC).
* [[Organizational Structure]] - A short explanation of how and why IC is structured as an "upside down umbrella".
* [[Stewards Council]] - The coordinating body for IC working groups.
* [[Facilitating Dialogue]] - Explains the role of IC in providing a space for shared conversation.
* [[Working Group Agreement]] - The implied contract between a working group and IC as a whole.
* [[Working Group Charter Template]] - The template any working group sponsor(s) can use to form a working group.
* [[How We Collaborate]] - Information on how participants in IC work together.
* Organizational Details [[Articles Of Incorporation]], [[Bylaws]] [[Identity Commons Brand Transfer]].

== Learn More about the Identity Space ==
* [[Identity Landscape]] is a community-wide project to produce a living "map" of the Internet identity space, including efforts both inside and outside Identity Commons. All community members are invited to contribute.
* [[Identity Gang|The Identity Gang Working Group]] maintains a list of resources for the user-centric identity space.
* [[Lexicon]] is a project of the [[Identity Gang]] to harmonize vocabulary for user-centric identity architecture.

== Archive ==
* [http://wiki.idcommons.net/ The Original Identity Commons Wiki (2002-2007)]

Identity Gang

2007-12-06T20:52:42Z

DrummondReed:

== About ==
The Identity Gang is a group of folks that found a common interest in user-centric identity and started meeting at events in 2004.

We have an active mailing list of over 400 people. If you would like to join feel free to just make a request of [mailto:paul@socialphysics.org Paul], [mailto:phil@windley.org Phil] or [mailto:identitywoman@gmail.com Kaliya]. The list contents are not public but are available to the members of the list (for list members, here is a [http://groups.google.com/group/idworkshop link to the archives]).

We no longer keep a wiki list of all active participants.

We are a Working Group of [[Identity Commons]] - see [[Identity Gang Charter|our charter]].

== Mission ==

To support the ongoing conversation about what is needed for a user-centric Internet identity layer that supports the whole marketplace, especially individuals.

== [[Lexicon]] ==
* The [[Lexicon]] is one of our main projects.

== [[Identipedia]] ==
* [http://www.identitygang.org/moin.cgi/Identipedia Identipedia] is a shared space where we can look at a range of definitions from a range of different communities. For example, if there are three different definitions of Trust from three different groups, all three will be listed along with a link to where the definition was drawn from. ''(Note: needs to be moved over to this wiki.)''

== [[Systemic Elements]] ==
* [http://www.identitygang.org/moin.cgi/Systemic_Elements Systemic Elements] is a list of the key elements in identity systems. ''(Note: } needs to be moved over to this wiki.''

== [[News Archive]] ==
* [http://www.identitygang.org/moin.cgi/News_Archive News Archive] tracks major news articles related to identity. ''(Note: needs to be moved over to this wiki.)''

== [[Reference]] ==
* [http://www.identitygang.org/moin.cgi/Reference Reference] has links to documents, blogs and related activities. ''(Note: needs to be moved over to this wiki.)''

* Oct 10 2006: [http://www.identitygang.org/moin.cgi/FrontPage?action=AttachFile&do=get&target=privacy_guidelines.doc Microsoft Privacy Guidelines for Developing Software Products and Services ]