Closed pigelvy closed 7 months ago
I cannot reproduce this Exception on my side.
Looking at my (self-built) XSD, I can see this comment:
<!-- [ph] Schematron 2016 adds this in favor of "document" -->
<xs:attribute name="documents" type="xs:string"/>
...
<xs:attribute name="document" type="xs:string"/>
So this is kind of Schematron-specification dependent.
The RNC of the 2006 specification contains this snippet:
The RNC of the 2016 specification contains the "documents" attribute:
Edit: for Schematron 2020 is identical to 2016 for this field
And ISO Schematron emits the document
attribute:
And finally SchXslt 1.9.5 does it according to Schematron 2016:
It is all very messy....
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Bascially by chosing an implementation you can decide what attribute you will get. Hope this works.
Or shall we modify the ISO Schematron XSLT to produce documents
instead?
Using SchematronResourceSCH (r7.0.1), the SVRL mashalling fails. It seems that the
active-pattern
contains the attributedocument
instead ofdocuments
.Here's a simple JUnit test showing the problem.