Xerces bug: Wrong value of xml:base attribute after resolving XInclude references
The following Xerces bug is affecting several users: https://issues.apache.org/jira/browse/XERCESJ-1102
This bug causes the wrong value of xml:base attribute after resolving XInclude references. One user applies a the patch in a jar file that is included on the Java classpath when Saxon is invoked. It would be good to apply this patch internally with Saxon as part of the issued product.
This affects: Saxon-J, Saxon.NET and Saxon/C
Updated by Michael Kay about 2 years ago
Apart from fixing this bug, I think there are a number of other changes that could be useful in terms of improving the integration between Xerces and Saxon. For example, we could consider defining a "SAX3" interface that resolves some of the long-standing issues in namespace handling and that removes the current duplication whereby both Xerces and Saxon maintain full capability for resolving QNames, without directly sharing the means of doing so.
Several Saxon users (Oxygen and DeltaXML to my knowledge) are understood to ship their own Xerces variants, which suggests that it might be possible to establish a community to take such a project forward, either on the main Apache development branch for Xerces or as a community fork.
Please register to edit this issue