Open LBlaive opened 4 months ago
Agree.
This issue needs to be addressed. The transformation into a requirement (“shall”) seems pertinent.
Issue accepted. • The text in the note attached to the “LinearWithinLinearElement” class in the “LinearLocation” class diagram is modified as follows: “When there are multiple instances of this class the attribute linearElementReferenceModel in the associated LinearElement shall be populated to explain the instance.”. • The text in the note attached to the “AlertCLinear” class in the “LinearLocation” class diagram is modified as follows: “When there are multiple instances of AlertCLinear, they shall represent the same location using different location tables.”
What happened?
Comment reported during the Formal Vote ballot in 2018 by FR (no FR029). The note related to the "AlertCLinear" introduces a recommendation regarding the use of different location tables. If the recommendation is not followed, it becomes impossible to correctly interpret the different instances of this class. Idem for "LinearWithinLinearElement". Solution: make the recommendations requirements.
Version
3
Code of Conduct