Restricting the behaviour of an imported complexType

[steve_marjoribanks]

I want to import a complex type into my schema which contains a complex
type which includes a choice as shown below:

<choice minOccurs="2" maxOccurs="unbounded">
<element ref="gmlos"/>
<element ref="gmlointProperty"/>
<element ref="gmlointRep">
</choice>

Howver, in my schema I only want to allow the "gmlos" element to
occur, not the others. Is it possible to restrict the allowable
instances of the imported complexType within my schema? I know I could
just reference the gmlos element directly but I was wondering if it
is possible to import the complex type and then restrict the values?

Thanks

Steve

 

[Martin Honnen]

I want to import a complex type into my schema which contains a complex
type which includes a choice as shown below:

<choice minOccurs="2" maxOccurs="unbounded">
<element ref="gmlos"/>
<element ref="gmlointProperty"/>
<element ref="gmlointRep">
</choice>

Howver, in my schema I only want to allow the "gmlos" element to
occur, not the others. Is it possible to restrict the allowable
instances of the imported complexType within my schema? I know I could
just reference the gmlos element directly but I was wondering if it
is possible to import the complex type and then restrict the values?

Generally you can extend and restrict existing types, see
<http://www.w3.org/TR/xmlschema-0/#DerivByRestrict>

 

[steve_marjoribanks]

I've tried that but it doesn't seem to like it. I created my complex
type and derived it from an existing type. When I had my type exaclt
the same as the existing type it validated fine and when I tried
changing the maxOccurs attribute of elements in my complex type which
were derived from the existing type that was fine too.

However, whenever I tried to remove elements from my type or setting
maxOccurs and minOccurs to 0 it doesn't like it.

In the W3C recommendation it says this should be ok though?!

Ah well, I just referenced gmlos directly in the end. Thanks anyhow!

 

[Henry S. Thompson]

I've tried that but it doesn't seem to like it. I created my complex
type and derived it from an existing type. When I had my type exaclt
the same as the existing type it validated fine and when I tried
changing the maxOccurs attribute of elements in my complex type which
were derived from the existing type that was fine too.

However, whenever I tried to remove elements from my type or setting
maxOccurs and minOccurs to 0 it doesn't like it.

In the W3C recommendation it says this should be ok though?!

Indeed it is OK -- what schema processor are you using, and what error
message are you getting, for what schema document?

ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: (e-mail address removed)
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]

 

[steve_marjoribanks]

I am using XMLSpy2006 Home edition. I think it is probably a bug in the
software to be honest, I have been informed of a coupld of other bugs
in the system. Unfortunately I can't show you the schema I was using as
it doesn't exist in that form anymore! It was identical to the schema
at http://www.dur.ac.uk/s.j.marjoribanks/geotechml/interpreted.xsd
except that the last complex type, instead of referencing <gmlos>
directly declared an element of type gml:LineStringType and then
restricted the allowed elements within it to only the <gmlos>
element. The gmlos and gml:LineStringType are in the
geometrybasic0d1d as imported at the top of the schema.

However, it's not really an issue now as I am not using that method
anymore, but thanks for enquiring!

Steve