Re: ebXML PoC -- feedback to working groups

[Scott Hinkelman/Austin/IBM <srh@us.ibm.com>]

Comments:
- On the other email concerning optionality: True optionality can reduce
interoperability. But beware that
if it is *truely* optional (not just per DTD rules) and then made
mandatory, garbage may have to be loaded
to satisfy.....
- Section 7.2.2 Content Length
The explanation is good on the definition of the length, but we either
should drop the one-line example
following it or actually put in an example where a small length can be
easily understood.
- I generally think we need another pass through the header DTD. I would
suggest that we align less to
a structure of human-readability and more to a flat structure without
artificial containment (remove
TPAInfo, MessageData tags for example and put the subtags directly under
Header). Fundamentally,
I favor for purposes of infrastructure the XML camp thinking of *data* not
*documents* (documents here
indicating considerations leaning toward human readability).
- Make Manifest optional. I'm not in favor of required-empty-tags.

Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074