Re: [wsrm] adding extensibility to the empy type

[Sunil Kunisetty <sunil.kunisetty@oracle.com>]

 <snip>

>
>
> Less importantly and more generally (about the schema as a whole and a long
> standing question I have forgotten to ask), this model puts all extension
> content (new elements) at the beginning of the WSRM elements.  This is
> counter-intuitive though I realise it comes from the use of schema type
> extensions rather than consistent placement of xsd:any at the end of every

 Right.. So either we can redefine the extension tags for every
 extensible  RM element or just define them in a base type and inherit thus implying
 extensions at the top... To my recollect, most WS schemas (WSDL for ex.)  do the latter.
 I was also told that many schema valuators do 'relax' on this particular restriction, i.e,
 they allow the elements to appear any where.  Let me check what XMLSpy does.


>
> "interesting" complex type.  For example, an extended MessageHeader would
> (today) appear as:
>
>    <wsrm:MessageHeader soap:mustUnderstand="1">
>      <foo:bar letsGoToTheBar="yeah" />
>      <wsrm:MessageId ... />
>      <wsrm:ExpiryTime ... />
>      <wsrm:ReplyPattern ... />
>    </wsrm:MessageHeader>
>
> rather than something that appears extended:
>
>    <wsrm:MessageHeader soap:mustUnderstand="1">
>      <wsrm:MessageId ... />
>      <wsrm:ExpiryTime ... />
>      <wsrm:ReplyPattern ... />
>      <foo:bar letsGoToTheBar="yeah" />
>    </wsrm:MessageHeader>
>
> Should we change our choice here?
>
> This also reminds me of another schema nit: Why is the existing extensible
> type (the one with the required soap:mustUnderstand) named wsrm:RmBaseType,

 Does it really matter as it is not exposed to the User?

>
> I thought we nuked all of the "Rm" prefixes?  I purposefully chose
> HeaderType above to work around this complaint.
>
> thanx,
>         doug
>
> On 20-Feb-04 12:09, 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.
>
> 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.