Ontology Pattern
Jump to navigation
Jump to search
An Ontology Pattern is a Pattern of an Ontology.
- Context:
- It can be:
- an Ontology Design Pattern, that can aid an Ontology Design Task.
- an Ontology Correspondence Pattern, that can aid an Ontology Alignment Task.
- It can
- It can be:
- See: Factmodels.com.
References
2009
- (Scharffe, 2009) ⇒ Francois Scharffe. (2009). “Correspondence Patterns Representation." PhD Thesis.
- ABSTRACT: We introduce in this dissertation correspondence patterns as a novel way to model ontology alignments. Correspondence patterns are meant to provide reference templates helping to model ontology alignments, like design patterns in software engineering help to model software designs. We develop an ontology mediation framework positioning patterns at the top level of abstraction of an ontology alignment representation, and introduce an expressive ontology alignment language allowing to represent correspondence patterns. Based on this framework, we propose a correspondence pattern library containing a number of patterns solving classical ontology mismatches, and modeled using the expressive alignment language.
- 2.3 Ontology Representation Framework. … A correspondence pattern is at the top level of abstraction of the ontology alignment representation stack. Correspondence patterns are essentially correspondences and sets of correspondences with generic entities. They act as templates to help finding more precise correspondences than simply relating one entity to another. Correspondence patterns are meant to be used in graphical user interfaces, in order to refine simple correspondences discovered by matching algorithms.
- http://ontologydesignpatterns.org/wiki/WOP2009:Main
- As interest in the Semantic Web increases and technologies for realizing the semantic web become more mature, the need for high-quality and reusable semantic web ontologies increases. To address the quality and reusability issues, different types of Ontology Design Patterns (ODPs) have emerged. Patterns can supply ontology designers with several kinds of benefits, including a direct link to requirements, reuse, guidance, and better communication. ODPs are well on their way to providing those benefits. ODPs have been proposed by the W3C and are currently being collected in various repositories, such as the catalogue maintained by the University of Manchester and the ODP portal at ontologydesignpatterns.org. However, pattern catalogues are still small and do not cover all types of patterns and all domains. Semantic Web applications could also benefit from additional types of patterns, such as knowledge patterns and specialized software patterns for semantic applications. In addition, to achieve communication benefits, patterns need to be shared by a community in order to provide a common language for discussing and understanding modeling problems. ...
- Reuse has been an important research subject in ontology engineering for many years, and this is also true for the semantic web community. Patterns are an approach to knowledge reuse that has proved feasible and very profitable in many other areas such as software engineering and data modeling.
Topics * Good practices of ontology design * Good practices for Linked Data and related applications * Good practices for hybridization of semantic web and NLP techniques * Good Practices and Patterns of semantic social networks, semantic wikis, semantic blogs * Good Practices of Semantic Web in general * Ontology Design Patterns and Linked Data * Ontology Patterns and Microformats * Patterns for using different vocabularies together e.g. FOAF, SIOC, DC, etc. * Web semantics from a pattern perspective * Software patterns for semantic web applications * Interaction patterns and the Semantic Web * Pattern-based methodologies for Semantic Web ontologies and software engineering * Application Profiles * Domain specific applications based on patterns and successful stories * Ontology design patterns (ODPs) for specific knowledge domains e.g. multimedia, fishery and agriculture, user profiling, business modeling, etc. * Collaboration patterns in ontology design and engineering * Correspondence patterns for ontology matching and integration * Lexico-syntactic patterns * Reasoning patterns (workflows made of reasoning steps for addressing specific goals) * Processes and services - process patterns * Re-engineering patterns for conceptual models, folksonomies, lexicons, thesauri * Problem solving methods and patterns * Tools support for pattern-based knowledge engineering * Pattern-based ontology evaluation and selection * Automatic ontology construction (ontology learning) based on patterns * Contextual reasoning and patterns as context * Knowledge patterns and knowledge re-engineering based on patterns * Pattern-based information extraction * Quality evaluation of patterns * Benefits of ontology patterns and knowledge patterns
2008
- (Clark et al., 2008) ⇒ Peter Clark, John Thompson, and Bruce Porter. (2008). “Knowledge Patterns.” In: Handbook of Ontologies.
- Summary: This Chapter describes a new technique, called “knowledge patterns", for helping construct axiom-rich, formal ontologies, based on identifying and explicitly representing recurring patterns of knowledge (theory schemata) in the ontology, and then stating how those patterns map onto domain-specific concepts in the ontology, and then stating how these patterns map onto domain-specific concepts in the ontology. From a modeling perspective, knowledge patterns provide an ...
- (Presutti et al., 2008) ⇒ Valentina Presutti, and Aldo Gangemi. (2008). “Content Ontology Design Patterns as Practical Building Blocks for Web Ontologies.” In: Proceedings of ER Conference (ER 2008)
- (Egaña et al., 2008) ⇒ Mikel Egaña, Alan Rector, Robert Stevens, and Erick Antezana. (2008). “Applying Ontology Design Patterns in bio-ontologies.” (EKAW 2008).
2006
- (Noy & Rector, 2006) ⇒ Natasha Noy and Alan Rector. (2006). “Defining N-ary Relations on the Semantic Web." W3C Working Group Note 12 April 2006 (W3C).
2005
- (Gangemi, 2005) ⇒ Aldo Gangemi. (2005). “Ontology Design Patterns for Semantic Web Content.” In: Proceedings of the International Semantic Web Conference (ISWC 2005). doi:10.1007/11574620.
- ABSTRACT: The paper presents a framework for introducing design patterns that facilitate or improve the techniques used during ontology lifecycle. Some distinctions are drawn between kinds of ontology design patterns. Some content-oriented patterns are presented in order to illustrate their utility at different degrees of abstraction, and how they can be specialized or composed. The proposed framework and the initial set of patterns are designed in order to function as a pipeline connecting domain modelling, user requirements, and ontology-driven tasks/queries to be executed.
- (Noy et al., 2005) ⇒ Natasha Noy, Michael Uschold, and Chris Welty. (2005). “Representing Classes As Property Values on the Semantic Web." W3C.
- This document addresses the issue of using classes as property values in OWL and RDF Schema. It is often convenient to put a class (e.g., Animal) as a property value (e.g., topic or book subject) when building an ontology. While OWL Full and RDF Schema do not put any restriction on using classes as property values, in OWL DL and OWL Lite most properties cannot have classes as their values. We illustrate the direct approach for representing classes as property values in OWL-Full and RDF Schema. We present various alternative mechanisms for representing the required information in OWL DL and OWL Lite. For each approach, we discuss various considerations that the users should keep in mind when choosing the best approach for their purposes.
- (Rector, 2005) ⇒ Alan Rector. (2005). “Representing Specified Values in OWL: 'value partitions' and 'value sets'."
- ABSTRACT: Modelling various descriptive "features" (also known variously as "qualities", "attributes" or "modifiers") is a frequent requirement when creating ontologies. For example: "size" may describe persons or other physical objects and be constrained to take the values "small", "medium" or "large"; rank may describe military officers and restricted to a specific list of values depending on the military organisation. In OWL such descriptive features are modelled as properties whose range specifies the constraints on the values that the property can take on. This document describes two methods to represent such features and their specified values: 1) as partitions of classes; and 2) as enumerations of individuals. It does not discuss the use of datatypes to represent lists of values.
- Eva Blomqvist, and Kurt Sandkuhl. (2005). “Patterns in Ontology Engineering: Classification of ontology patterns. In: ICEIS (3).