Skip to content

Missing Mandatory Constraint for BT-14-Lot in Notice Type 7 #747

Answered by YvesJo
dnl50 asked this question in Q&A
Discussion options

You must be logged in to vote

Hi,
The context for the rules is the node ND-LotProcurementDocument which may contain BT-14-Lot, BT-15-Lot, BT-615-Lot, BT-707-Lot,
OPT-140-Lot.
BT-14-Lot is the "entry point" for the Procurement Documents, in its absence neither the listed fields, nor the parent node shall exist.
In absence of the parent, the rules wouldn't get fired.
Additionally, the existence of the parent node with the the absence of OPT-140-Lot would lead to a non XSD compliant XML instance, while OPT-140-Lot is only allowed when BT-14-Lot is defined.
The 42 condition on the conditionally mandatory rule for BT-615-Lot in Notice Subtype 7 is in fact useless.
Given these details, BT-14-Lot is Mandatory where Procureme…

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@dnl50
Comment options

@YvesJo
Comment options

@dnl50
Comment options

@YvesJo
Comment options

Answer selected by YvesJo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
fields Related to field metadata (/fields/fields.json) validation Related to notice validation.
2 participants
Converted from issue

This discussion was converted from issue #745 on October 31, 2023 14:38.