In the example presented during the webinar dd. 2021-03-30, the following example flow of Requirements was given:
Criterion: The applicant is an adult.
Information Requirement: The age of the applicant.
Constraint: The applicant must be at least 18 years of age.
The question was asked to the Working Group whether all these steps in the flow of Requirements are always required. Can one for example also use the Information Requirement solely without specifying a Criterion.
During the webinar, most participants agreed that this decision should be left to the application/implementation and thus to keep it flexible within the Core Vocabulary.
Disjointness of the three Requirement subclasses is currently also not stated explicitly and thus also left to the implementor.
In the example presented during the webinar dd. 2021-03-30, the following example flow of Requirements was given:
The question was asked to the Working Group whether all these steps in the flow of Requirements are always required. Can one for example also use the Information Requirement solely without specifying a Criterion.
During the webinar, most participants agreed that this decision should be left to the application/implementation and thus to keep it flexible within the Core Vocabulary.
Disjointness of the three Requirement subclasses is currently also not stated explicitly and thus also left to the implementor.