Changes between Version 47 and Version 48 of BluePrintVITA
- Timestamp:
- 03/28/10 00:49:37 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrintVITA
v47 v48 13 13 - an XML-based data format to communicate person entity data 14 14 15 == Ontology == 16 17 === The 4-axes-model === 15 == 4-Axes-Model == 18 16 19 17 VITA defines four axes (aspects) for the construction of "Personal Data": … … 26 24 * '''Evidence''' - to describe the quality of the data 27 25 28 Any compliant set of person data has to implement at least one feature for each axis.26 Any compliant set of personal data has to implement at least one feature for each axis. 29 27 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 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: 31 31 32 32 - Individual … … 38 38 ''The Appearance axis does not describe the actually observed appearance form of a person, which indeed can be multiple at the same time.'' 39 39 40 '''Distinction''' can be understood as any features which are used to distinguish particular entities in operations. 40 === Distinction === 41 41 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).'' 42 Distinction 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 46 Distinction 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 48 Identities 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 === 43 51 44 52 '''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. 45 53 54 === Evidence === 55 46 56 '''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 === 48 59 49 60 Ontology draft for "Personal Data for Disaster Management": … … 53 64 54 65 ''(still under development, see the OWL source for version information)'' 66 55 67 == The Data Model == 56 68 … … 58 70 59 71 [[Image(vita.png)]] 60 61 === Person Entity ===62 72 63 73 === Presence Log === … … 84 94 ||Lost||no longer at this location, but destroyed/disposed/deceased here|| 85 95 86 === Identity ===87 88 === Contact Information ===89 90 === Address Information ===91 92 === Role and Status ===93 94 === Person ===95 96 96 ==== Names ==== 97 97 … … 112 112 * 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. 113 113 114 === Group ===115 116 === Findings ===117 118 == Functions ==119 120 == Interfaces ==121 122 === UUIDs ===123 124 125 114 == Motivation == 126 115
