Re: Options for change

["Eve L. Maler" <eve.maler@sun.com>]

At 12:06 PM 10/2/01 -0700, Hallam-Baker, Phillip wrote:
>Existing
>
><complexType name="AttributeValueType">
>         <sequence>
>                 <any namespace="##any" processContents="lax" minOccurs="0"
>maxOccurs="unbounded"/>
>         </sequence>
></complexType>
>
>The problem with this set up is that every application requires an extension
>schema to use an attribute statement.

(Strictly not really true; they could supply no schema for that stuff, and 
it won't be invalid because of the "lax" instruction...it just won't be 
maximally useful.)

>With Generic Data Slots:
>
>
><complexType name="AttributeValueType">
>         <sequence>

Do you mean <choice> here?  Having these all in order doesn't seem right.

>         <any namespace="##any" processContents="lax" minOccurs="0"
>maxOccurs="unbounded"/>
>                 <element ref="saml:BooleanData" minOccurs=0
>maxOccurs="unbounded"/>
>                 <element ref="saml:IntegerData" minOccurs=0
>maxOccurs="unbounded"/>
>                 <element ref="saml:BooleanData" minOccurs=0

(StringData, I assume)

>maxOccurs="unbounded"/>
>         </sequence>
></complexType>
><element name="BooleanData" type="boolean"/>
><element name="IntegerData" type="integer"/>
><element name="StringData" type="string"/>
>
>
>Using generic slots the namespace can specify the use of the slot, for
>example:
>
><AttributeValue Namespace="urn:whatever:academic-agreement-2001"
>         Name="MemberOfFaculty">
>    <StringData>MIT.EDU</StringData>
></AttributeValue>
>
><AttributeValue Namespace="urn:whatever:academic-agreement-2001"
>         Name="IsA Student">
>    <BooleanData>true</BooleanData>
></AttributeValue>
>
>
>This leave the problem that the attribute slot is intended to be extensible
>but an extension schema can't declare an extension that is only for use as
>an attribute value.
>
>With generic data slots and an extension point:
>
>
><complexType name="AttributeValueType">
>         <sequence>
>                 <any namespace="##any" processContents="lax" minOccurs="0"
>maxOccurs="unbounded"/>
>                 <element ref="saml:AttributeElement"/>
>                 <element ref="saml:BooleanData" minOccurs=0
>maxOccurs="unbounded"/>
>                 <element ref="saml:IntegerData" minOccurs=0
>maxOccurs="unbounded"/>
>                 <element ref="saml:BooleanData" minOccurs=0
>maxOccurs="unbounded"/>
>         </sequence>
></complexType>
><element name="AttributeElement" type="saml:AttributeElementType"/>
><complexType name="AttributeElementType"/>

If you do this, then there's no reason to have the ##any wildcard, is 
there?  We should pick one of the two ways, I think...

         Eve
--
Eve Maler                                    +1 781 442 3190
Sun Microsystems XML Technology Center   eve.maler @ sun.com