![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >comp.text.xml Archive Home >Recent entries >Thread Prev - Re: Restricting the behaviour of an imported complexType >Thread Next - Re: Restricting the behaviour of an imported complexType Re: Restricting the behaviour of an imported complexTypeTo: 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]
| ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
