Bug #4973
closed
Schema for XML namespace is being fetched using HTTP rather than using the local copy
100%
Description
Saxon has built-in knowledge of the schema for the XML namespace http://www.w3.org/XML/1998/namespace, but if a schemaLocation is given in an xs:import for this namespace, the schema is fetched from the W3C web site before it is recognised as being already known. The retrieval from W3C is extremely slow because access is deliberately throttled to reduce load on W3Cs servers.
Note there's a question-mark over what we should do if a non-standard schemaLocation is provided for this namespace: should we use our local copy, or should we go to the given location (which might have different definitions). In general, if a user tries to supply a non-standard schema for the XML namespace, the consequences are unpredictable, so we should probably use our own copy regardless.
Updated by Michael Kay about 3 years ago
I have fixed this on the 11.x branch (but not regression tested) by moving the code that deals with the XML space to earlier in the xs:import processing.
Updated by Norm Tovey-Walsh about 3 years ago
Given that schema locations are explicitly hints, I think we'd be justified in doing that. It sure would be nice to give the user some sort of message about it though.
Updated by Michael Kay over 2 years ago
- Category set to Schema-Aware processing
- Status changed from New to Resolved
- Applies to branch 10, trunk added
- Fix Committed on Branch trunk added
Decided to close this with no further action (i.e. no change on the 10.x branch).
Updated by O'Neil Delpratt over 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 10.6 added
Bug fix applied in the Saxon 10.6 maintenance release
Please register to edit this issue
.