Author: David Layton
Last saved by: SimonscottA
Company: Department Of The Navy Chief Information Office

** DRAFT **
Ver 1.0, 26 Feb 03

OASIS E-Gov TC
Web Services / ebXML Subcommittee (SC) Charter

Scope and Purpose:

The SC is concerned with the application of XML based  technologies in the government arena, with a focus on those requirements that are inherently governmental in nature (e.g., law enforcement, defense, diplomacy).  Although the initial focus will be on ebXML and web services technologies, the scope includes consideration of future and emerging technologies based on the XML paradigm, which in the opinion of the SC have significant application or implications for the delivery of e-government services.  Specifically, the SC shall:

•	Serve as coordinator and advocate of government requirements for consideration by any of the various open standards and specifications initiatives dealing with ebXML and web service technologies (e.g., other OASIS TCs, WC3, UN/CEFACT).  This includes providing a forum to identify and vet government requirements for ebXML and web services technologies, and proactively engaging with relevant standards and specifications initiatives to ensure that government requirements are understood and considered by these initiatives, wherever the products of such initiatives could affect the delivery of government services.

•	Encourage, foster and help enable broad adoption of ebXML and web services technologies in the government arena, with an emphasis on the application of these technologies to enhance G2G (both vertical and horizontal) interoperability.  This includes articulation of how and when governments should use ebXML and web service technologies, and the timescale for adoption of the technologies based on the maturity of the standards and availability of products that implement these standards. 

•	Identify and provide guidance and recommendations on public policy issues related to the adoption and deployment of ebXML and web service technology solutions in the government arena. 

Deliverables:

•	Distinguish among ebXML and other web services technologies exhibiting different levels of procedural granularity and identify the government application categories best suited to each approach. (White paper)

•	Develop recommendations on how to encourage and enable the widespread adoption and use of the appropriate web services model for each application category across vertical government entities (international, national, state/provincial and local).  This includes development of a maturity forecast and timeline for “mainstream” adoption of the technology, and identification and analysis of the barriers to adoption of the technology, with recommendations and strategies for overcoming them. (White Paper)  
Identify key public policy issues regarding government’s usage of ebXML and web services technologies and develop recommendations (including rationale) for the government’s response to and position on such issues.  Candidate issue areas for consideration include: ownership of the technology’s governance process, support by international trade organizations (e.g., WTO)  and other international consortia (e.g., BIS, WCO), common trust models, licensing and charge-back models, etc. (White Paper)

•	Identify and document generic business case examples for ebXML and web service solution proposals, targeted for executive government decision makers (typically business oriented and non-technical) responsible for funding and sponsoring ebXML and web service projects.  This would include elaboration of the alternatives, risks and expected benefits.  Because these factors require context in order to be quantified, the business case should take the form of a reusable template that can be modified as needed in the context of a particular proposal. (White paper / template)

•	Identify and facilitate (through partnership with industry and/or volunteer government agencies) development of a pilot web services and/or ebXML solution as a proof of concept and showcase for the value and potential of the technology.  Either or both technologies may be piloted, depending upon available resources and opportunities.  The pilot should focus on some common but inherently governmental process or problem, and preferably involve government-to-government (G2G) integration amongst multi-national entities. (Technical solution).

Timeline and Priorities:

•	The list and definition of deliverables is subject to change at the descretion of the SC (by consensus vote) and in consultation with the TC Chairperson.

•	The priority, need dates and sequence of deliverables shall be determined by SC consensus, in consultation with the TC Chairperson.  Depending upon the priorities and availablity of resources, some deliverables may be deferred for future action.

•	Deliverables shall be released in incremental fashion, wherever possible, to enable collection and incorporation of feedback as early in the deliverable development process as possible.