Colleen,
Regarding the original TRP Requirements spec: Since the TRP requirements
spec has not been kept up to date, I believe that the answer is that you
don't mention it or reference it. You could put it on the team's OASIS
page for reference by team members but it isn't something that will be of
interest to users of the spec, especially if it is not updated.
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown
Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
Colleen Evans <> on 09/25/2001 05:31:04 PM
To:
Arvola Chan <>
cc:
ebXML Msg <>
Subject: Re: revised-ebMS V1.01 Editorial changes
Arvola,
Thanks for the quick feedback.� Comments inline.
Colleen
Arvola Chan wrote: Colleen:
Here is some feedback on the V1.01 editorial changes:
- [ebMSREQ] may be an inappropriate reference. The document is not
� among those that came out of the Vienna meeting and is probably out of
� date and not easily accessible. Any suggestions from the group regarding
how we point to original requirements if this is no longer a valid
document?
- Figure 7-1 is still not quite correct. The Header Container arrow should
� point to the rectangle enclosing SOAP-ENV:Header, not to the one
� enclosing SOAP-ENV:Envelope.� There seems to be some disagreement here.
The original change request from Dan Weinreb indicated the header container
arrow should point to the MIME Part box, so that's how I revised it.� Maybe
we need some further discussion on this one.� (Issue #69:
http://lists.oasis-open.org/archives/ebxml-msg/200108/msg00162.html)
- There are minor problems in the signature example on page 60. The
�� backward slash towards the end of line 2279 should be a forward
�� slash instead. The namespace declaration for the dsig prefix on line
�� 2282 is unnecessary.� I'll fix.
- The eb:version="1.0" setting in the various examples should be updated
�� to eb:version="1.1". Yes.
- Line 1743 should say "an ErrorList element with the highest severity
� attribute set to Error" to be consistent with line 1748.� The intent is
to say� that an ErrorList element should NEVER be present with a
StatusRequest element, which makes its severity attribute setting
immaterial, so I believe this is okay as it is unless we need to rework to
add clarification.� See line 1750-1752.
- One bullet should be added after line 1756: * a StatusRequest element.
See above comment.- Replace the schema definition with the attached XSD
file content to
� ensure that Appendix A and the separately available XSD file are
� consistent. I have found one problem in the updated XSD I sent you
� earlier: the ackRequested attribute was not declared with the right
� data type. I have also updated the schema locations to point to
� http://www.oasis-open.org/committees/ebxml-msg/schemas
Will do.
Cheers,
Arvola
