Talk:NTCHRS

jens 16:39, 14 September 2009 (UTC)

o.k. should we amend the measure to seconds or constructions allowing dd/hh/mm ? That would provide more flexibility.

raphael 20:21, 14 September 2009 (UTC): OK. I suggest requiring the time to be according to the ISO 8601 time interval (duration) format.

jens 05:10, 15 September 2009 (UTC)

The standard looks fine. Checked in wikipedia (German Version). If not receiving other comments the definition can be amended accordingly.

raphael 16:52, 30 October 2009 (UTC): Fine. The definition can become:

The time duration prior to the time the service is needed, when notice must be provided to the service provider.

And the Resolution, Example, and Constraints can be deleted.

raphael 08:17, 15 January 2010 (UTC): TSMAD changed our proposed "Resolution" to "Precision" and I believe they also decided to remove Quantity. Will consult S-100 to find out the latest situation. The datatype should also be changed from "Integer" in accordance with the decision above about "measure".

DavidAcland 14:22, 24 March 2010 (UTC) I have checked with UKHO radio signals production and they say we often have notices of "1.5" or "2.5". Unless I missunderstand "Integer" this will not work. So I have changed the data type to "Real".

--raphael 02:09, 26 March 2010 (UTC): Type "Real" is fine but then we should delete the references to ISO8601 to keep it internally consistent. ISO 8601 format would allow a string like "PT1H30M" for a duration of 1 hour 30 minutes while a Real value would be coded like any other real number.

jens 11:31, 26 March 2010 (UTC) ok, I remove the reference to ISO8601. I must be clear to us, that we have to work only with real (hours) in the future. I only write that, because I can hear the crying people saying "How to model 2 days in advance?" That is fixed herewith. "BZ"

raphael 14:26, 26 March 2010 (UTC): "BZ", Jens.