OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wsrm] comments on ws-r 1.05


comments on the ws-r schema at: 

The schema defines two base types, HeaderBaseType and ExtensibleType, 
which allow for
attribute and element wildcards. For simplicity, I'll simply list the 
ExtensibleType definition:

        <xsd:complexType name="ExtensibleType">
                        <xsd:any namespace="##other" processContents="lax" 
minOccurs="0" maxOccurs="unbounded"/>
                <xsd:anyAttribute namespace="##other" 

And then these types are derived by extension, as in the case of 

        <xsd:complexType name="RequestType">
                        <xsd:extension base="wsrm:HeaderBaseType">
                                        <xsd:element name="MessageId" 
                                        <xsd:element name="ExpiryTime" 
                                        <xsd:element name="ReplyPattern" 
                                        <xsd:element name="AckRequested" 
type="wsrm:EmptyType" minOccurs="0"/>
name="DuplicateElimination" type="wsrm:EmptyType" minOccurs="0"/>
                                        <xsd:element name="MessageOrder" 
type="wsrm:EmptyType" minOccurs="0"/>

In the spec, the graphic in figure 6 suggests that the element wildcard 
content follows the wsrm:MessageOrder element
when in fact, it actually precedes the MessageId element according to XML 
Schema which only supports extension via appending.
The note in section of XML Schema Part 1 reads:

        NOTE: This specification allows only appending, and not other 
kinds of extensions. This decision simplifies application processing 
required to             cast instances from derived to base type. Future 
versions may allow more kinds of extension, requiring more complex 
transformations to effect 

Either the spec or the schema should be modified to correct this 
inconsistency. Also, I am puzzled as to why the formal prose and tabular
definitions of the elements for this spec do not identify those elements 
which are extensible via element and/or attributes.


Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
blog: http://webpages.charter.net/chrisfer/blog.html
phone: +1 508 377 9295

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]