RE: [ebxml-cppa] Friday, March 1, 11 AM Teleconference Agenda & Numbers

[Arvola Chan <arvola@tibco.com>]

Dale:

Can we include discussion on the use of wildcard elements and attributes to
provide extensibility? Please see

http://lists.oasis-open.org/archives/ebxml-cppa/200202/msg00137.html

Thanks,
-Arvola

-----Original Message-----
From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com]
Sent: Wednesday, February 27, 2002 9:44 AM
To: ebxml-cppa@lists.oasis-open.org
Subject: [ebxml-cppa] Friday, March 1, 11 AM Teleconference Agenda &
Numbers



Thanks to David Fischer, Rik Drummond and the Drummond Group
for hosting the March CPPA teleconference calls.

Number:  1-800-503-2899
Code:      2947339

Agenda: (Please add those I have not listed
by replying to this message with the additions.)
The general agenda is to follow up on the
action items and unresolved issues from last
week's discussion.



Arvola issue spillover from last week:

1. Can section 8.2 on SchemaLocation attribute be eliminated?

2. Under the PartyInfo element, do we need to include a packageId
attribute
to identify the packaging to be used for non piggybacked MSH level
messages?

3. Do we need to beef up the discussions on ApplicationCertificateRef
and
ApplicationSecurityDetailsRef?

Pallavi's reports on BPSS-related issues to be discussed as needed:

4.Arvola, I just wanted to clarify that timetoPerform
in BPSS is present for both BinaryCollaboration and
BusinessTransactionActivity. -Pallavi

5.Issue 148:
The CPPA team can close the issue.
They should pick a reasonable URN for their example. Brian

6. Issue 87 BPSS team have agreed to add Business Level Retries
to the BPSS (retrycount added to RequestingBusinessActivity -
Aligns with UMM). The message id be different when a retried
from business process level and the receiving application will
 be responsible for detecting for business level duplicates
using the unique id((like a purchase order number) )
 in the business information.-Pallavi

Discussion deferred from last week: Continues.

7. Issue 194
Interpretation of confidentiality attribute in DeliveryChannel

 "It MUST be encrypted above the level of the transport and delivered,
     encrypted, to the application."

Too strong or just right?

To these, some small corrective or enhancement technical issues:

8. Remove id attribute on CollaborationRole element. No use case
presented.

9. Add attribute group for SignatureAlgorithm, EncryptionAlgorithm for
issues 155. Proposed attributes are: oid, xmldsig, xmlenc,
minimumKeystrength,
and possibly some others. To allow other standardized ways of referring
to
algorithms. Issue about what text values are allowed from Hima.

10. Enhance discussion of allowable MIME type values to include at least
a
wildcard symbol "*". Combine with repetition attributes on Constituent
element to allow capability to deal with generalized packaging of
attachments.
Combine with enhancement (through text) on interpretation of
CompositeList element's
cardinality. Enhance appendix E accordingly.

General: Review of action items from last week. Discussion of how to
handle drafts.
Survey of what items remain to be written and send to Tony.
CPA and Certificate Expiration additions sent to Tony under discussion
of End element. (issues 9, 227)

Appendix modifications sent, but there are still some remaining,
depending
on outcome of 9, 10  above. Also add the "Match Task Table" summary for
implementers.


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>