Your example is still well-formed and can still be processed as such. It may
not be schema valid, but, hey, content models need to evolve, too! And RELAX
NG names-classes, as you probably already know, can help you deal with such
cases. See
http://www.oasis-open.org/committees/relax-ng/tutorial-20011203.html#IDAFLZR
.

Eric van der Vlist wrote:
> That's not that easy and there is nothing in the specs which helps to
> create the discipline required in the applications to make it smooth.
> 
> Let's take a simple example... I have a text only element:
> 
> <ns1:foo>This is a simple example.</ns1:foo>
> 
> If I extend this example to include a semantic element to identify
> "simple" as an adjective:

> <ns1:foo>This is a <ns2:adj>simple</ns2:adj> example.</ns1:foo>
> 
> I am changing a text leaf node into a mixed content including 2 text
> nodes separated by a child element and this will likely break 90+% of
> the existing applications.


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>