att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601 standard. [13.3.6 Dates and Times]
Modulenamesdates — 13 Names, Dates, People, and Places
Membersatt.datable [licence application creation change date time origDate origPlace stamp binding seal origin provenance acquisition custEvent orgName persName placeName bloc country region district settlement geogName geogFeat affiliation age birth climate death education event faith floruit langKnowledge langKnown location nationality occupation population relation residence sex socecStatus state terrain trait]
AttributesAttributes
when-isosupplies the value of a date or time in a standard form.
Status Optional
Datatype 

<rng:ref name="data.temporal.iso"/>
data.temporal.iso
Values Any string representing a valid date, time, or one of a variety of combinations.

The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.

<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date>
<date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date>
<time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time>
<time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time>
<date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date>
<time when-iso="03:00">3 A.M.</time>
<time when-iso="14">around two</time>
<time when-iso="15,5">half past three</time>

All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.

He likes to be punctual. I said <q>
 <time when-iso="12">around noon</time>
</q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.

The second occurence of time could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes specification. The first occurence could not.

Note
The value of the when-iso attribute should be the normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601, using the Gregorian calendar.
notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype 

<rng:ref name="data.temporal.iso"/>
data.temporal.iso
Values A normalized form of temporal expression conforming ISO 8601.
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype 

<rng:ref name="data.temporal.iso"/>
data.temporal.iso
Values A normalized form of temporal expression conforming ISO 8601.
from-isoindicates the starting point of the period in standard form.
Status Optional
Datatype 

<rng:ref name="data.temporal.iso"/>
data.temporal.iso
Values A normalized form of temporal expression conforming ISO 8601.
to-isoindicates the ending point of the period in standard form.
Status Optional
Datatype 

<rng:ref name="data.temporal.iso"/>
data.temporal.iso
Values A normalized form of temporal expression conforming ISO 8601.
Note
If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date when-iso="2007-06-01" dur-iso="P8D"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>
In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.