Uploaded image for project: 'Specification PR tracker'
  1. Specification PR tracker
  2. SPECPR-157

Remove ambiguity in ISO8601_TIME Class on fractional seconds

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: RM Release 1.0.3
    • Fix Version/s: RM Release 1.0.4
    • Component/s: RM Support IM
    • Labels:
      None
    • Environment:
      N/A

      Description

      ISO8601 spec allows for capturing time down to microseconds (0.000001) - that is 6 digits after decimal point. While current RM ISO8601_TIME Class defines Real type to capture fractional seconds there's potentially conflicting information which depicts: hh:mm:ss[,sss][Z | ±hh[mm]] (Note 3 fractional digits which can only cater for milliseconds)
      It seems at least one implementation (Marand) is not saving >3 digits after decimal point so they may have implemented this as a constraint.
      I suggest revising these format statements as: hh:mm:ss[,ssssss][Z | ±hh[mm]] And also providing accompanying text to clarify this is not a limitation and values for microseconds (and possibly beyond) should be supported.
      Ocean's Archetype Editor also provide microseconds as an option to define Event's periodicity and to define Interval duration but fail to save with Archetype (Hence is a bug).

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                thomas.beale Thomas Beale
                Reporter:
                atalagk Koray Atalag
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: