Changes between Version 5 and Version 6 of ISO15926inOWLLevels

Show
Ignore:
Timestamp:
07/02/08 13:10:46 (16 years ago)
Author:
margs (IP: 193.212.132.34)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ISO15926inOWLLevels

    v5 v6  
    1414 
    1515---- 
    16  
    1716== Introduction == 
    18  
    19 The initial goal of defining level and type is to add restrictions to the use of the relationships specialization and classification as they are defined in ISO-15926-2:2003.  
     17The initial goal of defining level and type is to add restrictions to the use of the relationships specialization and classification as they are defined in ISO-15926-2:2003. 
    2018 
    2119In ISO 15926-2:2003 a [http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/specialization.html specialization] is defined as a relationship between two instances of the entity type `class`: 
     20 
    2221  ''A <specialization> is a <relationship> that indicates that all members of the subclass are members of the superclass.'' 
    2322{{{ 
     
    2625  superclass     :      class; 
    2726}}} 
    28 This definition is too weak as the following illustrates. The definition allows an instance of `class of class of individual` to be declared as a subclass of an instance of a `class of individual`, since both `class of class of individual` and `class of individual` are subtypes of `class`. [http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/class_of_class_of_individual.html class of class of individual] is defined in ISO 15926-2 as  
    29   ''A <class_of_class_of_individual> is a <class_of_class> whose members are instances of <class_of_individual>''  
    30 and [http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/class_of_individual.html class of individual] is defined as  
    31   ''A <class_of_individual> is a class whose members are instances of <possible_individual>''.  
    32 Declaring an instance of `class of class of individual` '''A''' as a subclass of an instance of a `class of individual` '''B''' would mean that all the members of '''A''' are also members of '''B''', but that entails that all members of '''A''' are instances of `possible individual` hence violating the definition of `class of class of individual`. 
     27 
     28This definition is too weak as the following example illustrates. The definition allows an instance of `class of class of individual` to be declared as a subclass of an instance of a `class of individual`, since both `class of class of individual` and `class of individual` are subtypes of `class`. [http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/class_of_class_of_individual.html class of class of individual] is defined in ISO 15926-2 as 
     29 
     30  ''A <class_of_class_of_individual> is a <class_of_class> whose members are instances of <class_of_individual>'' 
     31 
     32and [http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/class_of_individual.html class of individual] is defined as 
     33 
     34  ''A <class_of_individual> is a class whose members are instances of <possible_individual>''. 
     35 
     36Declaring an instance of `class of class of individual` '''A''' as a subclass of an instance of a `class of individual` '''B''' would mean that all the members of '''A''' are also members of '''B''', which entails that all members of '''A''' are also instances of `possible individual`. 
     37|| [[Image(A.gif)]] || [[Image(B.gif)]] || [[Image(AB.gif)]] || 
     38|| '''A''' is an instance of `class of class of individual`. All members of '''A''' are instances of `class of individual`. || '''B''' is an instance of `class of individual`. All members of '''B''' are instances of `possible individual`. || '''A''' is a subclass of ''B''. All members of '''A''' are also instances of `possible individual`.|| 
    3339 
    3440By adding restrictions to the use of relationships in ISO 15926 we can avoid such problems. The notions defined in this article may also be valuable for adding restrictions to other relationships than specialization and classification defined in ISO 15926-2. 
    3541 
    3642== Types and levels == 
    37  
    3843We want to be able to categorize the entity types defined in ISO 15926-2 into categories, categories which should be non-overlapping. We categorize along two axis. First we observe that a relationship is a different concept than an individual. We call this axis ''type''. 
    3944 
     
    6065 
    6166==== Intuitions ==== 
    62  
    63 Intuitively the set Type_Individual is the set containing  
     67Intuitively the set Type_Individual is the set containing 
     68 
    6469 * all individuals 
    6570 * all sets of individuals 
     
    6873 * and so on. 
    6974 
    70 The set Type_Relationship is the set containing  
     75The set Type_Relationship is the set containing 
     76 
    7177 * all relationships between individuals 
    7278 * all sets of relationships between individuals 
     
    8086 * and so on. 
    8187 
    82  
    8388=== Definition in OWL === 
    84  
    8589{{{ 
    8690Class: Type_Individual 
     
    112116        Level_2 
    113117}}} 
    114  
    115   Note: Defining all levels as mutually disjoint is not correct according to the set theoretical definition above; the empty set is a member of all sets. A possible solution is to define a "ISO 15926 notion" of level. In ISO 15926-2 the empty set is an instance of the entity type [http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/class.html class].  
     118  Note: Defining all levels as mutually disjoint is not correct according to the set theoretical definition above; the empty set is a member of all sets. A possible solution is to define a "ISO 15926 notion" of level. In ISO 15926-2 the empty set is an instance of the entity type [http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/class.html class]. 
    116119 
    117120== Restricting ISO 15926-2 entity types to levels == 
    118  
    119121This section places most entity types defined in ISO 15926 on the level axis, in either Level 0, Level 1, Level 2 or Level 3. 
    120122 
     
    203205}}} 
    204206== Adding restrictions to relations using levels == 
    205  
    206 This section adds restrictions to relations defined in ISO 15926 using levels.  
     207This section adds restrictions to relations defined in ISO 15926 using levels. 
    207208 
    208209=== Specialization === 
    209210[http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/specialization.html Specialization] is in ISO 15926-2 defined as: 
     211 
    210212  ''A <specialization> is a <relationship> that indicates that all members of the subclass are members of the superclass. <specialization> is transitive. '' 
    211213{{{ 
     
    220222 
    221223OWL listing: 
     224 
    222225{{{ 
    223226Class: part2:Specialization 
     
    241244}}} 
    242245=== Classification === 
    243  
    244246[http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema/lexical/classification.html Classification] is defined as 
     247 
    245248  ''A <classification> is type of <relationship> that indicates that the classified <thing> is a member of the classifier <class>. <classification> is not transitive.'' 
    246249{{{ 
     
    252255 
    253256OWL listing: 
     257 
    254258{{{ 
    255259Class: part2:Classification 
     
    264268       and part2:hasClassifier only Level_3 
    265269}}} 
    266  
    267  
    268270---- 
    269  
    270271[[ViewTopic(ISO 15926 in OWL, adding restrictions to relationships)]] 
Home
About PCA
Reference Data Services
Projects
Workgroups