[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [tc-announce] ebXML CPPA Committee Specification for consideration asOASIS Standard
OASIS members: The OASIS ebXML CPPA TC has submitted the Collaboration-Protocol Profile and Agreement Specification Version 2.0, which is an approved Committee Specification, for review and consideration for approval by OASIS members to become an OASIS Standard. In accordance with Section 2 of the OASIS Technical Process (see http://www.oasis-open.org/committees/process.shtml#sec2), OASIS members have one calender quarter to review this submission then 30 days for voting. The review will take place from 1 July to 30 September 2002, and I will call for a vote on 1 October 2002; each OASIS member organization will have a single vote on the ballot. During the member review period comments may be sent to the TC via the TC's comment list at ebxml-cppa-comment@lists.oasis-open.org. You must subscribe to the list first before posting; go to http://lists.oasis-open.org/ob/adm.pl. (An HTML form for submission of comments in a standardized XML format is also available at http://www.oasis-open.org/committees/ebxml-cppa/forms/issuesform.htm This form allows you to send your comment to the CPPA comment list.) The OASIS TC has supplied the following required items for OASIS members to review: ------------ The OASIS ebXML CPPA TC has approved "Collaboration-Protocol Profile and Agreement Specification Version 2.0" as a Committee Specification, and has voted to submit the specification to the OASIS membership for their review and consideration for approval as an OASIS Standard. The OASIS TC is providing the following required items for OASIS members to review: (a) formal specification that is a valid member of its type The OASIS ebXML CPPA specification is found at http://www.oasis-open.org/committees/ebxml-cppa/documents/ebcpp-2.0.pd f (b) appropriate documentation for the specification The specification includes its own documentation. Examples and schemas for the specification available at the following locations: Schema: http://www.oasis-open.org/committees/ebxml-cppa/schema/cpp-cpa-2_0a.xs d Examples: http://www.oasis-open.org/committees/ebxml-cppa/schema/cpa-example-2_0 a.xml http://www.oasis-open.org/committees/ebxml-cppa/schema/cpp-example-com panyA-2_0a.xml http://www.oasis-open.org/committees/ebxml-cppa/schema/cpp-example-com panyB-2_0a.xml http://www.oasis-open.org/committees/ebxml-cppa/schema/bpss-example-2_ 0a.xml http://www.oasis-open.org/committees/ebxml-cppa/schema/ebBPSS1.04.xsd (c) a clear English-language summary of the specification A Business Partner is an entity that engages in Business Transactions with another Business Partner(s). The Message-exchange capabilities of a Party may be described by a Collaboration-Protocol Profile (CPP). The Message-exchange agreement between two Parties may be described by a Collaboration-Protocol Agreement (CPA). A CPA may be created by computing the intersection of the two Partners' CPPs. Included in the CPP and CPA are details of transport, messaging, security constraints, and bindings to a Business-Process-Specification (or, for short, Process-Specification) document that contains the definition of the interactions between the two Parties while engaging in a specified electronic Business Collaboration. The way each Party can exchange information, in the context of a Business Collaboration, can be described by a Collaboration-Protocol Profile (CPP). The agreement between the Parties can be expressed as a Collaboration-Protocol Agreement (CPA). This specification defines and explains the information items, and their organization, that are present within documents conforming to the Collaboration-Protocol Profile andCollaboration-Protocol Agreement schema. (d) certification by at least three OASIS member organizations that they are successfully using the specification See the following mail messages for successful use statements and notes regarding IP: XML Global Technologies http://lists.oasis-open.org/archives/ebxml-cppa/200206/msg00002.html http://lists.oasis-open.org/archives/ebxml-cppa/200206/msg00031.html Sybase http://lists.oasis-open.org/archives/ebxml-cppa/200206/msg00006.html http://lists.oasis-open.org/archives/ebxml-cppa/200206/msg00034.html Cyclone Commerce http://lists.oasis-open.org/archives/ebxml-cppa/200205/msg00055.html http://lists.oasis-open.org/archives/ebxml-cppa/200206/msg00032.html (e) an account of or pointer to votes and comments received in any earlier attempts to standardize substantially the same specification, together with the originating TC's response to each comment This specification has not previously been submitted to OASIS membership, so there are no previous votes or comments to respond to. (f) a pointer to the publicly visible comments archive for the originating TC The archives of the TC mail list are available at http://lists.oasis-open.org/archives/ebxml-cppa/ TC meeting minutes are available on the TC's web page at http://www.oasis-open.org/committees/ebxml-cppa/minutes/index.shtml To date, no comments have been received through the public comment list for the ebXML CPPA TC. (g) a statement from the chair of the TC certifying that all members of the TC have been provided with a copy of the OASIS IPR policy. From Dale Moberg: "The TC chair certifies that all members have been provided with a copy of the OASIS IPR policy. The mail message found at http://lists.oasis-open.org/archives/ebxml-cppa/200108/msg00139.html states that all TC members must be made aware of the OASIS IPR policy and directs them to the on-line version of the policy." </karl> ================================================================= Karl F. Best OASIS - Director, Technical Operations +1 978.667.5115 x206 karl.best@oasis-open.org http://www.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC