Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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: 

  1. Captures the assignment of the IUI to the name in addition to the name
  2. Implicit type of the name is Proper name from the Proper Names Ontology.
  3. Implicit relationship between the name and the temporal entity it designates is designates.
  4. 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

apEither temporal interval or temporal boundary (a.k.a. temporal instant).
ParameterDescriptionNotes
iuipThe IUI of the name of the temporal regionIUIs that designate a temporal region must first be assigned using a Te template.
iuiaThe 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.
ta  
iuiteThe time when the assignment was madeTo 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).uuiThe basic type of the temporal region, according to Basic Formal OntologyIUI of the temporal entity that this name designates.There must be a Te template that assigns this IUI.
nameThe name itself, ideally as a Unicode stringFor example: 2013-11-08T18:00-02:00
nsThe IUI of the naming system to which the name belongsFor example, Gregorian Calendar, Hebrew Calendar, Chinese Calendar, etc. ISO 8601 is a standard for formatting names according to the Gregorian Calendar.
iuitThe IUI of the Te Ten template itselfEvery template gets an IUI that is referenced minimally by one metadata template.

...