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


Help: OASIS Mailing Lists Help | MarkMail Help

obix message

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

Subject: Schema and spec issue related to "xs:any"

Note the use of "any" in Obj in the sequence. This is not reflected in the UML. This item is corrected in the proposed UML diagrams that were sent 21 October 5:20pm ET - pending resolution of the int/integer/long inconsistencies between the spec and schema.

This was sent off list before; making sure it's on the TC list.

schema wd36:
    <xs:complexType name="Obj">
            <xs:element ref="obj" minOccurs="0" maxOccurs="unbounded"/>
            <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        <xs:attribute ref="display"/>
        <xs:attribute ref="displayName"/>
        <xs:attribute ref="href"/>
        <xs:attribute ref="icon"/>
        <xs:attribute ref="is"/>
        <xs:attribute ref="name"/>
        <xs:attribute ref="null"/>
        <xs:attribute ref="status" default="ok"/>
        <xs:attribute ref="ts"/>
        <xs:attribute ref="writable" default="false"/>

The recursion is deliberate; should the use of xs:any be mentioned in the text? The three diagrams each address this issue, so Craig can take the one with the integer/int/long decision we take pursuant to the 21 October 520pm ET email.



William Cox 

Email: wtcox@CoxSoftwareArchitects.com 

Web: http://www.CoxSoftwareArchitects.com 

+1 862 485 3696 mobile

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