OASIS ebXML Collaboration Protocol Profile and Agreement TC
ebXML CPPA Technical Committee Teleconference
March 8, 2002
James Bryce Clark
Minutes of the face-to-face and February meetings were
We discussed William Kammerer's posting on WEDi/SNIP
Electronic Trading Partner Agreements for HIPAA
and will consider a separate mailing list for such a
Dale noted that the spec is becoming more stable and
projected a two-week internal review period towards
the end of March, with a vote during the April voting
meeting. That would allow 60 days with a stable implementer's
version before submission to OASIS.
We discussed Dale's agenda items (highlighted in boldface).
1. Issue 194: isConfidential behavior remarks:
Proposed language to satisfy BPSS copy-save semantics
and a slightly weakened form of Tony's current intent
to satisfy Arvola. Sample words to allow MSH to decrypt
for application but to adhere to local confidentiality
"...persisted locally, and made available to the
application in accordance with local security policies
implemented to preserve confidentiality."
Discussion led to the following wording:
"...persisted locally in encrypted form,
and made available to the application in accordance
with local security policies implemented to preserve
2. SynchReplyMode Appendix E issue from Arvola.
Dale and Arvola will continue to work on this item.
3. Issue 155 SignatureElement, EncryptionElement
new attributes: oid,w3c,enumerationType,minimumStrength
We discussed changes made for version 1.10. Dale encouraged
everyone to read them. Dale and Hima will check to see
that OID is not needed for S/MIME.
4. SimplePart and wildcard symbol.
This will also be in the next draft. Our intent is
to allow specification of RosettaNet packaging. The
proposed solution also aligns with WSDL.
5. Constituent attributes to support representing
repetition, minOccurs and maxOccurs
Dale will update Appendix E to more carefully characterize
the corresponding matching process.
6. Constituent transform to enable agreement about
signing/encrypting Xpath or canonicalizing transforms.
Arvola will update the schema and send text to Tony
by Monday. Dale will accommodate the change in his Appendix.
Discussion deferred pending Peter Ogden's availability.
8. Business level retry-attribute name. Do we have
The question is, what name to use? The BPSS team decided
to stay with the name RetryCount, believing that it's
unambiguous in context. Arvola agreed that RetryCount
would work for us too, since it's under BusinessTransactionCharacteristics.
9. Move BusinessTransactionCharacteristics under
an ActionBinding element? (Hima proposal)
Arvola will change the schema and examples to place
BusinessTransactionCharacteristics under ThisPartyActionBinding.
10. ServiceBinding cardinality: Is more than one
We agreed to exactly one. Arvola will make changes
[General discussion follows.]
Hima suggested [something like] a requirement that
when there is more than one delivery channel for a given
service and action, each must have a different endpoint
URL. Hima will send a write-up to Tony by Monday.
Arvola asked whether we want to allow wildcards everywhere
for extension purposes. Tony will open an issue.
There will be another teleconference next week on March