Module time 

The two ways a certificate writes a moment, read into one.

Both preserve UTC labels, including an inserted second. The form is kept because it is part of what the certificate says: the profile requires the two-digit form through 2049 and the four-digit form afterwards, and a report that has to explain a certificate cannot explain what it did not keep.

Only the fixed-width form with seconds and Z is accepted. The wider encodings the base standard allows, an offset from local time, minutes without seconds, a fractional part, all let one moment be written several ways, and here they would let two documents disagree about when a certificate expired while both claiming to be the same certificate.

Structs

Calendar

Gregorian calendar components of a labelled time, not an elapsed-time proof. The year uses astronomical numbering (zero denotes 1 BCE); callers of other calendar contracts must apply their own specified year-numbering convention.

Time

A moment, and how the certificate wrote it.

Xsd10Label

Bounded calendar components in XML Schema Datatypes 1.0 year numbering. Year -1 denotes 1 BCE; zero is not a valid label. This is a value-space bridge for already decoded fields, not an XML lexical parser. Arbitrary precision lexical years/fractions remain with the caller’s schema reader.

Enums

Form

Which form a time was written in.

Relation

UTC-qualified relation of a source label to the caller’s lossless reading. This is a temporal fact, not a rule for application acceptance.

Constants

NO_WELL_DEFINED_EXPIRY

The moment 99991231235959Z names, which the profile uses to say that a certificate has no well defined expiry rather than that it expires then.