...
| Parameter | Description | Notes |
|---|
| iuip | The IUI that designates the particular that is the subject of this template | |
| iuia | The IUI that designates the author of this template | |
| ta | The IUI that designates the temporal region at which this PtoU assertion was made | |
| inst | The relation that holds between the particular denoted by iuip and the universal denoted by uui | It is called "inst" because it is typically the is instance of relation, but other relations can be used here such as is about. |
| uui | The UUI that designates the universal to which the particular is related | Typically a Uniform Resource Identifier (URI) from an OWL ontology. But not necessary. |
| iuioiuio | The IUI of the ontology from which uui and inst were obtained | Increasingly, this parameter seems irrelevant. Although MIREOT allows that a given URI for a universal could come from any number of ontologies, it is not clear that it is valuable to say which one it came from specifically. Furthermore, we might have taken the relation (inst) and uui from different ontologies. It is not clear how to handle that situation either. |
| tr | The temporal region during which the relation inst holds between the particular (iuip) and universal (uui) | |
| iuit | The IUI of the template itself | Every template gets an IUI that is referenced minimally by one metadata template. |
Te
The temporal entity template captures both the assignment of an IUI to, and the basic type (instance vs. interval) of, a given temporal region. With the Ten template, it simplifies management of temporal entities and their names.
| Parameter | Description | Notes |
|---|
| iuip | The IUI that has been assigned to a temporal region | IUIs that designate a temporal region must first be assigned using a Te template. |
| iuia | The IUI that designates the entity who assigned iuip to a particular | The entity that assigned the IUI to the temporal region. |
| tap | 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). |
| iuit | The IUI of the Te template itself | Every template gets an IUI that is referenced minimally by one metadata template. |
Ten
PtoP
The particular-to-particular template captures the assertion that a relationship holds between a set of particulars.
| Parameter | Description | Notes |
|---|
| iuip | The IUI that designates the particular that is the subject of this template | |
| iuia | The IUI that designates the author of this template | |
| ta | The IUI that designates the temporal region at which this PtoP assertion was made | |
| p | The set of IUIs that denote that particulars that stand in the relation r | The first IUI in the set is redundant with iuip. Also, typically these will be binary relations, and there will only be two IUIs in this set. However, there is nothing inherent to referent tracking that limits the PtoP template to binary relations, and relations of any arity can be accomodated. |
| r | The relation that holds between the particulars | It is called "inst" because it is typically the is instance of relation, but other relations can be used here such as is about. |
| iuio | The IUI of the ontology from which r was obtained | Increasingly, this parameter seems irrelevant. Although MIREOT allows that a given URI for a relation could come from any number of ontologies, it is not clear that it is valuable to say which one it came from specifically. |
| tr | The temporal region during which the relation r holds between the particulars (p) | |
| iuit | The IUI of the template itself | Every template gets an IUI that is referenced minimally by one metadata template. |
PtoLackU
...