GEMS 1.0 NO IDEA Avatar
  1. OMG Issue

GEMS — GEMS PIM Time stamp definition is vague and needs to be clarified

  • Key: GEMS-4
  • Legacy Issue Number: 12757
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The time stamp in the message header is loosely defined in the document. Need to clarify this. Suggest UTC following the time parameter type.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Update all related time stamp fields to specify UTC. Also changed the examples in the GEMS-ASCII PSM section to us ASCII time parameter format for the time stamp.
    NOTE: There is an associated issue with this that was identified during the voting process. The time format is closer to POSIX than UTC and does not allow for unambiguous leap second resolution. Because the format of the message will likely not change, this should not impact GEMS 1.0 implementations. There are however several considerations that need to be taken in to account before a final decision can be made on using UTC vs POSIX. Therefore, the FTF is accepting the 3/4 yes vote as resolution of issue 12757. A new issue has been created (13132) and will be handled under a subsequent RTF to specifically address the UTC vs POSIX time concerns.

  • Updated: Fri, 6 Mar 2015 20:58 GMT