Re: DTD, XSD and sample XML header docs

["Nikola Stojanovic" <nhomest1@twcny.rr.com>]

<Scott>
Scott: I agree on the top ebXMLHeader tag and MessageManifest outside the
MessageHeader.
I might suggest <Manifest> and <Header> but I'm not picky on this.
</Scott>

Kind of agree on both. Also, I think that we should (at least try to) decide
on naming convention. One issue might be as you have it above
MessageManifest vs. Manifest. Or, do we imply context of parent elements or
not. Should we have:

<Message>
  <MessageManifest>
  </MessageManifest>
</Message>

or

<Message>
  <Manifest>
  </Manifest>
</Message>

<Scott>
Top tage would eventually facilitate a top control point for versioning
(once we figure out the
approach on this!), etc. I think we should end up with all sanctioned
ebXML tags being namespaced.
</Scott>

This ("ebXML tags being namespaced") might be related to another issue as
well => How do we specify Header Levels (tags) that are needed for some
levels, but not for others.

Nikola




=======================================================================
= This is ebxml-transport, the general mailing list for the ebXML     =
= Transport project team. The owner of this list is                   =
= owner-ebxml-transport@oasis-open.org                                =
=                                                                     =
= To unsubscribe, send mail to majordomo@lists.oasis-open.org with    =
= the following in the body of the message:                           =
=      unsubscribe ebxml-transport                                    =
= If you are subscribed using a different email address, put the      =
= address you subscribed with at the end of the line; e.g.            =
=      unsubscribe ebxml-transport myname@company.com                 =
=======================================================================