Project

Profile

Help

Support #5652

open

Questions about Xlink Schema

Added by Ben Weaver 4 months ago. Updated 3 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2022-08-17
Due date:
% Done:

0%

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

Description

We recently encountered an issue stemming from the way Saxon uses the built-in XLink schema. It appears the standard schema resolver forces Saxon's own version of xlink.xsd which means we can't add customization or restrictions to XLink without adding our own schema resolver (see Issue 3091).

1/ Could you help us understand the reasoning behind this change? It is confusing that it seems to apply only to the XLink schema.

2/ It would be helpful to have this behaviour documented somewhere. The "References to W3C DTDs" page is very clear and seemed relevant, but wasn't.

Additionally, the Saxon version of xlink.xsd references xml.xsd, which is not provided at all. This causes, in some cases, an attempt to retrieve xml.xsd from w3.org. It was here we encountered the problem, as the machine running the code was unable to connect to w3.org.

3/ Can Saxon supply the version of xml.xsd that is meant to be included by the Saxon version of xlink.xsd?

Would a catalog file enable us to supply our own cached version of xml.xsd to the xlink.xsd include?


Files

Please register to edit this issue

Also available in: Atom PDF