You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The intent of sch:pattern/@document is that it allows a pattern to validate an XML resource retrieved by constructing a URL with information from the primary document.
So this allows a hub or TOC document with links to other documents. Such in a ZIP archive. XML is a web technology, therefore it is good to support at least a minimal support for documents in a web.
For Schematron 2016, there was only one level of indirection allowed*; consequently there can be no problem with transitive closure issues such as loops and self-referencing documents.
Problem
If no XML resource can be retrieved from a URL in sch:pattern/@document what is the result of validation?
Proposed Solution
Schematron description enhanced: If a resource cannot be retrieved for a URL in sch:pattern/@document then it is implementation-defined whether validation of other patterns continues.
SVRL elements augmented to allow elements that flag that there was an error retrieving (or parsing/converting) an external resource.
Where the contents of svrl:resource-error are an implementation-defined message useful for the human in the context. It could, for example, be the MIME header for the error response. (Even some simple message like "Unable to retrieve external document XXXX.XXXX" would be better than nothing.)
The svrl:conversion-error element is the subject of a separate enhancement proposal. See #48 for details.
In theory, we could validate a fixed chain length of documents, reading one document into a top-level variable, then using that to for the URL for another document in another variable, and so on. Then using information in the variables to construct the URLs for sch:pattern/@documents. But with XPath 3 we get Xpath functions (I think), allowing an unbounded traversal of links.
The text was updated successfully, but these errors were encountered:
Background
The intent of
sch:pattern/@document
is that it allows a pattern to validate an XML resource retrieved by constructing a URL with information from the primary document.So this allows a hub or TOC document with links to other documents. Such in a ZIP archive. XML is a web technology, therefore it is good to support at least a minimal support for documents in a web.
For Schematron 2016, there was only one level of indirection allowed*; consequently there can be no problem with transitive closure issues such as loops and self-referencing documents.
Problem
If no XML resource can be retrieved from a URL in
sch:pattern/@document
what is the result of validation?Proposed Solution
Schematron description enhanced: If a resource cannot be retrieved for a URL in
sch:pattern/@document
then it is implementation-defined whether validation of other patterns continues.SVRL elements augmented to allow elements that flag that there was an error retrieving (or parsing/converting) an external resource.
Where the contents of
svrl:resource-error
are an implementation-defined message useful for the human in the context. It could, for example, be the MIME header for the error response. (Even some simple message like "Unable to retrieve external document XXXX.XXXX" would be better than nothing.)The
svrl:conversion-error
element is the subject of a separate enhancement proposal. See #48 for details.sch:pattern/@documents
. But with XPath 3 we get Xpath functions (I think), allowing an unbounded traversal of links.The text was updated successfully, but these errors were encountered: