[Home] [By Thread] [By Date] [Recent Entries]


Oops. This was in response to Jeff Lowery's clarification of the dual
nature of anyType in the following, and why an instance of myElem can
only have empty content.

> <element name="myElem">
>       <complexType>
>               <complexContent>
>                       <restriction base="anyType"/>
>               </complexContent>
>       </complexType>
> </element>

Sorry about the confusion.

-- Ron

Ronald Bourret wrote:
> 
> OK. Now that I finally understand why this is invalid, what is the point
> of allowing an xsd:restriction element with no children? Is it
> specifically to allow me to restrict content down to emptiness and yet
> still get the OO advantages (?) of using a restriction?

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member