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

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-policy message

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


Subject: [DISCUSSION] Intent Qualifier XSD does not provide extensibility



Folks,

While investigating the question of second level qualifiers I notice that the XSD for intent qualifiers does not
provide for any extensibility.

The intent complex type has the usual <any/> as part of its definition:

        <complexType name="Intent">
                <sequence>
                        <element name="description" type="string" minOccurs="0"
                           maxOccurs="1" />
                        <element name="qualifier" type="sca:IntentQualifier"
                           minOccurs="0" maxOccurs="unbounded" />
                        <any namespace="##other" processContents="lax"
                           minOccurs="0" maxOccurs="unbounded"/>
                </sequence>
                <attribute name="name" type="NCName" use="required"/>
                <attribute name="constrains" type="sca:listOfQNames"
                   use="optional"/>
                <attribute name="requires" type="sca:listOfQNames"
                   use="optional"/>
                <attribute name="excludes" type="sca:listOfQNames"
                   use="optional"/>
                <attribute name="mutuallyExclusive" type="boolean"
                   use="optional" default="false"/>
                <attribute name="intentType"
                        type="sca:InteractionOrImplementation"
                        use="optional" default="interaction"/>
                <anyAttribute namespace="##other" processContents="lax"/>
        </complexType>

...by contrast, the IntentQualifier type has no such extension point:

        <complexType name="IntentQualifier">
                <sequence>
                        <element name="description" type="string" minOccurs="0"
                           maxOccurs="1" />
                </sequence>
                  <attribute name="name" type="NCName" use="required"/>
                  <attribute name="default" type="boolean" use="optional"
                     default="false"/>
        </complexType>

...was this lack of extensibility intended or is it simply an oversight?

A simple change is to add

                        <any namespace="##other" processContents="lax"
                           minOccurs="0" maxOccurs="unbounded"/>

at the end of the sequence in the IntentQualifier definition.


Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU








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