RE: ebxml Messaging Services spec v 0.2

["Burdett, David" <david.burdett@commerceone.com>]

See comments inline ...

David


-----Original Message-----
From: Martin W Sachs/Watson/IBM [mailto:mwsachs@us.ibm.com]
Sent: Tuesday, September 12, 2000 7:37 AM
To: Burdett, David
Subject: Re: ebxml Messaging Services spec v 0.2



I vote yes, with some small "conditions".

Please add the following editorial comments to the deferred list:

3.3.3  MessageData

Lines 454-456:  The DTD has an attribute on RefToMessageId.  The attribute
should be described here or, if it is spurious, removed from the DTD.  I
submitted this as commment 131, which appears to have been overlooked.

This says ...

<!ELEMENT RefToMessageId  (#PCDATA )>
<!ATTLIST RefToMessageId  e-dtype NMTOKEN  #FIXED 'uuid' >

This is OK because it is an e-dtype. There is a convention for use with DTD
that involves "FIXED" attributes which means that *even if the attribute
value is not present* then the value of the attribute can be derived from
the DTD. In this case the "e-dtype" is an "element datatype". Therefore no
change.

4. Normative References

Line 479, rfc 2392:  Please correct the text of this reference - replace
2111 by 2392.

Fixed. Also changed 2111 to 2392 on line 379

Appendix B, examples:

Comment 161 appears to have been misinterpreted, based on the note in the
following covering letter.  This is not a matter of new examples.  Rather,
the header tag in both examples (lines 758-767 and 1021-1030) has to be
updated to conform to the definition in the text.  Please check that the
description of the comment in the current list of deferred comments
reflects this point.

DONE - see response to Nikola's email

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



"Burdett, David" <david.burdett@commerceone.com> on 09/11/2000 02:12:17 PM

To:   "ebXML Transport (E-mail)" <ebxml-transport@lists.ebxml.org>
cc:
Subject:  ebxml Messaging Services spec v 0.2



Folks

Here's the updated messaging service spec. I've done all the changes apart
from those described below.

There are two file formats:
1. A PDF format - this is the ONLY format that should be used when quoting
line numbers
2. The Microsoft Word format - you can use this to compare with the
previous
version if you want to.

In order to get this out sooner, I haven't done a final proof read -
although it has been spell checked and grammar checked.

David
------------
Outstanding changes

In making the changes I found the following problems which I meant I
couldn't quite make the changes as agreed ...

1. I've changed section 2.2.1 Content Type to reference two mandatory
attributes (type and boundary) and two optional (version and charset) as
there are four attributes not two !!
2. Still not clear when version or versionless ebXML Header Envelopes
should
be used.
3. There is a difference in the style of writing and usage of MS Word
headings between the "packaging specification" part of the spec and the
"ebXML header document" part of the spec. Suggest reworking the ebXML
Header
Document part of the spec to be in the same style as the packaging spec and
adding Word headings.
4. Changed status of Marty's changes 105 to 108 to Defer as they are
technical change and not an editorial change and I could not see any way to
express the solution clearly.
5. Changed status Gordon's changes to Message Type (change 114) since I we
have not discussed or agreed what the changes should be.
6. Not sure that the Schema has been updated correctly to reflect changes
to
DocumentReference.
7. Moved agreed changes refs 124 to 127 (about PartyId) back to suggested
changes as we are still discussing these.
8. Not done change 153 (remove detail of the XML Documents) as think it
probably needs some discussion
9. Can't do change 156, as I don't know who should (or should not) be there
10. Can't do changes 160, 161 - no new examples for Appendix B
11. Also deleted reference to the glossary in General Conventions since it
is covered in Notational Conventions

I'll send out an updated change list that reflects the above soon.

 <<ebXML Messaging Service Specification v0-2.doc>>  <<ebXML Messaging
Service Specification v0-2.pdf>>

Product Management, CommerceOne
4400 Rosewood Drive 3rd Fl, Bldg 4, Pleasanton, CA 94588, USA
Tel: +1 (925) 520 4422 (also voicemail); Pager: +1 (888) 936 9599
mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com