You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The class CriterionRequirement in CCCEV v.1 had properties expectedDataType, expectedValue, maximumValue, minimumValue etc., which are necessary to specify e.g. the requirement "age (positiveInteger) >= 20" machin-readably.
The class Criterion Requirement in CCCEV v.1 is split into the classes Requirement, Information Requirement and Constraint in CCCEV v.2, without explicitly mentioning where the abovementioned (and several other) properties of Criterion Requirement are in v.2.
Our questions are:
Where are the properties of Criterion Requirement in CCCEV v.1 now in CCCEV v.2? If they are intentionally omitted, why? As exemplified above, they are necessary in order to have machin-readable specifications of requirements and they should be standardized at the EU level.
If they are not going to be included in CCCEV v.2, are the properties cccev:expectedDataType (with cccev namespace) etc. deprecated, or is it still allowed and advisable to use them (with new domains), in our national application profiles of CPSV-AP?
The text was updated successfully, but these errors were encountered:
Should I post this issue to CCCEV (as well)?
CPSV-AP v.3.0.0 uses CCCEV v.2.00.
The class CriterionRequirement in CCCEV v.1 had properties expectedDataType, expectedValue, maximumValue, minimumValue etc., which are necessary to specify e.g. the requirement "age (positiveInteger) >= 20" machin-readably.
The class Criterion Requirement in CCCEV v.1 is split into the classes Requirement, Information Requirement and Constraint in CCCEV v.2, without explicitly mentioning where the abovementioned (and several other) properties of Criterion Requirement are in v.2.
Our questions are:
The text was updated successfully, but these errors were encountered: