Changes between Version 80 and Version 81 of BluePrintVITA

Timestamp:

03/28/10 13:43:36 (15 years ago)

Author:

Dominic König

Comment:

--

BluePrintVITA

@@ -94 +94 @@
   is a compliant set - it contains the "Entity" (pfif:person), "Distinction" (pfif:person_record_id, pfif:first_name, pfif:last_name), several "Findings" (pfif:sex, pfif:date_of_birth, pfif:age, pfif:photo_url) and plenty of "Evidence" (pfif:author_name, pfif:source_name, etc.).
 
+== Files ==
+
+All data sets describing one and the same instance of a person entity form a '''file'''.
+
+For disambiguation, files are sometimes also called '''case'''s.
+
+=== Central Access ===
+
+All data in a file must be accessible from a central point within the application (the "repository"). Especially the following must be implemented:
+
+  - status of the file as a whole
+  - opening/closing the file for write access
+  - permanent removal of the file as a whole from the repository
+  - a directory of all available record types in that file
+  - export of a file as a whole
+  - import of a file as a whole
+  - merging of files
+
+=== File Level Auditing ===
+
+VITA 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.
+
+Data which will naturally change over time (e.g. the location of a person) must be version-tracked in such way that they can be reconstructed for any point or interval of time.
+
+Data which will only change upon administrative measures (e.g. names) do not need to be version-tracked, with the exception of identities.
+
+==== Status ====
+
+VITA implementations must be able to handle status information of a personal data file as a whole.
+
 == The Data Model ==
 
@@ -107 +137 @@
 
 === Files ===
-
-All data sets describing one and the same instance of a person entity form a '''file'''. Within a file, data must be consistent, especially there must be only one entity for each (atomic) feature.
-
-==== Status ====
-
-VITA implementations must be able to handle status information of a personal data file as a whole.
 
 ==== Roles ====