Dynamic Schematron-Validation and BT-71-Lot

[dnl50]

I don't know if this is an issue just yet, so I will open a discussion about this:

When applying the dynamic Schematron-Rules for a Change Notice (Subtype Code 20) without BT-71-Lot, the Schematron Report always contains the following message:

The BT-71 Reserved Participation for Lot LOT-XXXX must be the same as for the parent notice.

After some investigation I discovered that this Message can be printed by two separate rule, which use different XPath-Expression to compare the values between the parent and the child notice.

The first one uses the XPath deep-equal function (see dynamic-validation-stage-6b.sch Line 213) and the other one just compares the two values with the = operator (see dynamic-validation-stage-6b.sch Line 264). The rule using the deep-equal function works as expected, but the one using the = operator is triggered, eventhough the XPath Expression does not match any nodes.

When the value of BT-71-Lot actually changes, the validation report contains the message mentioned above two times. Is this a problem with the SDK?

[bertrand-lorentz]

Thanks for your feedback !

We indeed changed the rules in dynamic-validation-stage-6b for this kind of problem:
b37b835

The one you mention might have slipped through. We'll have a closer look at it.

[bertrand-lorentz]

In the meantime, the list of fields that must have the same value in a change notice and in the original notice has been significantly reduced.
We've reviewed the content of "validation-stage-6b.sch" so that it does not contradict this. This meant removing a significant number of the rules, including both rules for BT-71-Lot. So the problem described here is resolved by this change, which will be available in SDK 1.9.0.

The commit with the change is:
8d6d8e7

Please note that not all rules on change notices are currently implemented in "validation-stage-6b.sch". We are working on a different approach for those rules, so that we don't have to maintain them entirely manually.