Project

Profile

Help

Bug #4973

Schema for XML namespace is being fetched using HTTP rather than using the local copy

Added by Michael Kay 26 days ago. Updated 26 days ago.

Status:
New
Priority:
Low
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
2021-04-20
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:

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.

History

#1 Updated by Michael Kay 26 days 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.

#2 Updated by Norm Tovey-Walsh 26 days 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.

Please register to edit this issue

Also available in: Atom PDF