Default Query Language Binding
A Schematron schema with no language binding or a queryBinding
attribute with the value xslt, in any mix of upper and lower case letters,
shall use the following binding:
The query language used is the extended version of
specified in .
Consequently, the data model used is the data model of those
specifications.
The rule context is interpreted according to the Production
1 of . The rule context may be elements, attributes,
comments and processing instructions.
The assertion test is interpreted according to
Production 14 of , as returning a Boolean value.
The name query is interpreted according to
Production 14 of , as returning a string value.
Typically, the select attribute contains an expression
returning an element node: the name query takes the local or prefixed name of the
node, not its value.
The value-of query is interpreted according to Production
14 of , as returning a string value.
The let value is interpreted according to Production
14 of , as returning a string value.
The notation for signifying the use of parameter of an abstract pattern is to prefix
the name token with the $ character.
This is a character not found as a delimiter in URLs or XPaths.
The $ character not followed by the name
of an in-scope parameter shall not be
treated as a parameter name delimiter. Such a character may
subsequently be used as a delimiter for a variable name or as
a literal character.
A Schematron let expression is treated
as an variable. The $ delimiter signifies the use
of a variables in an context expression, assertion test, name query, value-of
query or let expression.
The $ character not followed by the name
of an in-scope variable shall be
treated as a literal character.
The key element may be used, in
the namespace, before the pattern elements.
The attributes id, name and prefix should
follow the rules for non-colonized names
for the version of XML used by the document.
Schematron Validation Report Language
Description
The Schematron Validation Report Language (SVRL) is
a simple XML language which may be used for reporting the
results of Schematron validation and for conformance
suites.
The order of elements in an SVRL is implementation-dependent;
different implementations may generate the same elements in
a different order.
All elements shown in the grammar for Simple Validation Report Language
are qualified with the namespace
URI:
http://purl.oclc.org/dsdl/svrl
In subsequent schemas, the prefix svrl is taken as
bound to the Simple Validation Report Language namespace URI for exposition purposes.
The prefix svrl is not reserved or required by
this part of ISO/IEC 19757.
RELAX NG Compact Syntax Schema
default namespace = "http://purl.oclc.org/dsdl/svrl"
schematron-output element schematron-output {
attribute title { text }?,
attribute phase { xsd:NMTOKEN }?,
attribute schemaVersion { text }?,
human-text*,
ns-prefix-in-attribute-values*,
(active-pattern,
(fired-rule, (failed-assert | successful-report)*)+)+
}
# only namespaces from sch:ns need to be reported
ns-prefix-in-attribute-values element ns-prefix-in-attribute-values {
attribute prefix { xsd:NMTOKEN },
attribute uri { text },
empty
}
# only active patterns are reported
active-pattern element active-pattern {
attribute id { xsd:ID }?,
attribute name { text }?,
attribute role { xsd:NMTOKEN }?,
empty
}
# only rules that are fired are reported,
fired-rule =
element fired-rule {
attribute id { xsd:ID }?,
attribute context { text },
attribute role { xsd:NMTOKEN }?,
attribute flag { xsd:NMTOKEN }?,
empty
}
# only references are reported, not the diagnostic
diagnostic-reference element diagnostic-reference {
attribute diagnostic { xsd:NMTOKEN },
human-text
}
# only failed assertions are reported
failed-assert element failed-assert {
attlist.assert-and-report,
diagnostic-reference*,
human-text
}
# only successful asserts are reported
successful-report element successful-report {
attlist.assert-and-report,
diagnostic-reference*,
human-text
}
human-text = element text { text }
attlist.assert-and-report attribute id { xsd:ID }?,
attribute location { text },
attribute test { text },
attribute role { xsd:NMTOKEN }?,
attribute flag { xsd:NMTOKEN }?
start = schematron-output
]]>
Schematron Schema
The corresponding Schematron schema is:
Schema for Schematron Validation Report Language
The Schematron Validation Report Language is a simple language
for implementations to use to compare their conformance. It is
basically a list of all the assertions that fail when validating
a document, in any order, together with other information such
as which rules fire.
This schema can be used to validate SVRL documents, and provides
examples of the use of abstract rules and abstract patterns.
Elements
The element is a child of schematron-output.
The element should not contain any elements.
The element should be empty.
The element is the root element.
may only contain the following elements:
text, ns-prefix-in-attribute-values, active-pattern, fired-rule, failed-assert
and successful-report.
should have at least one active pattern.
should have a diagnostic attribute,
giving the id of the diagnostic.
A comes before an active-pattern or another
ns-prefix-in-attribute-values element.
A comes after an active-pattern, an empty
fired-rule, a failed-assert or a successful report.
The element should have a context attribute
giving the current context, in simple XPath format.
The element should only contain a text element
and diagnostic reference elements.
The element should only contain a text element.
A comes after a fired-rule, a failed-assert or a
successful-report.
An unknown element has been used.
Unique Ids
Id attributes should be unique in a document.
Required Attributes
The element should have a
attribute.
]]>
Design Requirements
Motivating design requirements for the schema language with the default
query language binding include:
Represent abstract patterns such as the head+body pattern.
Support progressive validation.
Include assertions or abstract rules from an external file.
Support a one-to-one mapping between the natural-language
statements and artificial-language statements.
Support the generation and labelling of arcs between information items.
Motivating design requirements for the schema language with the default
query language binding do not include:
Simple specification of constraints that are simply expressed by grammar-based validation,
such as ISO/IEC 19757-2 (RELAX NG) schemas.
Replacement of any other standard schema language for XML.
Single-pass or streamable implementation.
As well, certain outcomes are out-of-scope for this part of ISO/IEC 19757:
Query Language Binding for XPath 2
The xpath2 query language binding allows schemas
implemented using the simplest
A Schematron schema with a queryBinding
attribute with the value xpath2, in any mix of upper and lower case letters,
shall use the following binding:
The query language used is that of
used with no schema and
with backwards compatability mode as false.
Consequently, the data model used is the data model of
contructed from an infoset not a PSVI.
All namespaces, prefixes, functions and operators defined by
shall be available.
No user-written functions or extensions shall be available.
The rule context is interpreted according to the Production
Production 1 of . The rule context may be elements, attributes,
comments and processing instructions, including sequences of these.
The assertion test is interpreted according to
Production 1 of ,
using fn:boolean() on the result of evaluating the expression
and to find the effective boolean value.
The name query is interpreted according to
Production 1 of ,
using fn:node-name() on the result of evaluating the expression
which should be an element or attribute node
and returning a string value.
The value-of query is interpreted according to Production
Production 1 of ,
using fn:string() on the result of evaluating the expression
and returning a string value.
The let element should not be used.
Abstract patterns and parameters should not be used.
The attributes id, name and prefix should
follow the rules for non-colonized names
for the version of XML used by the document.
The fn:error() function or other dynamic errors
should not be used to provide assertion text
or to substitute for assertions and diagnostics.
Query Language Binding for XSLT 2
The xslt2 query language binding allows schemas
implemented using . All implementations
that support the xslt2 query language binding should also support
xpath2 query language binding.
A Schematron schema with a queryBinding
attribute with the value xslt2, in any mix of upper and lower case letters,
shall use the following binding:
The query language used is the extended version of
specified in
with backwards compatability mode as false.
Consequently, the data model used is the data model of
contructed from an infoset or a PSVI.
All namespaces, prefixes, functions and operators defined by
shall be available.
An implementation may allow user-written functions and extensions,
in the appropriate namespace.
The rule context is interpreted according to the Production
Production 1 of . The rule context may be elements, attributes,
comments and processing instructions, including sequences of these.
The assertion test is interpreted according to
Production 1 of ,
using fn:boolean() on the result of evaluating the expression
and to find the effective boolean value.
The name query is interpreted according to
Production 1 of ,
using fn:node-name() on the result of evaluating the expression
which should be an element or attribute node
and returning a string value.
The value-of query is interpreted according to Production
Production 1 of ,
using fn:string() on the result of evaluating the expression
and returning a string value.
The let value is interpreted according to Production
Production 1 of .
The notation for signifying the use of parameter of an abstract pattern is to prefix
the name token with the $ character.
This is a character not found as a delimiter in URLs or XPaths.
The $ character not followed by the name
of an in-scope parameter shall not be
treated as a parameter name delimiter. Such a character may
subsequently be used as a delimiter for a variable name or as
a literal character.
A Schematron let expression is treated
as an variable. The $ delimiter signifies the use
of a variables in an context expression, assertion test, name query, value-of
query or let expression.
The $ character not followed by the name
of an in-scope variable shall be
treated as a literal character.
All namespaces and prefixes defined by for modules are reserved
with their
usage. All functions defined by these modules shall be available in addition to the the functions defined
by .
The key element may be used, in
the namespace, before the pattern elements.
The function element may be used, in
the namespace, before the pattern elements.
The attributes id, name and prefix should
follow the rules for non-colonized names
for the version of XML used by the document.
The fn:error() function or other dynamic errors
should not be used to provide assertion text
or to substitute for assertions and diagnostics.
Query Language Binding for EXSLT
The exslt query language binding is the default xslt binding
augmented by the functions.
A Schematron schema with a queryBinding
attribute with the value exslt, in any mix of upper and lower case letters,
shall use the following binding:
The query language used is the extended version of
specified in .
Consequently, the data model used is the data model of those
specifications.
The rule context is interpreted according to the Production
1 of . The rule context may be elements, attributes,
comments and processing instructions.
The assertion test is interpreted according to
Production 14 of , as returning a Boolean value.
The name query is interpreted according to
Production 14 of , as returning a string value.
Typically, the select attribute contains an expression
returning an element node: the name query takes the local or prefixed name of the
node, not its value.
The value-of query is interpreted according to Production
14 of , as returning a string value.
The let value is interpreted according to Production
14 of , as returning a string value.
The notation for signifying the use of parameter of an abstract pattern is to prefix
the name token with the $ character.
This is a character not found as a delimiter in URLs or XPaths.
The $ character not followed by the name
of an in-scope parameter shall not be
treated as a parameter name delimiter. Such a character may
subsequently be used as a delimiter for a variable name or as
a literal character.
A Schematron let expression is treated
as an variable. The $ delimiter signifies the use
of a variables in an context expression, assertion test, name query, value-of
query or let expression.
The $ character not followed by the name
of an in-scope variable shall be
treated as a literal character.
All namespaces and prefixes defined by for modules are reserved
with their
usage. All functions defined by these modules shall be available in addition to the the functions defined
by Production 14 of and
Production
1 of
As does not require all implementations to provide all
modules, some schemas using this query language binding will fail if they use functions
which the implementation does not provide.
The key element may be used, in
the namespace, before the pattern elements.
The attributes id, name and prefix should
follow the rules for non-colonized names
for the version of XML used by the document.
Query Language Binding for STX
The stx query language binding provides a schema langauge
suited to memory-efficient streaming implementation.
A Schematron schema with a queryBinding
attribute with the value stx, in any mix of upper and lower case letters,
shall use the following binding:
The query language used is the streaming dialect of
specified in .
Consequently, the data model used is the data model of
which is a variant on noting that
all elements and attributes are treated as untyped in .
The rule context is interpreted according to the Production
2 of . The rule context may be elements, attributes,
comments and processing instructions.
The assertion test is interpreted according to
Production 1 of , as returning a Boolean value.
The name query is interpreted according to
Production 1 of , as returning a string value.
Typically, the select attribute contains an expression
returning an element node: the name query takes the local or prefixed name of the
node, not its value.
The value-of query is interpreted according to Production
1 of , as returning a string value.
The let value is interpreted according to Production
1 of , as returning a string value.
The notation for signifying the use of parameter of an abstract pattern is to prefix
the name token with the $ character.
This is a character not found as a delimiter in URLs or XPaths.
The $ character not followed by the name
of an in-scope parameter shall not be
treated as a parameter name delimiter. Such a character may
subsequently be used as a delimiter for a variable name or as
a literal character.
A Schematron let expression is treated
as an variable. The $ delimiter signifies the use
of a variables in an context expression, assertion test, name query, value-of
query or let expression.
The $ character not followed by the name
of an in-scope variable shall be
treated as a literal character.
The attributes id, name and prefix should
follow the rules for non-colonized names
for the version of XML used by the document.
The message element shall not be used to provide text for assertions
and diagnostics.