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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] XML Schema: restricted <xs:any>?

[ Lists Home | Date Index | Thread Index ]


On Sunday, May 4, 2003, at 07:41 US/Central, Henry S. Thompson wrote:

> Scott Lamb <slamb@slamb.org> writes:
>> Right. I know how to set up the sequence and stuff. What I don't know
>> how to do is how to do that for arbitrary elements in other
>> namespaces. <xs:element> seems to want me tied down to a specific
>> element name. <xs:any> doesn't seem to support any of the type stuff.
>
> True, but <xs:any> can go anywhere <xs:element> can go in a content
> model, so if I've understood you correctly, just replace
>
>   <xs:element ref="other"/>
>
> in your example wiht
>
>   <xs:any namespace="##other"/>
>
> and you'll have what you want.

The definition there should be the same as the outermost one. I.e., I 
want _all_ arbitrary elements in there to have the restrictions I've 
laid out. If I put in any <xs:any namespace="##other"/>, I lose control 
over the placement of xfp elements within it. So I want to make an 
element that I can refer to that is sort of like <xs:any> and sort of 
like <xs:element>. The more I look at the spec, the more I think what I 
want just doesn't exist...

Thanks,
Scott





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS