[
Lists Home |
Date Index |
Thread Index
]
Trouble is, it's not Microosft's XInlude implementation but the people
implementing it on top of our APIs. Implementers may have the user option,
but unless we give them the switch they effectively have no option.
Anyway, IIRC the decisions on how to mitigate the incompatibility were made
long before the errata were issued. But I'm glad to see that the basic
problem has been addressed!
>
>XInclude processors may "at user option" drop the addition of the xml:base
>and xml:lang
>fixup which is the problem they are seeing. See errata PEX16
> http://www.w3.org/2004/12/xinclude-errata/#PEX16
>It sounds way cleaner to drop the non-conformant XSD user option and
>instead
>add a
>user option for XInclude following this errata.
>
>Daniel
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
|
