FIBOFTF — The current Addresses.rdf specification does not allow for the temporality of addresses that are associated with an entity

1) The current Addresses.rdf specification does not allow for the temporality of addresses that are associated with an entity. Addresses change over time. For example, a corporate mailing address may change. It would be useful to introduce the ability to define an n-ary relation between an entity and an address, such that the n-ary relation that describes the address relation can include various date values, e.g. effective or start date, termination date or end-date, or even perhaps as-of-date. This would support the ability to track address changes over time. This also is equivalent to the notion that addresses are ìthings in a roleî. The role relation must reflect temporality.

The current Addresses.rdf specification does not allow for the temporality of addresses that are associated with an entity

The FIBO FND specification provides a conceptual model for addresses, not an operational one. Temporality and other features specific to various applications have not been included as they are out of scope, in other words.

Having said this, the FTF agrees that there are a number of data properties that assume certain structures of addresses that are overly constraining, and FIBO FND users should be able to map addresses to any standard or practice used in their organizations. As a result, the resolution to this issue involves elimination of all data properties in the addresses ontology, the addition of two ontologies (Arrangements and IdentifiersAndIndices) in a new module (Arrangements), a new class called AddressingScheme, and creating relationships between address and addressing scheme through property restrictions.