![]() |
![]() | ![]() | ![]() | 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/2/2006 8:05:00 AM 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 gml:pos directly in the end. Thanks anyhow! | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
