[
Lists Home |
Date Index |
Thread Index
]
- From: ht@cogsci.ed.ac.uk (Henry S. Thompson)
- To: Eckenberger Axel <Extern.Eckenberger@kmweg.de>
- Date: Tue, 05 Sep 2000 08:10:58 +0100
Eckenberger Axel <Extern.Eckenberger@kmweg.de> writes:
> Hi folks,
>
>
>
> is it possible to check for the existence of an unknown node during validation
> using schemas ???
>
>
>
> e.g.
>
> <SomeDoc> <!-- valid -->
> <Name>Test</Name>
> <XMLFragment>
> <P>Some arbitrary XML fragments go here</P>
> </XMLFragment>
> </SomeDoc>
>
> <SomeDoc> <!-- valid -->
> <Name>Test</Name>
> <XMLFragment>
> <DIV>Some arbitrary XML fragments go here</DIV>
> </XMLFragment>
> </SomeDoc>
>
> <SomeDoc> <!-- not valid -->
> <Name>Test</Name>
> <XMLFragment>
> </XMLFragment>
> </SomeDoc>
>
> <SomeDoc> <!-- not valid -->
> <Name>Test</Name>
> <XMLFragment>
> <P>Some arbitrary XML fragments go here</P>
> <P>Some arbitrary XML fragments go here</P>
> </XMLFragment>
> </SomeDoc>
>
>
> SomeDoc, Name and HTMLFragment are part of the schema, but the
> content of HTMLFragment has to be exactly one XML Element, although
> it does not matter what it is.
Sure -- use <any> [1] , it takes occurence indicators like any other
content model particle:
<xs:element name="XMLFragment">
<xs:complexType>
<xs:sequence>
<xs:any/>
</xs:sequence>
</xs:complexType>
</xs:element>
This requires exactly one element as the content of XMLFragment, but
puts no constraints on its name, content, attributes or namespace. <any>
offers options to constrain the namespace, see the PWD.
ht
[1] http://www.w3.org/TR/xmlschema-1/#Wildcard
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
|