[XERCESJ-1730] XSD 1.1 assertions on list types should be on typed value

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.12.1
• Fix Version/s: 2.12.2
• Component/s: XML Schema 1.1 Structures
• Environment: Windows
• Assignee: Mukul Gandhi
• Reporter: Priscilla Walmsley
• Created: 30/Jul/21 11:31
• Updated: 19/Jan/22 11:16
• Resolved: 07/Aug/21 06:31

Description

I am trying to use the XSD in the XSLT 3.0 specification and it contains the following assertion:

 

{{ <xs:assert test="every $prefix in (@exclude-result-prefixesnot(. = '#all'),
@extension-element-prefixes)
satisfies ((if ($prefix = '#default') then '' else $prefix) = in-scope-prefixes(.))">}}

 

I believe Xerces is treating the value of @exclude-result-prefixes like a single value rather than a list of strings. Every XSLT I have that has more than one value in @exclude-result-prefixes is supposedly violating this assertion.

I initially thought this was an issue with the schema itself but Michael Kay pointed out this:

"XSD 1.1 part 2 clause 4.3.13.3 says that in the XDM representation of the tree used for evaluation of an assertion, the atomization of the list-valued attribute @exclude-result-prefixes is the typed value, which is a sequence of tokens. So the tokenization has already been done, implicitly."

So, I believe Xerces has a bug.