
Thanks for this notification. I am a Canadian participant in ISO TC154 standardization work with respect to ISO 8601 Representation of Dates and Times as well as in ISO/IEC JTC1 SC32 Data Management and Interchange and SC27 Security Services. I also working in the voluntary standards area for Industry Canada's Task Force on Electronic Commerce. The reason for this introduction is that in various standardization areas and business sectors there is an increasing need for a standard for a date/time stamping service, related protocols and even trusted third party(TTP) certified time stamps, etc. My approach here is (1) is do not do work that overlaps/duplicates that which already exists, (2) utilise expertise that exists and work that is already done (or being done); and (3) do not "over kill", i.e. business, scientific and other requirements are not homogeneous and depending on the nature of the business transaction, application, etc. require different levels of granularity/degrees of preciseness not do users require TTPs, asymmetric cryptographic algorithms, etc. at all times. A modular, lego-block approach is needed. Can any of you help me out on this? Have some ideas? Are any of you aware of "standardised" approaches/implementations for date/time stamping services currently in existence that can/should serve as input into the development of an international standard?, etc. Comments, info, advice, etc. here is much appreciated. Regards - Jake Knoppers <<mpereira@istar.ca>>

"Infoman Inc." wrote on 1999-01-28 14:46 UTC:
I am a Canadian participant in ISO TC154 standardization work with respect to ISO 8601 Representation of Dates and Times as well as ...
Ah, good. Is there a newer draft of ISO 8601 available than the one on <http://www.cl.cam.ac.uk/~mgk25/8601v04.pdf> that Louis Visser has sent me exactly a year ago? The draft that I have still says (and did over many revisions) in awkwardly long-winded language that NOTE: To be precise, it should be mentioned that the naming and numbering of the days of the week correspond with assigning to the date of 2000-01-01 the name Wednesday. This will cause a major disruption of our calendar system, because >90% of all computers in operation still believe that my 29th birthday will be a Saturday and not a Wednesday ... ;-) Unnecessary to say that ISO 8601:1999 still needs a lot of proof-reading.
Can any of you help me out on this? Have some ideas? Are any of you aware of "standardised" approaches/implementations for date/time stamping services currently in existence that can/should serve as input into the development of an international standard?, etc.
My accumulated, condensed, and distilled knowledge on this topic is embedded in http://www.cl.cam.ac.uk/~mgk25/c-time/ http://www.cl.cam.ac.uk/~mgk25/iso-time.html where you will also find numerous pointers to relevant literature. Markus -- Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
participants (3)
-
Denis.Excoffier@ens.fr
-
Infoman Inc.
-
Markus Kuhn