> Or take the "guard" labelling approach - and allow overriding / replacing
>- so the second occurence inside an include can be noted to replace the
>existing definition...
At present, we can always safely swap two define or include statements
safely. This helps when we have to read large schemas and revise them.
So, I do not want to introduce such overriding.
Also note that we already have another mechanism for overriding:
childr definitions of include statements override those definitions
in the included schemas.
Cheers,
--
MURATA Makoto (FAMILY Given) <>
