DMN17 — Discrepancy in property between metamodel and specification (requiresInformation)

The association InformationRequirement2requiredDecision defines two properties based on its role ends:
Name (Role B): requiredDecision: Decision [0..1]
Name (Role A): requiresInformation: InformationRequirement [0..*]

The requiresInformation end of the association does not appear in the DMN specification, although the requiredDecision end does. If this is intentional, recommend updating the following aspects of the association (was -> is):
Name (Role A): requiresInformation -> ""
Multiplicity (Role A): 0..* -> Unspecified
Navigable (Role A): TRUE -> FALSE
If the property should be included, then recommend adding its description to the specification and updating the symbol properties for the association to show the name for the role end on the Decision diagram (source for Figure 6-13) and anywhere else it is used.