-
Key: DMN16-60
-
Status: closed
-
Source: Trisotech ( Mr. Denis Gagne)
-
Summary:
It should be possible to define partial temporal values but only for trailing precisions (i.e., if you specify a day, you must also specify a year and month)
Values of type Date, the precision unit must be one of: years, months, or Days
e.g. date( 2019 ), date( 2019, 09 ), date( 2019, 09, 17)
Values of type Time, the precision unit must be one of: hours, minutes, or seconds
e.g. time( 09 ), time( 09, 55), time( 09, 55, 00)
Values of type Date and Time, the precision unit must be one of: years, months, days, hours, minutes, or seconds
e.g. date and time( date(2019,09,17), time(09,55) ), date and time( “2019-09-17T09:55”)Operations carried out on elements with different time based precision units shall be done based on the lowest common precision unit (truncating any resulting decimal portion)
-
Reported: DMN 1.3 — Tue, 26 Jan 2021 22:17 GMT
-
Disposition: Deferred — DMN 1.6b1
-
Disposition Summary:
Defer to DMN 1.7
Defer to DMN 1.7
-
Updated: Mon, 16 Sep 2024 14:16 GMT
DMN16 — Allow for partial temporal values
- Key: DMN16-60
- OMG Task Force: Decision Model and Notation 1.6 RTF