Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - Re: Substitution groups - replacing required elements in the s.group head [Thread Next] Re: Extension and all-groupTo: <xmlschema-dev@--.---> Date: 8/4/2004 5:18:00 PM > Hello! > > This question was raised at news:microsoft.public.dotnet.xml newsgroup > - > > is the following schema valid? .NET gives errors, while XMLSpy">XMLSpy and > W3C validator say okay. The schema is not valid. The derived type violates the requirement that the only place an 'all' group can appear is all alone as the only group in a type. XSV should check for this, but doesn't [1]: "<all> groups are [not] properly constrained as to how they appear in schemas" I understand how this results from the definitions, but IMHO there is a problem here. Consider a case in which object A inherits from object B and both have attributes that should be serialized. When building the matching schema, it's either forgetting about the inheritance or using a 'sequence' and not 'all' in the definition of both the base type and the extending type. The latter however has the poor outcome of forcing order on the object's attributes. Am I missing something here? | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
