Version 43 (modified by Dominic König, 14 years ago) ( diff )


Blueprint: VITA Person Entity Model

Version 2.0 - under construction

VITA is the proposed application design for storage, manipulation and communication of person-related information in SahanaPy. It defines a set of data structures, interfaces and interoperability features to be implemented.


VITA defines:

  • an extensible data model for tagging, tracking and tracing of person entities
  • a set of interfaces to request and manipulate person entity data
  • an XML-based data format to communicate person entity data


The 4-axes-model

VITA defines four axes (aspects) for the construction of "Personal Data" relations:

  • Appearance - the appearance form (of persons) the data set relates to
  • Distinction - assigned features for operational distinction
  • Finding - features to be communicated by the data set
  • Evidence - to describe the quality of the data

Any compliant set of person data has to implement at least one feature for each axis.

Appearance can be understood as abstract means to determine the appearance form of persons to which the data set relates (=ownership), which can be types of "Individual", "Group", "Body", "Personal Effects" or "Relationship". This axis does not describe the actually observed appearance form of a person, which indeed can be multiple at the same time.

Distinction can be understood as any features which are used to distinguish particular persons (or groups, bodies...) in operations. It is important to understand that these features are always assigned, i.e. not naturally given - they cannot be observed but have to be communicated. The most commonly used distinction feature for persons is their name, but also identity (=an assigned unique number or character string).

Findings are all other features of the person (group, body...) which are to be communicated in this data set. These features can be either of assigned, observed or derived.

Evidence is a means to describe the quality of findings data. This always includes at least information on origin and time, but can also include references and links to sources or responsible persons, or information on methods of determination. This can even enclose the originating sources themselves, e.g. photograph images.


Ontology draft for "Personal Data for Disaster Management":

(still under development, see the OWL source for version information)

The Data Model

under construction

Data Model Overview

Person Entity

Presence Log

Presence means the fact, that an entity is physically there at a particular location at a particular time. This abstract construction covers even cases of explicit absence, i.e. when the entity is not present at that location at that time.

VITA applications record a presence log for each person entity. Each log entry is established through a recognition event, i.e. when the entity is recognized by a dedicated observer (human or automatic).

Recognition might happen implicitly, e.g. when other data are obtained directly from the entity. In these cases, the time and location of the observer are used for the record. Recognition can also happen explicitly, i.e. in response to observation requests. In such cases, the observation time and location determined by the request are used.

Locations in presence records represent geospatial features, which can basically be of any valid feature class (points, polygons, lines etc.). Where references to locations are used, they must be universally unique and resolvable; otherwise the referred geospatial information have to be enclosed in the database and/or communication.

In contrast to that, time in this regard means one exact time point, to be stored as coordinated universal time (UTC, Gregorian date including century) with a minimum precision of one second. References or relative times must not be used.

Presence Conditions:

Check-Inarriving at this location for storage/accommodation
Check-Outreleased from this location after storage/accommodation
Reconfirmationre-confirmation of storage/accommodation at this location (on request)
Foundonly temporarily at this location, accidentally found
Proceduretemporarily at this location for a procedure
Transittemporarily at this location between two transfers (specify origin and destination)
Transferreleased from this location to be transferred to another (specify destination)
Missingno longer present at this location, but missing
Lostno longer at this location, but destroyed/disposed/deceased here


Contact Information

Address Information

Role and Status



Names are used to identify persons in human communication. However, names of persons do not have to be unique nor do they have to be exact, and thus are no reliable identity features. The following name fields are mandatory to exist in person records:

  • first_name the first names (or the only name) of the person, in romanized script
  • middle_name the person's middle name (if customary), in romanized script
  • last_name the last name (mostly the family name) of the person, in romanized script
  • local_name the full name of the person, in a local language and script


  • Any of these mandatory name fields may be empty in a particular record except first_name.
  • A name field value starting with a question mark ? indicates that this part of the name is uncertain or unknown.
  • 'first', 'middle' and 'last' refer rather to the usual writing order of a person's full name than to the meaning of the name parts.
  • There is no need to split the full name into segments if that is not customary in the person's country of origin - in such case first_name should represent the person's full name.
  • In case there are multiple local languages, the local_name should be in the language/script that is most likely readable by that person and/or their relatives.
  • An application may define additional name fields to represent e.g. titles, nicknames or pseudonyms, however, these additional fields must not be used to repeat or replace any of the mandatory fields.









Attachments (2)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.