OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Comments on MS v0-21


Note: This has not been sent to any other list as Klaus'
message was not clear as to where comments should go.

Henry
----------------------------------
Comments on ebXML Messaging Service, V0-21, 13 Sept. 2000
from Henry Lowe, 6 Oct. 2000

Line 172: it is possible to carry more than one document in
  the payload.  So, text should be modified to read:
  "XML or other document(s) for the ebXML Payload."

Lines 185 and 195:  There is no choice possible, so the text 
  "For example" should be replaced with "It must be".

Lines 221 and 278:  There is a problem with the text not 
  completely matching figure 2-1 which makes it a bit difficult 
  to understand what is meant.  In particular, the figure doesn't
  have a label on the "Container".  In actual fact, the light 
  and dark gray shaded boxes are the Containers -- they should 
  be labeled in the figure.

Lines 267-269: In the example, Context-Type does not have its 
  attributes version & charset specified.  The text of section 
  2.3.3 says they MUST be present (of course, the default could 
  be assumed, but 2.3.3 say nothing of a default).

Lines 283-284: The Payload Container can carry more than one 
  document by having appropriate references in the Manifest.  It 
  would be useful if something to this effect were added to this 
  section, probably in this paragraph.  Suggested text: "The 
  Payload Container may contain more than one document and the 
  Message Manifest provides references which allow documents 
  to be distinguished."

Line 297:  The text "This is the implementor's decision" implies 
  it is entirely up to the implementor as to whether (s)he wants 
  to carry multiple documents and how it is done.  This isn't quite 
  the case as the Document Reference, section 3.2.1, is the 
  standardized method for distinguishing multiple documents.  A 
  statement to this effect and reference to 3.2.1 should be added.
  It might, also, be nice to add another example in 3.2.1 illustrating 
  the case for multiple documents in the same payload container.

Line 326: It is not clear what this means.  Explanation should be 
  added.

Lines 403-416 (section 3.3.1): I thought we had agreed that PartyID 
  would be a URI.  This section should be updated accordingly.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC