|Subject:||[ebxml-cppa] Re: My contributions to the 1.04 draft|
|From:||Tony Weida (rwe...@hotmail.com)|
|Date:||Jan 17, 2002 12:03:21 pm|
As agreed during today's call, I'll close out the following issues unless someone objects by EOD Monday:
- Issues identified by Arvola in the attachment to his message below, except for Issue 78 which will remain open for version 1.1 (Peter Ogden to investigate) - Issue 195: Require that Service value in message header agree with CPA
----- Original Message ----- From: Arvola Chan To: Tony Weida ; CPPA Sent: Wednesday, January 16, 2002 6:45 PM Subject: My contributions to the 1.04 draft Tony:
Attached is a zip package which contains my contributions to the 1.04 draft.
The file AddressedIssues.doc identifies issues in the issue database that I believe have been addressed in the current draft.
The changes I have made to the 1.03 draft to arrive at the current draft include:
1. Clarify that ReceiptAcknowledgment, AcceptanceAcknowledgment, and Exception are the values for the action attribute that should be used for business signals. 2. Move syncReplyMode attribute from BusinessProcessCharacteristics to MessagingCharacteristics. 3. Clarify meaning of RetryInterval. 4. Clarify meaning of PersistDuration. 5. Added xlink:role attribute to SimplePart to be consistent with Reference element in message header. 6. Clarify that cpaid attribute in CollaborationProtocolAgreement element MUST be used as CPAId in ebXML Message Header. 7. Clarify that the max cardinality for ds:Signature should be 3. 8. Update synchronous reply mode examples in the sample CPPs and CPA by introducing a second ServiceBinding. 9. Mention use of wildcard elements for extensibility purposes in Appendix D. 10. Added comments about the requirement for explicit declaration of the xml namespace by some parsers in draft-cpp-cpa-011.xsd. 11. Add normative appendix summarizing correspondence between Messaging parameters and CPP/A elements and attributes as Appendix G.
The latest CPPA issues database is attached in a zip file, together with external RTF versions of several reports within the database.
Reports for discussion during the next call:
1. Version TBD issues (12 issues whose target version was explicitly left open at the last F2F) 2. Version NULL issues (7 new issues) 3. Unresolved and Unassigned Version 1_1 Issues (90 issues without a responsible party)
The first report is the same as distributed yesterday, but with a corrected heading.
Regarding the first two reports, I suggest a default target version of 2.0 in the absence of specific interest (read volunteers) for version 1.1.
The latest updates reflect:
- Decisions made during the last teleconference - Seven new issues - Closed issues based on Peter Ogden's changes 2, 31, 93, 102, 118 - Closed issue 161 (Numbering of subsections within section 7.5.8) per Arvola's version 1.01 updates - Closed issue 185 (Warn readers about non-normative nature of PartyRef) per Jean's version 1.01 updates
I've identified about a dozen more issues that can probably be closed out thanks to Arvola's updates. He plans to prepare a table of his own today, so we should soon be able to reduce the issues in the third report accordingly.
Assignments for reviewing issues (not to be confused with resolving issues) will be made along the lines proposed by Dale at the last teleconference and distributed shortly.
Cheers, Tony Weida