Difference between revisions of "Talk:SMTOFF"

From IHO Nautical Information Processing Working Group
Jump to navigation Jump to search
(New page: ~~~~: I think the format for offset should be the more common hours and minutes format. Wikipedia (http://en.wikipedia.org/wiki/ISO8601#Time_offsets_from_UTC) and the Internet standard RFC...)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
[[User:Rmm|raphael]] 18:59, 3 February 2012 (UTC): I think the format for offset should be the more common hours and minutes format. Wikipedia (http://en.wikipedia.org/wiki/ISO8601#Time_offsets_from_UTC) and the Internet standard RFC 3339  use hours and minutes.
 
[[User:Rmm|raphael]] 18:59, 3 February 2012 (UTC): I think the format for offset should be the more common hours and minutes format. Wikipedia (http://en.wikipedia.org/wiki/ISO8601#Time_offsets_from_UTC) and the Internet standard RFC 3339  use hours and minutes.
 +
 +
 +
[[User:DavidAcland|DavidAcland]] 12:39, 4 February 2012 (UTC) Thank you Raphael.  I am very happy to use a standard although I do not know of any summertime offsets which are other than 1 hour, i.e. "01" or "+01:00".
 +
 +
But assuming that a nation was to specify a summer time difference of 1.5 hours, using the standard the encoder would have to put in:
 +
 +
+01:30
 +
 +
Does this mean that the data type must now be "String"?
 +
 +
Reading the wiki entry on ISO8601 has introduced another slight concern in my mind.  The Wikipedia entry on ISO8601 uses the word "Offset" to describe the differences between UTC and LT for both standard time and summer times.  I fear we may confuse things, or some may be confused, if we also use "Offset" for the difference between summer time and standard time. To help clarity, perhaps we could use the word "Shift", or a better synonym if we can find one, for the difference between summer time and normal zone time, i.e. summerTimeShift; SMTSFT.
 +
 +
[[User:Jens|jens]] 12:44, 4 February 2012 (UTC) Hey guys, do we have areas where the summer time offset is not +1h? The attribute becomes superfluous if we couldn't find suchnan area.

Revision as of 12:44, 4 February 2012

raphael 18:59, 3 February 2012 (UTC): I think the format for offset should be the more common hours and minutes format. Wikipedia (http://en.wikipedia.org/wiki/ISO8601#Time_offsets_from_UTC) and the Internet standard RFC 3339 use hours and minutes.


DavidAcland 12:39, 4 February 2012 (UTC) Thank you Raphael. I am very happy to use a standard although I do not know of any summertime offsets which are other than 1 hour, i.e. "01" or "+01:00".

But assuming that a nation was to specify a summer time difference of 1.5 hours, using the standard the encoder would have to put in:

+01:30

Does this mean that the data type must now be "String"?

Reading the wiki entry on ISO8601 has introduced another slight concern in my mind. The Wikipedia entry on ISO8601 uses the word "Offset" to describe the differences between UTC and LT for both standard time and summer times. I fear we may confuse things, or some may be confused, if we also use "Offset" for the difference between summer time and standard time. To help clarity, perhaps we could use the word "Shift", or a better synonym if we can find one, for the difference between summer time and normal zone time, i.e. summerTimeShift; SMTSFT.

jens 12:44, 4 February 2012 (UTC) Hey guys, do we have areas where the summer time offset is not +1h? The attribute becomes superfluous if we couldn't find suchnan area.