Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Restricting the behaviour of an imported complexType

From: ht@---.--.--.-- (----- -. --------)
To: NULL
Date: 3/6/2006 5:22:00 AM
steve_marjoribanks writes:

> 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: ht@i...
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent