UML time-zone stereotype conversion behavior
0 reputation · 06 Jun 2022, 13:43 UTC
Goal
Determine whether a UML model element annotated with a time-zone stereotype implies automatic offset conversion during serialization, code generation, or model exchange.
Constraints and uncertainty
UML 2.x is a modeling language, not a runtime platform, and the OMG specification does not mandate a universal DateTime type or built-in time-zone arithmetic. Stereotypes and tagged values express design intent, but their meaning and any automatic conversion are left to profiles, tools, or the implementing platform. Regional calendar rules, daylight-saving transitions, and IANA zone identifiers fall outside UML scope.
It is therefore unclear whether a time-zone-tagged attribute represents a local instant, a UTC instant, or a serialized string without offset adjustment.
Questions
- Does a UML time-zone stereotype imply automatic offset conversion during model serialization?
- Should code generation or model transformation insert conversion logic based solely on the stereotype?
- Where should conversion semantics be defined if not in the UML model itself?
