Hi,

It has something to do with the rules matching on an attribute. I've modified a bit the Schematron file to match on the element that contains that attribute and the tests pass. I've attached these changed resources (actually just media-type.sch is changed).

I'm not sure why it behaves like that. I've reproduced the issue with the command line XSpec 2.1.4 latest release. I recommend asking a question in an issue on the XSpec GitHub project [1] or on the email address xspec-users@googlegroups.com . I'm sure the project maintainers will know the cause and give you a recommendation.

[1] https://github.com/xspec/xspec/issues

Best regards,
Alex
-- 
Alex Jitianu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
On 7/2/2021 11:28 PM, Gary Gapinski wrote:

Hello, all:

I have found creation of XSPec unit tests for Schematron assertions a bit puzzling. I frequently manage to create Schematron which works correctly for instance document validation but related XSpec scenarios produce incorrect results. I may be repeatedly doing something erroneous but have yet to determine what.

I am using <oXygen/> XML Editor 23.1, build 2021061407 which includes an XSpec 1.6.0 framework.

An exemplar of my problem can be seen at https://github.com/18F/fedramp-automation/commit/d023c719754ee5ed14dfc8a8991fbfafb82ff18b. The Schematron (media-type.sch) works correctly with an instance document (media-type.xml) but both XSpec scenarios (in media-type.xspec) fail when the inbuilt "Run XSpec Test" translation scenario is used.

Any and all suggestions are welcome.

Best regards,

Gary

--
Gary Gapinski's contact information
Gary Gapinski
+1 216 820 1849
gary@garygapinski.com
gary@garygapinski.com

_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user