Re: Both extending and restricting with <redefine>

In theory, would the same desing pattern also apply when attempting to 
replace an element in a complexType? 

The underlying issue is that there is no mechanism available in the 
current XML Schema specification that would allow a designer to 
replace/rename an element (global or local) in a specific content model 
only. Right?

Kind regards,
Eric

>None-the-less I think it's the only correct way.
>
>Is redefining things really the logically correct way to think about
>the underlying requirement?
>
>ht
>  
>