RE: restricting anySimpleType in complexType definition

In case I implied otherwise, there was a discussion in March about whether
xs:anySimpleType was legal. It appears to be:

	http://lists.w3.org/Archives/Public/xmlschema-dev/2002Mar/0087.html 

Mark



Mark Feblowitz                                   	
XML Architect
       [t]   617.715.7231                                     	
       [f]   617.495.0188
Frictionless Commerce Incorporated 	
       [e]  mfeblowitz@frictionless.com
       [w] http://www.frictionless.com
       [m] 400 Technology Square, 9th Floor
             Cambridge, MA 02139 
Open Applications Group Incorporated
       [e]  mfeblowitz@openapplications.org
       [w] http://www.openapplications.org 

 -----Original Message-----
From: 	Calvin Smith [mailto:calvins@SIMS.Berkeley.EDU] 
Sent:	Monday, June 17, 2002 3:23 PM
To:	xmlschema-dev@w3.org
Subject:	restricting anySimpleType in complexType definition


greetings,

I have a question about restricting anySimpleType.  I wanted to define a
type based on xsd:token that would allow for a few possible values for the
element content and an optional attribute.  After much difficulty, I
finally got the following to validate fine, and it appears to be what I
wanted, but I am not sure if this is legal or just not caught by my
validator (XML Spy 4.4).  The base below is anySimpleType, which I thought
shouldn't work, since it is not a complex type.  Is what I have below
legal, and is there a better way to define a type with an element with
enumerated values and an attribute?


<xsd:complexType name="ExampleType">
  <xsd:simpleContent>
    <xsd:restriction base="xsd:anySimpleType">
      <xsd:enumeration value="a possible value"/>
      <xsd:enumeration value="another possible value"/>
      <xsd:attribute name="anAttribute" type="xsd:token"/>
    </xsd:restriction>
  </xsd:simpleContent>
</xsd:complexType>

thanks,

calvin

Received on Monday, 17 June 2002 16:03:58 UTC