Attaining Semantic Enterprise Interoperability Through Ontology Architectural Patterns

2017 ◽  
pp. 705-740 ◽  
Author(s):  
Rishi Kanth Saripalle ◽  
Steven A. Demurjian
Keyword(s):  
Software Design ◽  
Information Exchange ◽  
Design Patterns ◽  
Domain Knowledge ◽  
Domain Model ◽  
Enterprise Application ◽  
Architectural Patterns ◽  
Enterprise Interoperability ◽  
Modular Ontology ◽  
Semantic Ontology

Enterprise Interoperability Science Base (EISB) represents the wide range of interoperability techniques that allow the creation of a new enterprise application by utilizing technologies with varied data formats and different paradigms. Even if one is able to bridge across these formats and paradigms to interoperate a new application, one crucial consideration is the semantic interoperability to insure that similar data is reconciled that might be stored differently from a semantic perspective. In support of this requirement, usage of ontologies is gaining increasing attention as they capture shareable domain knowledge semantics. The design and deployment of an ontology for any system is very specific, created in isolation to suit the specific needs with limited reuse in the same domain. The broad proliferation of ontologies for different systems, which, while similar in content, are often semantically different, can significantly inhibit the information exchange across enterprise systems. This situation is attributed, in part, to a lack of a software-engineering-based approach for ontologies; an ontology is often designed and built using domain data, while software design involves abstract modeling concepts that promote abstraction, reusability, interoperability, etc. The intent in this chapter is to define ontologies by leveraging software design pattern concepts to more effectively design ontologies. To support this, the chapter proposes Ontology Architectural Patterns (OAPs), which are higher-level abstract reusable templates with well-defined structures and semantics to conceptualize modular ontology models at the domain model level. OAP borrows from software design patterns inheriting their key characteristics for supporting enterprise semantic ontology interoperability.

Attaining Semantic Enterprise Interoperability Through Ontology Architectural Patterns

2018 ◽  
pp. 335-369
Author(s):  
Rishi Kanth Saripalle ◽  
Steven A. Demurjian
Keyword(s):  
Software Design ◽  
Information Exchange ◽  
Design Patterns ◽  
Domain Knowledge ◽  
Domain Model ◽  
Enterprise Application ◽  
Architectural Patterns ◽  
Enterprise Interoperability ◽  
Modular Ontology ◽  
Semantic Ontology

Enterprise Interoperability Science Base (EISB) represents the wide range of interoperability techniques that allow the creation of a new enterprise application by utilizing technologies with varied data formats and different paradigms. Even if one is able to bridge across these formats and paradigms to interoperate a new application, one crucial consideration is the semantic interoperability to insure that similar data is reconciled that might be stored differently from a semantic perspective. In support of this requirement, usage of ontologies is gaining increasing attention as they capture shareable domain knowledge semantics. The design and deployment of an ontology for any system is very specific, created in isolation to suit the specific needs with limited reuse in the same domain. The broad proliferation of ontologies for different systems, which, while similar in content, are often semantically different, can significantly inhibit the information exchange across enterprise systems. This situation is attributed, in part, to a lack of a software-engineering-based approach for ontologies; an ontology is often designed and built using domain data, while software design involves abstract modeling concepts that promote abstraction, reusability, interoperability, etc. The intent in this chapter is to define ontologies by leveraging software design pattern concepts to more effectively design ontologies. To support this, the chapter proposes Ontology Architectural Patterns (OAPs), which are higher-level abstract reusable templates with well-defined structures and semantics to conceptualize modular ontology models at the domain model level. OAP borrows from software design patterns inheriting their key characteristics for supporting enterprise semantic ontology interoperability.

Attaining Semantic Enterprise Interoperability through Ontology Architectural Patterns

2014 ◽  
pp. 216-251 ◽  
Author(s):  
Rishi Kanth Saripalle ◽  
Steven A. Demurjian
Keyword(s):  
Software Design ◽  
Information Exchange ◽  
Design Patterns ◽  
Domain Knowledge ◽  
Domain Model ◽  
Enterprise Application ◽  
Architectural Patterns ◽  
Enterprise Interoperability ◽  
Modular Ontology ◽  
Semantic Ontology

Enterprise Interoperability Science Base (EISB) represents the wide range of interoperability techniques that allow the creation of a new enterprise application by utilizing technologies with varied data formats and different paradigms. Even if one is able to bridge across these formats and paradigms to interoperate a new application, one crucial consideration is the semantic interoperability to insure that similar data is reconciled that might be stored differently from a semantic perspective. In support of this requirement, usage of ontologies is gaining increasing attention as they capture shareable domain knowledge semantics. The design and deployment of an ontology for any system is very specific, created in isolation to suit the specific needs with limited reuse in the same domain. The broad proliferation of ontologies for different systems, which, while similar in content, are often semantically different, can significantly inhibit the information exchange across enterprise systems. This situation is attributed, in part, to a lack of a software-engineering-based approach for ontologies; an ontology is often designed and built using domain data, while software design involves abstract modeling concepts that promote abstraction, reusability, interoperability, etc. The intent in this chapter is to define ontologies by leveraging software design pattern concepts to more effectively design ontologies. To support this, the chapter proposes Ontology Architectural Patterns (OAPs), which are higher-level abstract reusable templates with well-defined structures and semantics to conceptualize modular ontology models at the domain model level. OAP borrows from software design patterns inheriting their key characteristics for supporting enterprise semantic ontology interoperability.

A Study of Database Connection Pool

2014 ◽  
Vol 556-562 ◽  
pp. 5267-5270
Author(s):  
Tai Fa Zhang ◽  
Ya Jiang Zhang ◽  
Jun Yao
Keyword(s):  
Software Design ◽  
Design Patterns ◽  
Object Oriented ◽  
Access Time ◽  
Research Topics ◽  
Object Oriented Design ◽  
Java Language ◽  
Software Design Patterns ◽  
Connection Pool ◽  
Access Efficiency

Nowadays, object-oriented design is the trend of software design patterns, and the database connection pool is one of the important research topics. The paper firstly describes the basic principle of connection pool under traditional, tomcat and hibernate modes. Based on that, a new connection pool method is proposed, and these four methods are experimentally simulated in java language at last. The comparative analysis has verified that the presented connection pool owns the optimum access time and it can greatly improve the access efficiency of database.

Modular Ontology Modeling: A Tutorial

2020 ◽  
Author(s):  
Cogan Shimizu ◽  
Pascal Hitzler ◽  
Adila Krisnadhi
Keyword(s):  
Design Patterns ◽  
Ontology Engineering ◽  
Web Ontology Language ◽  
Ontology Language ◽  
Ontology Modeling ◽  
Ontology Design ◽  
Modular Ontology ◽  
The Web

We provide an in-depth example of modular ontology engineering with ontology design patterns. The style and content of this chapter is adapted from previous work and tutorials on Modular Ontology Modeling. It offers expanded steps and updated tool information. The tutorial is largely self-contained, but assumes that the reader is familiar with the Web Ontology Language OWL; however, we do briefly review some foundational concepts. By the end of the tutorial, we expect the reader to have an understanding of the underlying motivation and methodology for producing a modular ontology.

Iterative and Pattern-Based Development of Internal Domain-Specific Languages

2012 ◽  
pp. 132-155
Author(s):  
Sebastian Günther
Keyword(s):  
Design Patterns ◽  
Domain Knowledge ◽  
Special Kind ◽  
Language Implementation ◽  
Domain Specific ◽  
Iterative Development ◽  
Essential Properties ◽  
Familiar Environment ◽  
Independent Design ◽  
Internal Domain

Internal DSLs are a special kind of DSLs that use an existing programming language as their host. In this chapter, the author explains an iterative development process for internal DSLs. The goals of this process are: (1) to give developers a familiar environment in which they can use known and proven development steps, techniques, tools, and host languages, (2) to provide a set of repeatable, iterative steps that support the continuous adaptation and evolution of the domain knowledge and the DSL implementation, and (3) to apply design principles that help to develop DSLs with essential properties and to use host language independent design patterns to plan and communicate the design and implementation of the DSL. The process consists of three development steps (analysis, language design, and language implementation) and applies four principles: open form, agile and test-driven development, design pattern knowledge, and design principle knowledge.

A Trajectory Ontology Design Pattern for Semantic Trajectory Data Warehouses

2019 ◽  
pp. 83-104 ◽  
Author(s):  
Marwa Manaa ◽  
Thouraya Sakouhi ◽  
Jalel Akaichi
Keyword(s):  
Case Studies ◽  
Design Pattern ◽  
Design Patterns ◽  
Domain Knowledge ◽  
Data Warehouses ◽  
Trajectory Data ◽  
Semantic Approach ◽  
Mobility Data ◽  
Ontology Design ◽  
Ontology Design Pattern

Mobility data became an important paradigm for computing performed in various areas. Mobility data is considered as a core revealing the trace of mobile objects displacements. While each area presents a different optic of trajectory, they aim to support mobility data with domain knowledge. Semantic annotations may offer a common model for trajectories. Ontology design patterns seem to be promising solutions to define such trajectory related pattern. They appear more suitable for the annotation of multiperspective data than the only use of ontologies. The trajectory ontology design pattern will be used as a semantic layer for trajectory data warehouses for the sake of analyzing instantaneous behaviors conducted by mobile entities. In this chapter, the authors propose a semantic approach for the semantic modeling of trajectory and trajectory data warehouses based on a trajectory ontology design pattern. They validate the proposal through real case studies dealing with behavior analysis and animal tracking case studies.

Sign in / Sign up

Export Citation Format

Share Document