|
Difference between
version 46
and
version 45:
| Line 25 was replaced by line 25 |
| - 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 by composites). 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)}}. |
| + 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 by composites). The hasPart and partOf relationships are inverses. 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 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. |
| + The hasPart and partOf relationships are also transitive. 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. |
Back to Eco Ontology Manual Draft,
or to the Page History.
|
