-
Type: Bug
-
Status: Closed
-
Priority: Critical
-
Resolution: Won't Fix
-
Component/s: EDXL-TEP
-
Labels:None
-
Environment:
Normative
-
Proposal:
-
Resolution:
1.4 Terminology reads in part:
-
-
-
-
In addition, within this Specification, the keyword “CONDITIONAL” should be interpreted as potentially “REQUIRED” or “OPTIONAL” depending on the surrounding context.
-
-
-
It isn't cricket to use a keyword to mean opposite things depending on context.
"CONDITIONAL" appears only twice in this document:
Both under unitNumber,
-
-
-
-
-
Usage: CONDITIONAL; MAY be used once but only once [0..1]
-
-
-
-
Constraints: CONDITIONAL (If "providerKind" is EMS, then "unitNumber" is REQUIRED)
Elements often have occurrence or co-occurrence constraints.
It is sufficient to state the constraint without the "CONDITIONAL" keyword, thus:
Delete: 1.4 "In addition, within this Specification, the keyword “CONDITIONAL” should be interpreted as potentially “REQUIRED” or “OPTIONAL” depending on the surrounding context."
unitNumber, delete "CONDITIONAL" so that the remaining text reads:
Usage: MAY be used once but only once [0..1]
Constraints: If "providerKind" is EMS, then "unitNumber" is REQUIRED
which agrees with standard markup practices.