Page Comparison

(1) WG NAME (and any acronym or abbreviation of the name):  The WG name, acronym and abbreviation must not include trademarks not owned by the Organization, or content that is infringing, harmful, or inappropriate.

 
eGovernment Work Group (eGov)
 
(2) PURPOSE: Please provide a clear statement of purpose and justification why the proposed WG is necessary.
 
The eGovernment Work Group (eGov WG) will be responsible for:

...

provides an information sharing and feedback forum for Kantara members with an interest in eGovernment

...

to identify core federated identity requirements toward the development of the rules of engagement for operators of online privacy-preserving identity and access services for governments across its many jurisdictional sectors: national, regional and municipal.

Towards this end the eGov WG will:

Identify profiles of core requirements to address the unique aspects each government must address when binding policy to the technology of Federated Identity Management programs.

Collect government requirements for technical interoperability and assured Trusted Identities for assessment and approval under the Kantara Interoperability and assurance programs. 

Present a "government view" as well as information sharing and feedback to other Kantara Work Groups so that these views may be taken into account in the development of all Kantara Initiative Policy Recommendations and Specifications

...

including future

...

contributions to

...

appropriate Standards Setting

...

Organizations.

...

Promote the development, adoption and support for eGovernment deployment profiles of open specifications.

...

To accomplish this goal the eGov Work Group shall:

Provide Kantara with subject matter expertise on government-related requirements, challenges for existing and potential work areas

...

.

Where appropriate (e.g. employee able to represent his/her employer), take part in the identification, planning, execution and follow-up of Government-focused industry events and provide Kantara with spokespersons on eGovernment-related topics.

Where appropriate, recommend liaison relationships for Kantara that will further adopt and deploy OASIS SAML 2.0

...

, OAuth based Specification Sets

...

solutions or extensions thereof

...

.

Share solutions and/or technical approaches to avoid 'reinventing the wheel' and to drive adoption of standards-based identity management mechanisms in government on a global basis.

(3) SCOPE:   Explain the scope and definition of the planned work. 
 
Specific Objectives of the eGov Work Group shall include:
1. Continue to develop an operational checklist for the federation and trust aspects of deployments of OASIS SAML 2.0 and ID-WSF Specification Sets
2. Work in concert with other Kantara groups on further requirements e.g. but not limited to, refinement and promotion of privacy, security and legal Frameworks and Deployment Guidelines for Circles of Trust, IAF and SAC development and specifications as required

(4) DRAFT TECHNICAL SPECIFICATIONS: List Working Titles of draft Technical Specifications to be produced (if any), projected completion dates, and the Standards Setting Organization(s) to which they will be submitted upon approval by the Membership.

...

In respect to the Identity Assurance Framework (IAF 2.0); gather requirements for a context specific eGov profile of the IAF v2.0 Service Assessment Criteria (SACs) or component SACs, as they apply to governments acting in the roles of relying party, identity providers or attribute providers, providing authoritative sources of identity attributes, as applicable, and revise as new requirements emerge. Document eGov use cases requiring federation and identify and agree a common set and format of identity attributes used by governments.

In respect to authentication protocols; gather requirements for (and any suggested tests for) the Test Plan to test the presence of and SAML 2.0 conformance with the SAML 2.0 web browser SSO eGov Implementation Profile V2.0

...

The specifciations (other than those listed above) will be handed to the agreed most appropriate SDO(s) but not limited to; OASIS (eGov MS and SSTC), W3C (eGov), UN/CEFACT (eGov TBG19), WS-i, IDABC, APEC, ISO SC27, ITU-T and other sector based organizations as required.

 (5) OTHER DRAFT RECOMMENDATIONS: Other Draft Recommendations and projected completion dates for submission for All Member Ballot.

...

, for consumption by the Kantara Federation Interoperability Working Group, and ultimately the Interoperability Review Board.  Continue to develop an operational checklist for the federation and trust aspects of deployments of OASIS SAML 2.0, OAuth 2.0 based Specification Sets solutions or extensions thereof.  Continued input into the Authentication Context Level of Assurance Profile submitted to OASIS SSTC (ongoing as required)

...

(6) LEADERSHIP:  Proposed WG Chair and Editor(s) (if any) subject to confirmation by a vote of the WG Participants..

Work in concert with other Kantara groups on further requirements and formalization reflecting deployment experiences, for example (but not limited to); refinement and promotion of privacy, security and legal Frameworks, deployment guidelines for Circles of Trust, IAF and related SAC specifications as required, liability issues between Identity Providers surrounding public/private circles of trust.
 
 
(4) DRAFT TECHNICAL SPECIFICATIONS: 
 
No draft technical specifications are planned at this time.
Reports may be developed as appropriate and identified by the eGov WG. 
 
(5) OTHER DRAFT RECOMMENDATIONS: 
 
No other draft recommendations are planned at this time

(6) LEADERSHIP: 

At the time of this charter’s revision, following are the members of the leadership team:

Rainer Hoerbe, Kismed, Austria (Chair)
Keith Uber, Ubisecure, Finland (Secretary)
Colin Wallis, New Zealand Government, Department of Internal Affairs Affairs (interim Vice Chair)
To Be Advised (interim Deputy Chair) 
(7) AUDIENCE:  Anticipated audience or users of the work. 
 
International Government Security and Technology administrationsElectronic Service Delivery administrations and their applicable federated identity service organizations 
 
(8) DURATION: Objective criteria for determining when the work of the WG has been completed (or a statement that the WG is intended to be a standing WG to address work that is expected to be ongoing).

 
The Kantara Leadership Council  Council charters the eGovernment Work Group for five yearsone year, expiring in 2014.  The fixed in December 2014. The fixed end date is to allow for the current Specification work to complete, any subsequent work following the Recommendations to complete, and force and force a review of whether 'eGov' continues to pose significantly special or different challenges to those faced by other large enterprises, and whether a Discussion Group is a better forum for this domain. 
 
The charter may charter may be amended from time to time, with changes approved by the Leadership Council. 
 
(9) IPR POLICY: The Organization approved Intellectual Property Rights Policy under which the WG will operate. 
 
Creative Commons Attribution Share Alike optionAlike option
 
(10) RELATED WORK AND LIAISONS:  Related work being done in other WGs or other organizations and any proposed liaison with those other WGs or organizations. 
 
Kantara Work Groups (such as the ID-WSF Evolution WGIdentity Assurance WG, Privacy & Public Policy WG, Health Identity Assurance Work Group, Info Sharing WG and Federation Interoperability WG and others as they come into existence) as required. 

The expected liaisons with SDOs are: OASIS eGov Member Section, OASIS Transformational Government TC, Oasis Trust Elevation TC, OASIS Security Services TC, Open Identity Exchange (OIX), IETF, W3C eGov, UN/ CEFACT TBG19 (eGov), IDABC, APEC, ISO SC27 WG5, ITU-T and other sector based organizations and groups as required.

 Where the eGov WG contributes to existing liaison relationships which are subject to 3^rd party confidentiality (such as ITU-T and ISO) the eGov WG will manage such input through the Kantara Board of Trustee Liaison Sub-Committee. 

(11) CONTRIBUTIONS (optional):   A list of contributions that the proposers anticipate will be made to the WG. eGov Profile v1.5 Final
ID-WSF/WSTrust interface pilot in the Danish Health sector - findings

No contributions are expected at this time

(12) MEETING PROCEDURE:

Meetings will be conducted under The Chatham House Rule as the default (seesee http://www.chathamhouse.org.uk/about/chathamhouserule/ ). However, any individual making a statement retains the right to opt out of the rule and direct the minutes to record that same individual's attribution to the statement.

(13) PROPOSERS:  Names, email addresses, and any constituent affiliations of at least the minimum set of proposers required to support forming the WG.

The original proposers of the Work Group were:

• Rainer Hoerbe, KisMed, Austria, rainer (at) hoerbe (dot) at
• Colin Wallis, New Zealand Government, Department of Internal Affairs, colin (dot) wallis (at) dia (dot) govt (dot) nz
• Soren-Peter Nielsen, Danish National IT and Telecom Agency, spnKeith Uber, Ubisecure, Finland, keith (dot) uber (at) itstubisecure (dot) dkShin Adachi, NTT, shincom
• Ken Dagg, Government of Canada, Treasury Board Secretariat, kenneth (dot) dagg (at) adachitbs-sct (dot) usTrent Adams, Internet Society, adams(at)isoc(gc (dot) org ca
• Lena Kannappan, FuGen Solutions, Inc., lkannappanJohn Bradley, Ping Identity, jbradley (at) fugensolutionspingidentity (dot) com 

History