DavidCarral (Talk | contribs) |
DavidCarral (Talk | contribs) |
||
| Line 13: | Line 13: | ||
}} | }} | ||
{{Logical OP Example Template}} | {{Logical OP Example Template}} | ||
| − | {{Logical OP Reference Template}} | + | {{Logical OP Reference Template |
| + | |RelatedTo=http://ontologydesignpatterns.org/wiki/Submissions:Tree_Pattern | ||
| + | |InCombination=http://ontologydesignpatterns.org/wiki/Submissions:Tree_Pattern | ||
| + | }} | ||
{{Additional information header}} | {{Additional information header}} | ||
Diagram
| Name | List |
|---|---|
| Also known as | |
| Author(s) | David Carral, Pascal Hitzler, Hilmar Lapp, Sebastian Rudolph |
| SubmittedBy | David Carral |
| Motivation | The list pattern just cited provides basic building blocks for a simple tree pattern. However, we opt to change the names of the properties: It seems to be more appropriate to use "hasChild" and "hasDescendant" rather than "directlyPrecedes" and "precedes, and to use "hasParent" and "hasAncestor"' rather than "directlyFollows" and "follows." |
|---|---|
| Aim | |
| Solution description | |
| Elements | |
| Implementation | |
| Reusable component | |
| Component type |
| Problem example | |
|---|---|
| Pattern solution example | |
| Consequences |
| Origin | |
|---|---|
| Known use | |
| Reference | |
| Related ODP | http://ontologydesignpatterns.org/wiki/Submissions:Tree_Pattern |
| Used in combination with | http://ontologydesignpatterns.org/wiki/Submissions:Tree_Pattern |
| Test |
No scenario is added to this Content OP.
This revision (revision ID 13242) takes in account the reviews: none
Other info at evaluation tab