Dale urged OASIS company representatives to vote on the ebXML Messaging 2.0 specification.
Dale reported on the initial JC discussion of long term maintenance of ebXML. Registry and Messaging expressed an intent to continue beyond the December 2002 rechartering decision point. Dale expressed a willingness to consider merger of the CPPA TC into an umbrella TC ebXML group or perhaps into Messaging. While CPPA does have a firm commitment to the Negotiation deliverable, the other subteams have lost team leaders and, with the exception of BTP, are now only in a research phase, and being jointly worked on with BPSS. Tony expressed his desire to retain the TC at least until the first part of 2003. Dale encouraged him to think about finishing the BTP support additions for a small minor version (2.1) of the core specification in the first months of 2003. Dale urged all TC members to be thinking about how and whether to recharter the TC at the rechartering decision point (around the end of this year or the first months of 2003).
The group proposed and agreed to the following "intended" compatibility information for the ebXML JCC (UN/CEFACT plus OASIS):
CPPA 1.0 and 2.0 "works with" any announced version of ebXML Registry. [This means that both CPPs or CPA-templates of either version can be stored within ebXML Registries. Registry should state whether their messaging constructs can be described using CPPs or CPA-templates.]
CPPA 2.0 is intended to work with BPSS 1.05 [a 2.0 candidate] and 1.0. CPPA 1.0 works with BPSS 1.0.
CPPA 1.0 works with Messaging 1.0
CPPA 2.0 works with Messaging 2.0.
Discussion of the Resolution seemed to reveal 1. some reservations about wording, 2. some approval of content, 3. an intent to decide on whether to submit a mail ballot for voting during the August 9 voting meeting.