...
For every temporal entity for which we store a name, we ought to also store the UTC name (2013-11-08T20:00Z) in the RTS ideally.
Notes:
- Captures the assignment of the IUI to the name in addition to the name
- Implicit type of the name is Proper name from the Proper Names Ontology.
- Implicit relationship between the name and the temporal entity it designates is designates.
- Every Ten template is associated with one Te template. A Te template may be associated with multiple Ten templates.
The IUI that designates the temporal region at which this PtoU assertion was made
Parameter | Description | Notes | ||||
---|---|---|---|---|---|---|
iuip | The IUI of the name of the temporal region | IUIs that designate a temporal region must first be assigned using a Te template. | ||||
iuia | The IUI that designates the entity who asserted this name for the temporal entity. | The entity that asserted that this name denotes a particular temporal entity. | ||||
t | apa | |||||
iuite | The time when the assignment was made | To avoid complexities of using temporal region IUIs here, we simply use an ISO8601 compliant date/time string (e.g., 2013-10-31T14:48:32.234-05:00). | uui | The basic type of the temporal region, according to Basic Formal Ontology | Either temporal interval or temporal boundary (a.k.a. temporal instant).IUI of the temporal entity that this name designates. | There must be a Te template that assigns this IUI. |
name | The name itself, ideally as a Unicode string | For example: 2013-11-08T18:00-02:00 | ||||
ns | The IUI of the naming system to which the name belongs | For example, Gregorian Calendar, Hebrew Calendar, Chinese Calendar, etc. ISO 8601 is a standard for formatting names according to the Gregorian Calendar. | ||||
iuit | The IUI of the Te Ten template itself | Every template gets an IUI that is referenced minimally by one metadata template. |
...