| Lines 1-85 were replaced by line 1 |
| - !1 Introduction |
| - |
| - |
| - |
| - ;:''Comment: Introduction goes here. Introduce our basic vocabulary of concepts including: classes, relationships (i.e., so called owl:ObjectProperty or property definitions between concepts), attributes (owl:DatatypeProperties; property definitions between a concept and a datatype like string), objects, properties, and what we mean by package.'' |
| - |
| - |
| - |
| - !2 The Eco-Ontology Core |
| - |
| - |
| - |
| - This section describes the fundamental building blocks of the eco-ontology -- called the ''eco-ontology core'' (or just the ''core''). The core is represented as a single package, and all other ontologies defined within (or that extend) the eco-ontology are built from the core. The purpose of the core is to establish the set of basic semantic constructs that can be used to define more complex ecological concepts and relationships. |
| - |
| - |
| - |
| - !''Things'' |
| - |
| - |
| - |
| - Every concept in the eco-ontology extends the generic concept ''EcoOntThing''. The name "thing" is often informally used in ontologies to denote the set of all things. We use the term ''object'' instead of "thing", but we retain the convention of using "thing" to name generic concepts. Figure 1 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..*'. |
| - |
| - |
| - [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/seek/projects/kr-sms/docs/OntoManual/core1.png] |
| - \\__Fig. 1:__ Definition of EcoOntThing; the most general eco-ontology concept. |
| - |
| - |
| - |
| - !''Parts and Wholes'' |
| - |
| - |
| - |
| - 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'', containing zero or more other objects serving as ''parts''. Figure 2 shows how parts and wholes are defined in the core. The concepts ''Composite'' and ''Part'' are sub-concepts of EcoOntThing, and are related through the ''hasPart'' and ''partOf''' relationships. |
| - |
| - |
| - [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/seek/projects/kr-sms/docs/OntoManual/core2.png] |
| - \\__Fig. 2:__ Basic part-whole concepts and relationships. |
| - |
| - |
| - We denote a hasPart relationship between a composite object c and a part object p as {{hasPart(c, p)}}. And a partOf relationship between p and c as {{partOf(p, c)}}. Note that a part object can participate in zero or more composite objects -- thus, parts can be shared by composites. |
| - |
| - |
| - The hasPart and partOf relationships are inverse and transitive. The inverse relationship states that for every composite object c and part p, {{hasPart(c, p)}} if and only if {{partOf(p, c)}}. The transitive relationship states that for every composite object c and parts p1 and p2, if {{hasPart(c, p1)}} and {{hasPart(p1, p2)}} then {{hasPart(c, p2)}}. The inverse relationship also implies that if {{partOf(p1, c)}} and {{partOf(p2, p1)}} then {{partOf(p2, c)}}. |
| - |
| - |
| - There are four ways that part-whole relationships are specialized in the core, shown in Figures 3 - 6. The first specialization is shown in Figure 3 and defines inseparable parts, which are parts that are always contained within at least one composite -- that is, the part object does not exist separately from a collection. Inseparable parts are represented using the ''inseparablePartOf'' relationship and the concept ''InseparablePart''. As shown, the ''inseparablePartOf'' relationship is a sub-relationship (that is, specializes) the more general partOf relationship. |
| - |
| - |
| - [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/seek/projects/kr-sms/docs/OntoManual/core3.png] |
| - \\__Fig. 3:__ Inseparable parts. |
| - |
| - The second specialization is shown in Figure 4 and defines essential parts, which are parts that are required by a composite. In general, composite objects can contain a variety of different part types. For example, a car contains various parts including wheels, a chassis, bumpers, and so on. For cars, wheels are essential, whereas sunroofs are optional. Essential parts are defined using the ''hasEssentialPart'' relationship and the ''EssentialPart'' concept. |
| - |
| - |
| - [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/seek/projects/kr-sms/docs/OntoManual/core4.png] |
| - \\__Fig. 4:__ Essential parts. |
| - |
| - |
| - The third specialization is shown in Figure 5 and describes unique parts, which are one-of-a-kind parts of a composite. An example of a unique part is a chassis -- any one car can have at most one chassis. Unique parts are defined using the ''hasUniquePart'' relationship and the ''UniquePart'' concept. Note that a chassis is also an essential part for a car. In general, we permit part-whole specializations to be freely mixed. |
| - |
| - |
| - [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/seek/projects/kr-sms/docs/OntoManual/core5.png] |
| - \\__Fig. 5:__ Unique parts. |
| - |
| - |
| - The last specialization is shown in Figure 6 and defines unshareable parts, which are parts that can be within at most one composite. All car parts are unshareable. Unshareable parts are defined using the ''isUnshareablePartOf'' relationship and the 'UnshareablePart'' concept. |
| - |
| - |
| - [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/seek/projects/kr-sms/docs/OntoManual/core6.png] |
| - \\__Fig. 6:__ Unshareable parts. |
| - |
| - |
| - |
| - !''Observations and Measurements'' |
| - |
| - |
| - |
| - Like parts and wholes, measurements (as well as the more general notion of observations) are fundamental building blocks in the eco-ontology. As shown in Figure 8, we define __MeasurementConcept__ to highlight the special status of measurements in the core. In particular, MeasurementConcept is defined as an abstract concept (denoted by the italics type in the figure) that all other measurement definitions fall under. |
| - |
| - [http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/seek/projects/kr-sms/docs/OntoManual/core8a.png] |
| - \\__Fig. 7:__ Observations and observation collections. |
| - |
| - Observations (and therefore, measurements, which we describe further below) can be grouped into collections through the concept __ObservationCollection__. Observation collections can also be grouped into other collections. We use the abstract concept __ObservationCollectionPart__ to denote the objects that can act as parts in an observation collection object. As shown in Figure 8, we use the part-whole constructs to describe these relationships between observations and observation collections. Note that the cardinality restrictions are not shown because they are implied by the part-whole constructs used. |
| - |
| - An observation is a generalization of a measurement. Informally, we define an observation as an assertion of the existence of an entity or of the existence of some property of an entity. A measurement goes further by asserting a value for a property. To illustrate, consider the statement "I saw a tree frog". This statement refers to an observation, in which the existence of a tree frog was observed. The statement "I noticed the tree frog had spots" is also an observation in which the existence of the property "spots" was observed for a tree frog. We say that for this case, the observation asserts there is some value for the property "spots" that was observed, but the value was not provided. Finally, the statement "I noticed the tree frog had ten spots" is a measurement, in which the existence of the value ten is being asserted for the "spots" property of a tree frog. |
| + Coming Soon ... |
