OASIS ebXML Collaboration Protocol Profile and Agreement TC
ebXML CPPA Technical Committee Teleconference
January 17, 2002
Dale reported on his conversation with Karl Best about our committee's ability to override OASIS procedures for voting membership. According to Karl, a TC can take exceptional action on membership as long as it's fully documented in the minutes. Also, there is a "vacation option" during which absence is not counted against voting privileges.
Dale told us that he hasn't yet received feedback from Norm Walsh on using the OASIS namespace for enumerated values. An issue is maintenance of the values by OASIS.
Marty raised an issue, later written up by Dale as follows:
"Identify protocols, defaults, discovery and publication support, and/or automated negotiation and configuration processes that can support "spontaneous business process interactions," perhaps using lightweight protocols suitable for use by SME businesses. The automation level for these configuration and deployment mechanisms should be so high that it appears to the end user that no configuration is needed, but only an acceptance of some already worked out and available set of options. This issue can be shaped and modified by further information about the range of activities needing spontaneous business interactions by Small and "Medium Businesses (SMEs), and the range of technology options imposed by larger, and more technologically advanced, trading partners of the SMEs.
Background consists of messages in the thread [ebxml-msg] Messaging Spec v1.092 of January 2002."
Hima raised the matter of moving towards support for flow languages besides BPSS and suggested the use of #wildcard. He will write up an issue and send it to Tony W.
Dale pointed out an upcoming ebTWG meeting in Seattle and offered to send information to the list. He mentioned that we could create a subgroup to coordinate with ebTWG as needed. Dale also mentioned "talk" of an ebXML architecture TC - he's not yet clear on the intent. For example, he has asked whether the TC would it be normative for other TCs and noted that the question posed all sorts of difficulties. Dale urged everyone to follow developments. Marty expressed reservations about how the initial ebXML Architecture group specified requirements and made normative statements concerning other teams' specifications; he feels that such an Architecture group should instead produce a retroactive technical report pulling together the work of the other technical groups. Dale agreed and expressed his belief that since OASIS is a democratic organization, our voices would be heard.
The starting time for the F2F on the first day (a Monday) will be 8:30 am. Brian will try to be there by 8 am to have the door open. A continental breakfast and lunch will be served. Anyone planning to dial in to the F2F should notify Dale, who'll advise Brian accordingly.
Tony W. led a discussion of issues triage based on reports he previously distributed to the list:
Issue 11, Third-party security services, was targeted for version 2.0.
Issue 23, Intermediaries and Multihop Scenarios, was targeted for version 2.0.
Issue 27, CPA Use Cases, was targeted for version 2.0.
Issue 41, Nonrepudiation of business signals, was targeted for review prior to version 1.1, with Peter Ogden to clarify the specification regarding the distinction between NRR at the BP level and NRR at the MSG level.
Issue 78, Relationship between Acknowledgement, DeliveryReceipt,and BPSS
Business Signals, was targeted for version 1.1 with Peter Ogden responsible.
Issue 80, Advertise use of of NTP, XNTP etc. in CPP, was deferred for version 2.0.
Issue 86, Designation of mutually trusted third party, was targeted for version 2.0.
Issue 90, T2 Non repudiation and MSG, CPP/A, BPSS spec alignment, was deemed closed, subject to notification on the list.
Issue 144, CPP Categories, was targeted for version 2.0.
Issue 145, CPA Categories, was targeted for version 2.0.
Issue 169, Handling exceptions when synchronous messaging connection is lost, was targeted for version 2.0.
Issue 174, Implementation timeouts, was targeted for version 1.1 with Arvola responsible.
Issues with NULL Version
Issue 191, SMTP e-mail addresses and certificates, was targeted for version 1.1 with Dale responsible.
Issue 192, Names and usage of BusinessProcessCharacteristics attributes, was targeted for version 1.1 with Arvola responsible.
Issue 193, Enumerated types and unique identifiers for PartyID, was targeted for version 1.1 with Dale responsible.
Issue 194, Interpretation of confidentiality attribute in DeliveryChannel, was targeted for version 1.1 with Arvola, Hima, Peter O. and Tony W. responsible.
Issue 195, Require that Service value in message header agree with CPA, was deemed closed, subject to notification on the list.
Issue 196, Text about intermediaries specifically for version 1.1, was targeted for version 1.1, with Tony to remove the text indicated in the issue from the specification.
Issue 197, Context for interpretation/execution of BPSS, was targeted for version 2.0.
There will be another teleconference next week on January 24.