Catalogue:Main
From Odp
This area is dedicated to the ODP official Catalogue of Content Ontology Design Patterns.
Each Content OP is presented as a catalogue entry and has passed a quality check step before its publishing.
The quality check is performed by one or more members of the Quality Committee who are in charge of evaluating each Content OP against a set of evaluation principles.
Below you can find the list of Catalogue entries. You might also want to browse additional Content OPs in the Content OP Proposals area.
Content Ontology Design Patterns Catalogue (grouped by domain)
| Name | HasIntent | Domain |
|---|---|---|
| Course | The aim of this content ontology design patterns-Course Pattern- is to model the core attributes of a course and the basic relationships of the course in an educational institution. | |
| AOS AGROVOC Concept Server fundation ontology model | Act as a basic model for Agricultural Related Ontologies, in particular for the AGROVOC Concept Server. The model clearly identify concepts (domain concepts) from terms (which are represented as instances). Both concepts and terms have specific relationships connecting them. | |
| HasPest | Define the relationship between a concept and an organism which has characteristics that are regarded by other organisms as injurious or unwanted. Generally causing damages. | |
| ComputationalEnvironment | The pattern is intended to support comparison and reproducibility of computational analyses. | |
| Born Digital Archives | The pattern intends to model the domain of born digital archives. This pattern has been developed by MKLab at CERTH/ITI for the PERICLES FP7 project. | |
| Biological Entities | To represent biological species and relations between them. | |
| GO Top | To represent types of gene-related entities and their parts. | |
| EEP | To represent executions made by executors that implement procedures. Executions are events like observations or actuations. Executors are systems like sensors or actuators that produce executions. Executors implement procedures to carry out their goals. Executions and executors are taken over features of interest and their intrinsic properties/qualities. | |
| AffectedBy | To represent properties/qualities that may affect the status of a feature of interest. | |
| Invoice | To represent the core attributes of an invoice | |
| PharmaInnova | To describe invoices with the PharmaInnova Model. This schema can be applied to other invoice models. | |
| HistoricalMap | The ontology's intent is to describe a historical map and its attributes. | |
| SpatioTemporalExtent | This pattern models a spatiotemporal extent, i.e., a combination of spatial and temporal extent as a set of generalized trajectories which cannot have temporal overlap. This pattern reuses semantic trajectory pattern as component. | |
| TransportPattern | The goal of the pattern is to facilitate modelling the movement of mass or energy from one location to another, based on a common persistent frame of reference. | |
| NewsReportingEvent | The pattern can be used for modelling situations in which we are not certain that a particular actual event has the properties which were described in a news message. We want to define the properties of an actual event which were reported (time, place, actors, subevents, cause, effect etc.), but not to treat them as universal, verified knowledge. The pattern also allows to define who is responsible for a particular description of an event and how this description is dealt with. | |
| ReportingNewsEvent | The pattern can be used for modelling situations in which we are not certain that a particular actual event has the properties which were described in a news message. We want to define the properties of an actual event which were reported (time, place, actors, subevents, cause, effect etc.), but not to treat them as universal, verified knowledge. The pattern also allows to define who is responsible for a particular description of an event and how this description is dealt with. | |
| ActivitySpecification | This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time. This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL. |
|
| EventProcessing | To model event objects (in the context of complex event processing), their attributes, and their relations actual events, and sensor readings producing the events. Different types of event objects, such as complex, composite, and simple events are modelled, preoperties for expressing relations between event objects, such as constituency and componency are expressed, and attributes of event objects, such as timestamps and other data values. This pattern is aligned both to the SSN (Semantic Sensor Network) ontology, and the Event-F model, which in turn both use DUL as an upper layer. | |
| ExplanationODP | Describing the process and components of an explanation in different disciplines. | |
| GearWaterArea | to represent gear types in terms of the water areas where they can be employed to collect aquatic resources | |
| CatchRecord | To represent the catch records from time series FIGIS application, which contain temporally-indexed aggregated information about aquatic species cacthing. | |
| Metonymy-species-commodity | To establish a link between species exploitation and consumer goods.
This pattern has been observed in WordNet, where words share the following metonymic or regular polysemic patterns: animal-food, animal-commodity and life form-consumer goods. This is why the pattern has been named "metonymy". Regular polysemy is a metonymic phenomenon in that it describes the substitution of one word sense by another related sense. It establishes a semantic relation between two concepts that are associated with the same word. Regular polysemy is regular in that it captures conventionalized and therefore recurrent processes of sense extension, which have been captured in lexical resources such as dictionaries and thesauri. |
|
| ResourceAbundanceObservation | The intent of the pattern is to be able to represent observations of aquatic resources, where the observations have been made a certain year and has certain other parameters. | |
| AquaticResourceObservation | To represent the aquatic observation data extracted from factsheet application. An aquatic observation refers to a specific year, is about an aquatic resource, and is situated in a given habitat, in which the aquatic species from the resource live. Observations can have a reporting year that is different from the observation time. | |
| VesselSpecies | to provide a direct relation between aquatic species and vessels that are able to catch them, regardless of the fishing gear used. | |
| ResourceExploitationObservation | The intent of the pattern is to be able to represent observations of aquatic resources, where the observations have been made a certain year and has certain other parameters. | |
| ClimaticZone | The intent of the pattern is to be able to represent climatic zones for aquatic resources. | |
| AquaticResources | To represent aquatic resources or stocks as composed of aquatic organisms from one or more species, and living in a water area. | |
| GearVessel | to represent types of fishing gear with regard to the types of vessel they can be mounted on | |
| ChessGame | To model a flexible schema to allow exposing chess games as linked data. | |
| Object with states | An object can have different states for which different restrictions apply. The goal of the pattern is to allow modelling the different states of an object and the restrictions on such object for its different states. | |
| Classification | To represent the relations between concepts (roles, task, parameters) and entities (person, events, values), which concepts can be assigned to. To formalize the application (e.g. tagging) of informal knowledge organization systems such as lexica, thesauri, subject directories, folksonomies, etc., where concepts are first-order elements. | |
| Collection | To represent domain (not set theory) membership. | |
| RecurrentSituationSeries | To represent recurrent situation series as situations and collections of consecutive situations, with a regular time period between situations and unifying factors. | |
| HazardousSituation | To model hazardous situations and their associated hazardous events with events' participating objects and the hazards the objects are exposed to with the exposure value. | |
| TimeIndexedSituation | To represent time indexed situations. | |
| ParticipantRole | To represent participants in events holding specific roles in that particular event. | |
| Literal Reification | This pattern promotes any literal as “first class object” in OWL by reifying it as a proper individual of the class litre:Literal. | |
| Transition | To represent basic knowledge about transitions (events, states, processes, objects). | |
| Situation | To represent contexts or situations, and the things that are contextualized. | |
| Region | To represent and reason on values of attributes of things, by explicitly talking about the dimensions ("regions") of the attributes, which include those values. | |
| Trajectory | The pattern provides a model of trajectory, which is understood as a sequence of spatiotemporal points. The model generalizing the Semantic Trajectory pattern from [Hu, et al., COSIT 2013] by employing the notion of place, instead of location/geo-coordinate, to represent the spatial extent of the trajectory. This pattern is suitable for a variety of trajectory datasets and easily extendible by by aligning to or matching with existing trajectory ontologies, foundational ontologies, or other domain specific vocabularies. | |
| Bag | To model bags of items (elements). The Bag is characterized by a collection that can have multiple copies of each object. | |
| Observation | The intent of this pattern is to represent observations of things, under a set of parameters. Common parameters may be the time and place of the observation, but may be any feature that is observed concerning the specific thing being observed. | |
| Template Instance | The Template Instance pattern proposes a way of reducing the number of reified instances and the related property assertion axioms in an ontology, especially for the cases in which the reified relations are identical for multiple entities. | |
| Description | To formally represent a conceptualization or a descriptive context. | |
| Parameter | To represent parameters to be used for a certain concept. | |
| Participation | To represent participation of an object in an event. | |
| Sequence | To represent sequence schemas. It defines the notion of transitive and intransitive precedence and their inverses. It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc. | |
| Policy | The pattern intends to model policies, their characteristics and their associated entities, such as processes and agents. This pattern has been developed by MKLab at CERTH/ITI and the University of Liverpool for the PERICLES FP7 project. | |
| Types of entities | To identify and categorize the most general types of things in the domain of discourse. | |
| Topic | To represent topics and their relations. | |
| Co-participation | To represent two objects that both participate in a same event. | |
| CriterionSetter | The purpose of this pattern is to provide a broader context for criteria modeling. Possible specializations could introduce new kinds of criteria setters representing criteria in detailed contexts (for example: a pattern for describing the success/failure condition for some actions). Possible criteria setters may include requirements, recommendations, constraints etc. | |
| Complaint Design Pattern | To represent core constituents found commonly in complaints across domains. | |
| Objectrole | To represents objects and the roles they play. | |
| Tagging | To represent a tagging situation, in which someone uses a term, from a list of a folksonomy, to tag something (or the content of something). We might also want to represent the time and the polarity of the tagging. | |
| Food Recipe Ingredient Substitution Ontology Design Pattern | To model substitutes for ingredients in food recipes. Essential aspects of modelling substitutes are their quantity in a recipe, the constraints and the qualitative and quantitative conditions for the substitutions, and other nutrition values, e.g. containing a number of calories or technological effects, and substitution objectives. The pattern should allow to represent different types of food substitutes in recipes, and recipe process, and overall notion of food substitution. | |
| ReportingEvent | The intent of the pattern is to allow for modelling situations in which the knowledge about an event cannot be treated as certain. It is particularly useful for cases in which two or more agents provide different, contradictory information about the same event. It can be also used for modelling situation in which a single agent provided contradictory information about the same event in different points in time. In general the pattern allows for stating different circumstances of an act of the information provision. | |
| Nary Participation | To represent events with their participants, time, space, etc. | |
| Computer System | The pattern intends to model computer systems based on a hardware/software approach. This pattern has been developed by MKLab at CERTH/ITI and Tate for the PERICLES FP7 project. | |
| Criterion | The purpose of this pattern is to provide a basis for criteria modeling. For more advanced use see the 'criterion setter' pattern that enables describing entities that define criteria (such as requirements, constraints etc.). | |
| Time indexed person role | To represent classification of things at a certain time. | |
| Place | To talk about places of things. | |
| IntensionExtension | To represent the meaning of an information object: the concepts it expresses, the things it is about. | |
| EventCore | The purpose of this pattern is to provide a minimalistic model of event where it is not always possible to separate its spatial and the temporal aspects, thus can model events that move or possess discontinuous temporal extent. Events according to this model has at least one participant, attached via a participant-role, and may have additional descriptive information through its information object. | |
| AlgorithmImplementationExecution | To model algorithm specifications, their implementations and executions, together with parameters of implementations, settings of the parameters for the execution, and inputs the execution consumes (e.g., data) and outputs the execution produces (e.g., models, reports). | |
| Time indexed participation | To represent participants in events at some time,To represent participants in parts of events. | |
| Map Legend Ontology | Map legends are keys to the understanding of symbols used on maps. Without such legends and the knowledge to interpret them, maps are reduced to mere pictures.From an information retrieval perspective, facts such as that a certain map contains transportation features organized in a hierarchy of highways, streets, trails, and so forth, remain hidden and therefore can neither be used by machines nor humans to enable a richer search for map contents. | |
| Gesture Interaction | The Gesture Interaction Pattern aims to model the pose and movement of human body that are used to interact with devices (particularly with device affordances). This helps to describe a human gesture with its relationship between certain device affordances, related body parts and the temporal components associated with those. This might be helpful in creating user specific gesture profiles. This ontology pattern is geared at mapping the ubiquitousness in gesture vocabularies by linking them appropriately and does not enforce designers and manufacturers to follow a standard. | |
| ExperimentalParadigmData | to provide a minimal pattern for the integration and exploration of data from heterogeneous experimental paradigms in the biomedical domain | |
| Spatial Graph Adapter (SGA) | Link to OWL File: https://raw.githubusercontent.com/HollyFerguson/Spatial-Graph-Adapter-Pattern/master/SGA_Protege_OWL.owl
PDF of SGA Pattern Image: Image:USOcore3.pdf To answer the modern, interdisciplinary questions asked within the Building domain, industry tools and data standards need to become far more interoperable in order to be able to provide a full and accurate set of analysis to engineers and designers. To provide this full picture from which to make decisions, we needed a way to resolve the spatial data that tools provide in order to synthesize it together. In addition to missing, incorrect, and inconsistent information, there is also the challenge of not being able to use existing spatial patterns to capture the full granularity or specificity of the geospatial descriptions required to capture full and dynamic geometric contexts. The Spatial Graph Adapter (SGA) pattern provides us a way to extend the simple identification of geometries and simultaneously assign further descriptions and self-context as well as contextual and relational references to other spatial objects in or surrounding the original entity. For example, not only can we use existing notions say that one surface is adjacent to another, but we have a way to say exactly what type of adjacency and to what extent it is adjacent (more examples in accompanying paper). The SGA has also been implemented for several building industry schemas and our further research is in bringing this and other patterns into full use in a Linked Data Platform (ongoing). |
|
| Experience & Observation | to represent the epistemological "missing link" between a cognitive activity, e.g. the interaction with a cultural object, and any evidence of the effects this activity has on the individuals that are engaged with it; what can collectively be considered as an experience. | |
| Actuation-Actuator-Effect | This ODP intents to model the relationship between an Actuator and the Effect it has on its environment through Actuations. It structures an Actuator ontology : http://www.irit.fr/recherches/MELODI/ontologies/SAN.owl | |
| FIEST-IoT | See paper R. Agarwal, D. Fernandez, T. Elsaleh, A. Gyrard, J. Lanza, L. Sanchez, N. Georgantas, V. Issarny, "Unified IoT Ontology to Enable Interoperability and Federation of Testbeds", 3rd IEEE World Forum on IoT, pp. 70-75, Reston, USA, 12-14 December 2016. DOI: 10.1109/WF-IoT.2016.7845470, IEEE, HAL | |
| ConceptTerms | This CP allows designers to represent jointly conceptual and linguistic part of a vocabulary. The pattern purpose is not to encompass all linguistic complexity as Linginfo or LMF does, but to describe linguistic information in more details than SKOS which names concept whith simple labels. | |
| LicenseLinkedDataResources | To provide a pattern for expressing rights on Linked Data Resources, understood as RDF triples, datasets or mappings.
These rights include intellectual property rights, database rights and the right of access, which can be limited by personal data protection laws and others. Rights expressions may assert, waive and license the rights, either conditionally or inconditionally, either to the public or to agents in particular. |
|
| AgentRole | To represent agents and the roles they play. | |
| Material Transformation | To contextualize the transformation process from raw components and the required equipment to a final manufactured artifact. | |
| MaterialsProperty | To capture the provenance an assertion about a material's properties as well as capture the particulars of the property itself. | |
| DigitalVideo | The pattern intends to model digital video files, their components and other associated entities, such as codecs and containers. This pattern has been developed by MKLab at CERTH/ITI for the PERICLES FP7 project. | |
| Musicalobject | This content ODP models the acoustic features of a music note played in a performance. | |
| TaskExecution | To represent actions through which tasks are executed. | |
| CommunicationEvent | To model communication events, such as phone calls, e-mails and meetings, their involved parties and the roles and relations of the parties in the context of the communication events. | |
| Role task | To represent the assignment of tasks to roles | |
| CollectionEntity | To represent collections, and their entities, i.e. to represent membership. | |
| RelativeRelationship | For dynamically conceptualizing, establishing, tracking, and updating relative relationships and dependencies between entities (real or representational) of a physical, temporal, and/or importance scope. | |
| PartOf | To represents entities and their parts. | |
| Componency | To represent (non-transitively) that objects either are proper parts of other objects, or have proper parts. | |
| ConceptGroup | This CP allows designers to represent concept group defined by intention (all concepts satisfying group membership condition) or by extension (all concepts referring a group). | |
| Constituency | To represent the constituents of a layered structure. | |
| TimeIndexedPartOf | To represent objects that have temporary parts. | |
| SimpleOrAggregated | The goal of this pattern is to represent objects that can be simple or aggregated (that is, several objects gathered in another object acting as a whole). The main difference between the aggregation relation and other mereological relationships (such as part-of or componency) is that the aggregated object and its aggregated members should belong to the same concept. For example, a turbine is part of an engine, whereas an aggregated provider is formed by providers. | |
| DetectorFinalState | This pattern represent schematic model for high-energy physics experiment data. | |
| Action | The purpose of the pattern is to model actions that are proposed, planned, and performed or abandoned, together with their status and durations in time. | |
| Information realization | To represent information objects and their physical realization. | |
| Smart City Strategy Design | This modular ODP is used for strategies design to transform a city to a smart one. | |
| City Resident Pattern | This file defines an ontology design pattern for City "Resident.” Why is the development a Resident pattern important for the development of a city data on-tology? In the PolisGnosis project (Fox, 2017), where ontologies have been developed for measuring city performance across the 17 themes defined in ISO37120:2104 (e.g., Education, Public Safety, Health, Water & Sanitation), one of the concepts that recurs across themes is “(city) Resident”. The provisioning of city services is often contingent upon whether the person is a resident of the city. Whether it is access to swimming lessons provided by Parks and Recreation, or affordable housing provided by Shelters and Housing, many are contingent upon satisfying the residency requirement. This ontology pattern make it possible to define the semantics of residency for a city, and use the definition to automate the classification of a person as a resident or not of a city. | |
| OOPMetrics | To represent software metrics especially for the purpose of detecting design-flaws in software systems based on these metrics. This is useful for re-engineering the software system., De a reprezenta metricile soft in special in scopul detectarii defectelor de proiectare din sistemele soft pe baza acestor metrici. Acest lucru este folositor pentru reingineria sistemului soft. | |
| PeriodicInterval | The goal of this pattern is to represent non-convex intervals where the duration of each internal interval and the duration of the gaps between intervals are constant. These intervals are called periodic intervals within the context of this pattern. | |
| TimePeriod | To represent time periods between events. | |
| TimeInterval | To represent time intervals. | |
| Disposition | This pattern allow the representation of non-probabilistic dispositions with unique triggering and realization process types. | |
| GeoInsight | The goal of the pattern is to model the when, what, who, how and scope of insight capture during an interaction session with a geovisualization. | |
| An Ontology Design Pattern for Activity Reasoning | To incorporate the general two perspectives of activities: a workflow perspective, which are often observed in planning-related applications, and a spatiotemporal perspective, which are often found in geographic activity analysis. | |
| Reaction | To model dynamic situations, tracking agents and actions they produce, events that are results of some action(s), and consequences as new actions, i.e. reactions |
