Changes between Version 83 and Version 84 of BluePrintVITA


Ignore:
Timestamp:
03/28/10 13:50:08 (12 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintVITA

    v83 v84  
    112112  - merging of files
    113113
    114 === File Level Auditing ===
     114=== Auditing ===
    115115
    116116VITA implementations must be able to log all successful attempts to access and/or manipulate data in a file, even if the application does not require auditing. All logs, regardless of their actual granularity, must be available as a function of the file.
     
    119119
    120120Data which only change upon administrative measures (e.g. names) do not need to be version-tracked.
     121
    121122== The Data Model ==
    122 
    123 === Entity Model ===
    124123
    125124''under construction''
     
    131130Some (atomic) features in personal data sets are not applicable to all instances of the set (e.g. "Occupation" not applicable for infants), thus undefined values can be ambiguous here. For disambiguation, VITA implementations handle undefined values always as "not available", whereas "not applicable" must be defined explicitly and must not be the default value.
    132131
    133 === Files ===
    134 
    135 ==== Roles ====
     132=== Roles ===
    136133
    137134Any person entity can be assigned to roles, which qualify the entity for inclusion into certain processes. One and the same instance of the entity can be assigned to multiple roles at the same time.
     
    139136Within a role, the entity instance can be assigned to a status, where the status values must be discrete, unambiguous and consistent. There can only be one status per instance and role at a time. VITA implementations should keep a tally of all status transitions of an entity instance in such way that it is possible to reconstruct the role and status of the entity instance for any point or interval of time.
    140137
    141 ==== Presence ====
     138=== Presence ===
    142139
    143140Presence 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.
     
    162159  ||Lost||no longer at this location, but destroyed/disposed/deceased here||
    163160
    164 ==== Names ====
     161=== Names ===
    165162
    166163Names 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: