Changes between Version 105 and Version 106 of BluePrintVITA


Ignore:
Timestamp:
11/29/10 13:47:47 (11 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintVITA

    v105 v106  
    9191== Design ==
    9292
    93 === Ontology ===
     93
     94=== Registries ===
     95
     96All data sets describing the same instance of a person entity form a '''file'''.
     97
     98All files for an entity type are accessible through a central '''registry'''.
     99
     100The registry implements the following:
     101
     102  - dereferencing of URI's
     103  - CRUD access brokerage for file contents
     104  - file-access auditing
     105  - classification of files
     106  - administration of file status
     107  - administration of access permission to a file as a whole
     108  - permanent removal of a file as a whole
     109  - a directory of all available record types in a file
     110  - coverage statistics of files
     111  - export of a file as a whole
     112  - import of a file as a whole
     113  - merging of files
     114
     115=== Auditing ===
     116
     117VITA 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.
     118
     119Data which will naturally change over time (e.g. the location of a person) must additionally be version-tracked in such way that they can be reconstructed for any point or interval of time.
     120
     121Data which only change upon administrative measures (e.g. names) do not need to be version-tracked.
     122
     123=== Data Model ===
     124
     125==== Overview ====
     126
     127[[Image(vita.png)]]
     128
     129This diagram is not complete and just meant to illustrate the general data structure.
     130
     131==== Background ====
    94132
    95133VITA defines four axes (aspects) for the construction of any "Personal Data":
     
    106144  - [http://ontology.nursix.org/vita.owl OWL Source] ([http://ontology.nursix.org/vita.png Class Tree])
    107145
    108 ==== Entity ====
     146===== Entity =====
    109147
    110148The ''entity'' axis determines the entity type to which the data set relates (=ownership), which can be types of:
     
    116154  - Relationship
    117155
    118 ==== Distinction ====
     156===== Distinction =====
    119157
    120158The ''distinction'' axis describes any features which are used to distinguish particular person entities.
     
    126164Identities don't have to be unique across multiple domains. In case they are not, any communications of identities have to enclose a reference to the domain which administrates the particular identity (administrative domain).
    127165
    128 ==== Findings ====
     166===== Findings =====
    129167
    130168''Findings'' are all other features of the person entity which are to be communicated in this data set. These features can be assigned, observed or derived.
     
    132170  ''In the VITA context, photographs or other images are findings, not evidence.''
    133171
    134 ==== Evidence ====
     172===== Evidence =====
    135173
    136174''Evidence'' is any suitable means to describe the quality of data of the findings.
     
    138176  ''This always includes at least information on origin and time of the particular finding, but can also include references and links to sources, or information on methods of determination.''
    139177
    140 ==== Examples ====
     178===== Examples =====
    141179
    142180{{{
     
    174212  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.).
    175213
    176 === Registries ===
    177 
    178 All data sets describing the same instance of a person entity form a '''file'''.
    179 
    180 All files for an entity type are accessible through a central '''registry'''.
    181 
    182 The registry implements the following:
    183 
    184   - dereferencing of URI's
    185   - CRUD access brokerage for file contents
    186   - file-access auditing
    187   - classification of files
    188   - administration of file status
    189   - administration of access permission to a file as a whole
    190   - permanent removal of a file as a whole
    191   - a directory of all available record types in a file
    192   - coverage statistics of files
    193   - export of a file as a whole
    194   - import of a file as a whole
    195   - merging of files
    196 
    197 === Auditing ===
    198 
    199 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.
    200 
    201 Data which will naturally change over time (e.g. the location of a person) must additionally be version-tracked in such way that they can be reconstructed for any point or interval of time.
    202 
    203 Data which only change upon administrative measures (e.g. names) do not need to be version-tracked.
    204 
    205 === Data Model ===
    206 
    207 ==== Overview ====
    208 
    209 [[Image(vita.png)]]
    210 
    211214==== Undefined values ====
    212215