|
Difference between
version 40
and
version 39:
| Line 11 was replaced by line 11 |
| - Every concept in the eco-ontology extends the concept __EcoOntThing__. The name "thing" is often used informally in ontologies to denote the set of all things. Instead of "thing", we use the term __object__, but we retain the convention of using the term "thing" to name the most general concept. Every object in the eco-ontology is thus considered an ecological ontology "thing". Figure 1 below shows the definition of EcoOntThing. As shown, objects can be named using the __hasName__ attribute. Object names are optional (denoted by the '0' in the cardinality restriction '0..*'), and an object may have more than one name (denoted by the '*' in the cardinality restriction '0..*'). |
| + Every concept in the eco-ontology extends the concept __EcoOntThing__. The name "thing" is often used informally in ontologies to denote the set of all things. Instead of "thing", we use the term __object__, but we retain the convention of using the term "thing" to name generic concepts. Figure 1 below defines EcoOntThing. As shown, objects can be named using the __hasName__ attribute. Object names are optional (denoted by the '0' in the cardinality restriction '0..*'), and an object may have more than one name (denoted by the '*' in the cardinality restriction '0..*'). |
| Line 19 was replaced by line 19 |
| - Objects are often described in terms of their structural relationships. One of the most basic structural relationships is the connection between parts and wholes. These part-whole relationships treat one object as the "composite", containing zero or more other objects serving as the "parts". Figure 2 shows the basic constructs used in the core for representing parts and wholes. The concepts __Composite__ and __Part__ are defined as sub-concepts of EcoOntThing. And composites and parts are related through the __hasPart__ and __partOf__ relationships, respectively. |
| + Objects are often described in terms of their structural relationships. A basic structural relationship is the connection between parts and wholes in which one object serves as a "composite" that contains zero or more other objects serving as "parts". Figure 2 shows how the definition of parts and wholes in the core. The concepts __Composite__ and __Part__ are sub-concepts of EcoOntThing, which are related through the __hasPart__ and __partOf__ relationships. |
| Line 25 was replaced by line 25 |
| - As shown, the hasPart relationship relates a composite object to zero or more parts. Similarly, the partOf relationship relates a part object to its associated composite object. A part object can participate in zero or more composite objects (that is, a part can be shared between containers). |
| + The hasPart relationship relates a composite object to zero or more parts. Similarly, the partOf relationship relates a part object to its associated composite object. A part object can participate in zero or more composite objects (that is, a part can be shared between containers). The hasPart and partOf relationships are considered inverses. That is, if a composite c has a part p, denoted {{hasPart(p, c}}, then p must also be a part of c, denoted {{partOf(p, c)}}. |
| Line 27 was replaced by line 27 |
| - The part-whole relationship of Figure 2 is defined to be transitive. If a container c contains a part p1, and part p1 is also a container containing a part p2, then c is said to also contain p2 by virtue of transitivity. We can represent this more formally by saying that if {{hasPart(c, p1)}} and {{hasPart(p1, p2)}} is true, then {{hasPart(c, p2)}} is also true. The inverse also holds, that is, if {{partOf(p2, p1)}} and {{partOf(p1, c)}} is true, then {{partOf(p2, c)}} is also true. |
| + The hasPart and partOf relationships are also transitive. That is, if a composite c contains a part p1, and part p1 is also a composite containing a part p2, then c also contains p2. More formally, if {{hasPart(c, p1)}} and {{hasPart(p1, p2)}} is true, then {{hasPart(c, p2)}} is also true. The inverse also holds, that is, if {{partOf(p2, p1)}} and {{partOf(p1, c)}} is true, then {{partOf(p2, c)}} is also true. |
| Line 29 was replaced by line 29 |
| - There are four distinct ways that part-whole relationships can be specialized within the core, shown in Figures 3 - 6. The first specialization, shown in Figure 3, describes the concept of inseparable parts. As shown, all __InseparablePart__ objects are contained within at least one composite object, that is, the object will not exist separately from a collection. |
| + There are four distinct ways that part-whole relationships can be specialized within the core, shown in Figures 3 - 6. The first specialization, defined in Figure 3, allows parts to be inseparable. That is, all __InseparablePart__ objects are contained within at least one composite object -- the object will not exist separately from a collection. |
Back to Eco Ontology Manual Draft,
or to the Page History.
|
