[ebxml-cppa] Should a SimplePart be reusable?

[Arvola Chan <arvola@tibco.com>]

Currently, SimplePart is a sub-element of Packaging. That suggests a
SimplePart cannot be reused across multiple Packaging elements.

Consider the following Packaging definition:

 <tp:Packaging tp:id="package1">
  <tp:ProcessingCapabilities tp:parse="true" tp:generate="true"/>
  <tp:SimplePart tp:id="part11" tp:mimetype="text/xml">
   <tp:NamespaceSupported
tp:location="http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg
-header-01.xsd"
tp:version="1.1">http://www.oasis-open.org/committees/ebxml-msg/schema/draft
-msg-header-01.xsd</tp:NamespaceSupported>
  </tp:SimplePart>
  <tp:SimplePart tp:id="part12" tp:mimetype="text/xml">
   <tp:NamespaceSupported
tp:location="http://www.rosettanet.org/schemas/PIP3A4RequestPurchaseOrder.xs
d"
tp:version="1.0">http://www.rosettanet.org/schemas/PIP3A4RequestPurchaseOrde
r.xsd</tp:NamespaceSupported>
  </tp:SimplePart>
  <tp:CompositeList>
   <tp:Composite tp:id="part1" tp:mimetype="multipart/related"
tp:mimeparameters="type=text/xml;">
    <tp:Constituent tp:idref="part11"/>
    <tp:Constituent tp:idref="part12"/>
   </tp:Composite>
  </tp:CompositeList>
 </tp:Packaging>

The SimplePart part11 describes the SOAP:Envelope portion of an ebXML
message. If this is not reusable, then for every Packaging element, a
similar SimplePart with a different ID value will have to be redeclared. Is
that desirable? If not, should we consider moving SimplePart to the same
level as Packaging.

Thanks,
-Arvola