Category:ArchitecturalOP
From Odp
(Difference between revisions)
(New page: {{Definition |Architectural Ontology Design Patterns (Architectural OPs) |A }}) |
|||
| Line 1: | Line 1: | ||
{{Definition | {{Definition | ||
|Architectural Ontology Design Patterns (Architectural OPs) | |Architectural Ontology Design Patterns (Architectural OPs) | ||
| - | | | + | |Architectural ODPs affect the overall shape of the ontology: their aim is to constrain ‘how the ontology should look like’. |
}} | }} | ||
| + | |||
| + | |||
| + | == Description == | ||
| + | Architectural ODPs affect the overall shape of the ontology: their aim is to constrain ‘how the ontology should look like’. Architectural ODPs emerged as design choices motivated by specific needs, e.g. computational complexity constraints. They are useful as reference documentation for those initially approaching the design of an ontology. | ||
Revision as of 09:38, 15 June 2009
Architectural Ontology Design Patterns (Architectural OPs)
Architectural ODPs affect the overall shape of the ontology: their aim is to constrain ‘how the ontology should look like’.
Description
Architectural ODPs affect the overall shape of the ontology: their aim is to constrain ‘how the ontology should look like’. Architectural ODPs emerged as design choices motivated by specific needs, e.g. computational complexity constraints. They are useful as reference documentation for those initially approaching the design of an ontology.
