Changes between Version 47 and Version 48 of BluePrintVITA


Ignore:
Timestamp:
03/28/10 00:49:37 (12 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintVITA

    v47 v48  
    1313  - an XML-based data format to communicate person entity data
    1414
    15 == Ontology ==
    16 
    17 === The 4-axes-model ===
     15== 4-Axes-Model ==
    1816
    1917VITA defines four axes (aspects) for the construction of "Personal Data":
     
    2624  * '''Evidence''' - to describe the quality of the data
    2725
    28 Any compliant set of person data has to implement at least one feature for each axis.
     26Any compliant set of personal data has to implement at least one feature for each axis.
    2927
    30 '''Appearance''' can be understood as abstract means to determine the entity type to which the data set relates (=ownership), which can be types of:
     28=== Appearance ===
     29
     30Appearance can be understood as abstract means to determine the entity type to which the data set relates (=ownership), which can be types of:
    3131
    3232  - Individual
     
    3838  ''The Appearance axis does not describe the actually observed appearance form of a person, which indeed can be multiple at the same time.''
    3939
    40 '''Distinction''' can be understood as any features which are used to distinguish particular entities in operations.
     40=== Distinction ===
    4141
    42   ''It is important to understand that Distinction 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 person entities are their names, but often also identities (=assigned unique numbers or character strings).''
     42Distinction is to be understood as any features which are used to distinguish particular entities in operations.
     43
     44  ''It is important to understand that Distinction 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 person entities are names.''
     45
     46Distinction features may be ambiguous, even within the same domain (e.g. database). However, it is desirable to assign at least at least one unique feature in order to identify person entities. Such unique features are called '''Identity''' (ID).
     47
     48Identities 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 that originates the identity.
     49
     50=== Findings ===
    4351
    4452'''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.
    4553
     54=== Evidence ===
     55
    4656'''Evidence''' is a means to describe the quality of findings data. 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. This can even enclose the originating sources themselves, e.g. photograph images.
    47 === Files ===
     57
     58=== Ontology ===
    4859
    4960Ontology draft for "Personal Data for Disaster Management":
     
    5364
    5465''(still under development, see the OWL source for version information)''
     66
    5567== The Data Model ==
    5668
     
    5870
    5971[[Image(vita.png)]]
    60 
    61 === Person Entity ===
    6272
    6373=== Presence Log ===
     
    8494  ||Lost||no longer at this location, but destroyed/disposed/deceased here||
    8595
    86 === Identity ===
    87 
    88 === Contact Information ===
    89 
    90 === Address Information ===
    91 
    92 === Role and Status ===
    93 
    94 === Person ===
    95 
    9696==== Names ====
    9797
     
    112112 * 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.
    113113
    114 === Group ===
    115 
    116 === Findings ===
    117 
    118 == Functions ==
    119 
    120 == Interfaces ==
    121 
    122 === UUIDs ===
    123 
    124 
    125114== Motivation ==
    126115