OASIS ebXML Collaboration Protocol Profile and Agreement TC

The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200105/msg00002.html

The charter for this TC is as follows.


OASIS ebXML Collaboration Protocol Profile and Agreement Technical Committee

Statement of Purpose

The committee will address the following matters:

  1. Maintenance of version 1.0 of the ebXML Collaboration-Protocol Profile and Agreement Specification (the CPP/CPA Specification, for short) including solicitation and collection of feedback on that specification, as well as possible development of minor follow-on versions to provide clarifications and/or minor technical corrections.
  2. Production of other documents, e.g., technical reports, white papers, implementation guidelines, and discussion of "best practices" to foster adoption of the specification.
  3. Gathering of requirements for new function from related OASIS and UN/CEFACT teams as well as other sources.
  4. Implement the advanced security functions discussed in the ebXML technical report "Technical Architecture Risk Assessment".
  5. Design other new function related to CPP and CPA, such as negotiation protocols.
  6. Creation of substantive new version(s) of the CPP/CPA specification.
  7. Coordination within OASIS and UN/CEFACT to ensure consistency with related committees. In particular, the committee will work with the ebXML coordination committee that OASIS and UN/CEFACT will jointly charter, and will track related specifications to ensure that the CPP/CPA specification is consistent with appropriate versions thereof.
  8. Proactive work with other recognized bodies, particularly with W3C activities and working groups related to web services. One specific example is the proposed W3C activity on WSDL. In addition, security work will be coordinated with ongoing work in W3C (e.g., XKMS) and OASIS (e.g. SAML)
  9. Provision of technical information to other bodies, for possible incorporation into their standards, for example as W3C notes. For example, the CPP includes many details about party properties, such as security properties, that have no counterpart in WSDL today.
  10. Assessment of specifications or other documents from other bodies, e.g., W3C, for possible inclusion by reference in future versions of the CPP/CPA specification.

List of Deliverables

4th Quarter, 2001
Assembly and Grouping of Residual and New Requirements and Assignment to SubGroups for Maintenance, new major versions and/or new Specifications. (See above items 3, 4, 5, 7, 8, 10.)

1st Quarter, 2002
Maintenance release of the CPP/CPA specification if warranted. (See items 1, 4, 7, 8.)

4th Quarter, 2002
Completion of any new major versions of the main Specification and any new Supporting Specifications (for example, Negotiation protocols). (See items 2, 4, 5, 6, 10.)

4th Quarter, 2002
Technical Committee reconsiders its charter and scope after its initial 18 month lifetime.