| Joerg - Ok - I was hoping to have a discussion on how this breaks the schematron because the other way breaks the OCL This constraint logic has always been a confusing point but if i have a base property that has a cardinality of 0..* and you define a constraint of “SHOULD HAVE ONE” struc docs wants the cardinality in guide to be 0..1 - if you implement this literally - it will never be “invalid” so we imply a lower property of 1 for that reason in the OCL
How does this approach impact schematron ?
Thanks Sean
A quick check on ereferal reveals shows
this change breaks both the schematron/xpath at 11 places, so it
should be revised
I modified the cardinality to support open and closed
Open will use “not isEmpty” while closed will use size >= property.getlower and size <= property.getupper
This is working for consol and consol2
Is this going to impact the schematron generation as the original change was made as part of schematron
https://git.eclipse.org/r/#/c/74122/
Thanks
Sean
_______________________________________________
mdht-dev mailing list
mdht-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdht-dev
_______________________________________________
mdht-dev mailing list
mdht-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdht-dev
|
