[ebxml-cppa] cpa-example.xml and NamespaceSupported element

[Arvola Chan <arvola@tibco.com>]

Hima:

In your recent example (cpa-example.xml), you have:

  <SimplePart id="N40" mimetype="text/xml">
  <NamespaceSupported
location="http://ebxml.org/project_teams/transport/messageService.xsd"
version="1.0">http://www.ebxml.org/namespaces/messageService</NamespaceSuppo
rted>
  <NamespaceSupported
location="http://ebxml.org/project_teams/transport/xmldsig-core-schema.xsd"
version="1.0">http://www.w3.org/2000/09/xmldsig</NamespaceSupported>
  </SimplePart>

Presumably, this is describing the namespaces supported in the ebXML message
SOAP envelope. In draft-msg-header-00.xsd, I have

 <import namespace="http://www.w3.org/2000/09/xmldsig#"
schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/xmldsi
g-core-schema.xsd"/>
 <import namespace="http://www.w3.org/1999/xlink"
schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/xlink.
xsd"/>
 <import namespace="http://schemas.xmlsoap.org/soap/envelope/"
schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/envelo
pe.xsd"/>
 <import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/xml_la
ng.xsd"/>

To be complete, shouldn't the Packaging element describing the ebXML message
SOAP envelope include NamespaceSupported elements for each of the following
namespaces:

http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-00.xs
d
http://www.w3.org/2000/09/xmldsig#
http://www.w3.org/1999/xlink
http://schemas.xmlsoap.org/soap/envelope/
http://www.w3.org/XML/1998/namespace

Alternatively, would it be sufficient just to list the namespace
http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-00.xs
d, since it imports all of the other identified namespaces?

Regards,
-Arvola