[LEAPSECS] A new use for Pre-1972 UTC

Rob Seaman seaman at noao.edu
Tue Feb 17 16:44:26 EST 2009


Thanks, that's better.

Ok, so the format is like:

<element_name>-<country_code>-<state_code>-<notary>-<epoch>-<SHA-256>

The hash is over the named element (minus the ID itself). The hash
itself is what does all the heavy lifting. The rest of it is really
for human consumption. A particular notary will be decipherable.
Expressing the epoch as ISO 8601 should be, too. That would permit
easy grepping (for instance) for documents signed by a particular
individual (or agent of same) on a particular date.

5000+ consecutive nights of tracking data issues resulting from
several million documents (images) let me unequivocally assert that
you want ISO 8601 here. Don't keep the date of signing obscure from
the users.

Rob
---

On Feb 17, 2009, at 2:28 PM, Gerard Ashton wrote:


> Perhaps a link to the PDF version will work better:

>

> http://www.oasis-open.org/committees/download.php/31222/ENML-1.0-Specificati

> on.pdf

>

> -----Original Message-----

> From: leapsecs-bounces at leapsecond.com

> [mailto:leapsecs-bounces at leapsecond.com] On Behalf Of Rob Seaman

> Sent: Tuesday, February 17, 2009 3:48 PM

> To: Leap Second Discussion List

> Subject: Re: [LEAPSECS] A new use for Pre-1972 UTC

>

>

> The URL to the OASIS document didn't work for me ...

>

> _______________________________________________

> LEAPSECS mailing list

> LEAPSECS at leapsecond.com

> http://six.pairlist.net/mailman/listinfo/leapsecs




More information about the LEAPSECS mailing list