Adding extensibility tags for EmptyType will be wrong as it will result
in pretty much every RM element to be extensible. Do we really want
this? As per my recollection, we decided to have our Header elements
only to be extensible.
My suggestion would be to have 2 base extensible elements:
<xsd:complexType name="BaseType">
- <xsd:sequence>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
<xsd:anyAttribute namespace="##other" processContents="lax" />
</xsd:complexType>
<xsd:complexType name="BaseHeaderType">
<xsd:sequence>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
<xsd:attribute ref="soap:mustUnderstand" use="required" fixed="1" />
<xsd:anyAttribute namespace="##other" processContents="lax" />
</xsd:complexType>
(note: to reduce the verbosity we can redefine BaseHeaderType as an
extension of BaseType and add soap:mustUnderstand Header).
Header elements will be based on BaseHeaderType. Other 'extensible'
elements such as Fault can be based on BaseType. Other non extensible
elements will extend from EmptyType.
-Sunil
Tom Rutt wrote:
> Would the following change to the empy type provide better extensibility
> for the protocol?
>
> <xsd:complexType name="EmptyType">
> <xsd:sequence>
> <xsd:any namespace="##other" processContents="lax"
> minOccurs="0" maxOccurs="unbounded"/>
> </xsd:sequence>
> <xsd:anyAttribute namespace="##other" processContents="lax"/>
> </xsd:complexType>
>
> The above prosal adds extensible attributes and elements , without the
> soap must understand attribute which is there for header elements.
>
> --
> ----------------------------------------------------
> Tom Rutt email: ;
> Tel: +1 732 801 5744 Fax: +1 732 774 5133
>
> To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.
