Difference between revisions of "HasComponent"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
{{Supplementary Figures | {{Supplementary Figures | ||
|Figure Row={{Figure Row | |Figure Row={{Figure Row | ||
| − | |Figure=Part1.png | + | |Figure=Part1.png |
|Caption=Figure 1: Example use of the Parthood Ontology. | |Caption=Figure 1: Example use of the Parthood Ontology. | ||
}} | }} | ||
}} | }} | ||
Latest revision as of 21:59, 3 July 2021
Pattern
This property has been associated with the following pattern:
Subproperty Of
Definition
An English description of the definition (what distinguishes this sense of the term?).
The hasComponent property specifies a part-whole relationship between objects where the part is defined based on actual boundaries. The parts are often also defined according to distinct functions. For example, a car has a component called trunk.
Required by Use Case(s)
(why is this specialized definition needed?)
CDM References
What other classes or properties reference this term?
Interface Specification References
This property has been associated with the following interface specification items:
Sources
Sources considered when developing the property.
Status
Proposed
Has SubObjectProperties
Annotations
| Annotation | Value |
|---|
Property Specification
| Characteristic | Value (if applicable) |
|---|---|
| owl:inverseOf | componentOf |
Supplementary Figures
| Figure | Caption |
|---|---|
| Figure 1: Example use of the Parthood Ontology. |
