Tony:
In the past, I have highlighted an entire section and
indicated that section is to be modified with someone else's changes. Once the
changes have been made, I would prefer to see the highlighting
removed.
I will make an attempt to get rid of some of the
highlighting/comments I have previously introduced, as I work on the 1.04
draft.
Thanks,
-Arvola
Arvola,
Regarding the merge of your changes with Peter's,
I should have mentioned in in my email accompanying version 1.03
that he encountered some difficulties with Word, which he described as
follows: "I was partially successful at just merging [Arvola's] changes
with mine, but then Word hosed me and I had to do the rest by hand (so some of
his changes look like they were made by me)."
As for highlights and comments, I said that I'd accept
all revisions for a given version before beginning work on the next
version and I've done just that. Changes that introduce highlights and
comments become "accepted" parts of the document just like any other
changes when using Word's "accept all" feature (which is the right behavior,
IMHO). I don't recall any discussion about treating them
differently. When you make your revisions for version 1.04, please feel
free to update or remove your comments/highlights as
appropriate. If you really want them all removed, let me know and I'll
be happy to undertake that as part of my editorial duties. Note
that I did manually modify some comments and/or
highlights to reflect changes that I made manually in a given version.
I'll send you a version of the document with the result
of applying Word's "accept all" changes operation to version 1.03 in
separate email -- Word indicates that no tracked changes remain. Please
go ahead with the changes that you proposed.
Thanks,
Tony
----- Original Message -----
Sent: Monday, January 14, 2002 6:22
PM
Subject: Re: [ebxml-cppa] CPPA version
1.03
Tony:
I like to propose making the following changes in the 1.04
draft:
- Move syncReplyMode attribute from
BusinessProcessCharacteristics to MessagingCharacteristics.
- Claification of PersistDuration attribute. (It applies
also to the response message.)
- Add notes about declaration of the xml namespace, plus
comments within the schema itself.
- Replace use of NMTOKEN with Name.
- Update CPP and CPA examples to illustrate use of
synchronous reply mode.
- Add normative appendix to show mapping between message
header element (plus implicit parameters) and CPA elements.
Can you please send me a version of the Word document with
appropriate changes accepted, for use as starting point for my new edits?
For some reason, a number of the highlight/comments introduced in the 1.01
draft still show up in the 1.03 draft. This is contrary to what we have
agreed to, i.e., accepting essentially all prior changes before working on a
new version, so that all revisions introduced in a new version can be
discerned easily. I tried removing some of the old highlighting when I sent
my changes to Peter last week. However, they became lost when my version was
merged into Peter's version.
Thanks,
-Arvola
CPPA version 1.03 is attached. The zip
file includes the specification, the XSD, an example CPA, and example
CPPs. Feedback on this version of the specification will be
accepted through Friday, January 18.
Changes from
Arvola include:
ebcpp 1.03.doc: please refer to change tracking within
the Word document
3A4.xml: updated uuid for business process as
bpid:icann:rosettanet.org:3A4$2.0
draft-cpa-example-09.xml: updated service name as
bpid:icann:rosettanet.org:3A4$2.0
draft-cpp-example-companyA-09.xml: updated service
name as bpid:icann:rosettanet.org:3A4$2.0
draft-cpp-example-companyB-09.xml: updated service
name as bpid:icann:rosettanet.org:3A4$2.0
draft-cpp-cpa-09.xsd:added wildcard elements including
the one under ActionContext requested by
Hima/Tony.
Changes from Peter Ogden include:
ebcpp
1.03.doc:
Mainly changes related
to SecurityDetails, *SecurityDetailsRef, *CertificateRef,
TransportSender, TransportReceiver, ebXMLSenderBinding,
ebXMLReceiverBinding. MS-Word change tracking should give you the
details.
draft-cpp-cpa-010.xsd:
1. Removed
the trustId attribute of the TrustAnchors element - it was
unused.
2. Under
[Sender/Receiver]NonRepudiation, renamed Protocol element to
NonRepudiationProtocol.
3. Under
[Sender/Receiver]DigitalEnvelop, renamed Protocol element to
DigitalEnvelopeProtocol.
4. Under Transport[Sender/Receiver],
renamed Protocol element to TransportProtocol.
5. Under TransportSender, renamed
TransportSenderSecurity element to TransportClientSecurity.
6. Under TransportReceiver, renamed
TransportReceiverSecurity element to
TransportServerSecurity.
7. Under TransportReceiver, change
cardinality of Endpoint element from exactly one to one or more.
8. Under
Transport[Client/Server]Security, renamed Protocol element to
TransportSecurityProtocol.
9. Under
ebXML[Sender/Receiver]Binding, made the version attribute
required.
I updated the examples
(draft-cpp-example-companyA-010.xml, draft-cpp-example-companyB-010.xml,
draft-cpa-example-010.xml) to
reflect the changes made to the schema.
My own token changes include:
Resolved issue 64: Title of XSD Appendix
Several clerical changes
I expect to make more substantive changes for
the next version.
Cheers,
Tony
Weida
|