[ebxml-cppa-negot] Dale Moberg's 11/19/02 comments on draft

[Martin W Sachs <mwsachs@us.ibm.com>]

The following of Dale's 11/19/02 comment set are still open.  Here are my
responses:


Line 1122: I do not understand assumption

MWS:  This statement in the 10/17/02 draft is not correct.

-     Dale” In counter-proposals, elements that are not listed as
“add/delete/update” are accepted as is.”? I see this assumption as simply
clarifying that you must list as added, deleted, or updated everything you
wish to alter in the counter-proposal.

MWS:  Accepted elements must be listed as accepted.  Items not listed under
add, delete, update, and accepted have not yet been negotiated.
I believe that the about-to-be issued draft is much clearer in these
matters.

-     Do we care that delete and add can suffice for update?

MWS:  Delete and add (in separate iterations) do not suffice for an update
since once an item is negotiated (in this case, deleted), there is no going
back to it (this is stated in the draft and has been generally agreed to).
I guess that delete and add in the same message could be equivalent to
update if we were to add a rule that if an item appears under both delete
and add, the meaning is "delete followed by add".  To me this seems more
complex than having a separate category of "update".

Or is the worry about inserted?

MWS:  My only concern about "inserted" is that we don't yet clearly explain
what can be inserted and under what conditions (i.e. what has to be in the
NDD)?  Is there another problem?
-
      Line 1279: How is status indicated

Status attribute gets value from an enumeration:

               <enumeration value="Offer"/>
       <enumeration value="CounterOffer"/>
       <enumeration value="CounterPending"/>
       <enumeration value="Rejected"/>
       <enumeration value="Accepted"/>
       <enumeration value="Expired"/>
       <enumeration value="SinglePartySigned"/>
       <enumeration value="Signed"/>

The values in the text seem incomplete. Also we should not put whitespace
in these terms when talking about the enumeration IMO.

MWS: I am adding this as two loose ends:
- The set of values may be incomplete.  Are there any thoughts on what
should be added?  Incidentally, it's now called MessageType. Please note
that the new draft includes an error element, with an enumeration of
values, that   expands on "Rejected".
-  White space:  At the moment, the only white space in the text is in
"Counter Offer" and that's a typo; there is no white space in the schema.

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
*************************************************************************************