DavidCarral (Talk | contribs) |
DavidCarral (Talk | contribs) |
||
| Line 9: | Line 9: | ||
|Author=David Carral, Pascal Hitzler, Hilmar Lapp, Sebastian Rudolph | |Author=David Carral, Pascal Hitzler, Hilmar Lapp, Sebastian Rudolph | ||
}} | }} | ||
| − | {{Logical OP Description Template}} | + | {{Logical OP Description Template |
| + | |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.'' | ||
| + | |||
| + | }} | ||
{{Logical OP Example Template}} | {{Logical OP Example Template}} | ||
{{Logical OP Reference Template}} | {{Logical OP Reference Template}} | ||
|
Last modified date is: 2017-07-16 |
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 | |
| Used in combination with | |
| Test |
No scenario is added to this Content OP.
This revision (revision ID 13236) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
