A semantic web environment for components

2009 ◽  
Vol 24 (1) ◽  
pp. 59-75 ◽  
Author(s):  
Hai H. Wang ◽  
Jing Sun

AbstractComponent-based development (CBD) has become an important emerging topic in the software engineering field. It promises long-sought-after benefits such as increased software reuse, reduced development time to market and, hence, reduced software production cost. Despite the huge potential, the lack of reasoning support and development environment of component modeling and verification may hinder its development. Methods and tools that can support component model analysis are highly appreciated by industry. Such a tool support should be fully automated as well as efficient. At the same time, the reasoning tool should scale up well as it may need to handle hundreds or even thousands of components that a modern software system may have. Furthermore, a distributed environment that can effectively manage and compose components is also desirable. In this paper, we present an approach to the modeling and verification of a newly proposed component model using Semantic Web languages and their reasoning tools. We use the Web Ontology Language and the Semantic Web Rule Language to precisely capture the inter-relationships and constraints among the entities in a component model. Semantic Web reasoning tools are deployed to perform automated analysis support of the component models. Moreover, we also proposed a service-oriented architecture (SOA)-based semantic web environment for CBD. The adoption of Semantic Web services and SOA make our component environment more reusable, scalable, dynamic and adaptive.

2009 ◽  
pp. 1250-1279
Author(s):  
Kalapriya Kannan ◽  
Biplav Srivastava

Ontology is a basic building block for the semantic web. An active line of research in semantic web is focused on how to build and evolve ontologies using the information from different ontological sources inherent in the domain. A large part of the IT industry uses software engineering methodologies to build software solutions that solve real-world problems. For them, instead of creating solutions from scratch, reusing previously built software as much as possible is a business-imperative today. As part of their projects, they use design diagrams to capture various facets of the software development process. We discuss how semantic web technologies can help solutionbuilding organizations achieve software reuse by first learning ontologies from design diagrams of existing solutions and then using them to create design diagrams for new solutions. Our technique, called OntExtract, extracts domain ontology information (entities and their relationship(s)) from class diagrams and further refines the extracted information using diagrams that express dynamic interactions among entities such as sequence diagram. A proof of concept implementations is also developed as a Plug-in over a commercial development environment IBM’s Rational Software Architect.


Author(s):  
Kalapriya Kannan

Ontology is a basic building block for the semantic web. An active line of research in semantic web is focused on how to build and evolve ontologies using the information from different ontological sources inherent in the domain. A large part of the IT industry uses software engineering methodologies to build software solutions that solve real-world problems. For them, instead of creating solutions from scratch, reusing previously built software as much as possible is a business-imperative today. As part of their projects, they use design diagrams to capture various facets of the software development process. We discuss how semantic web technologies can help solution-building organizations achieve software reuse by first learning ontologies from design diagrams of existing solutions and then using them to create design diagrams for new solutions. Our technique, called OntExtract, extracts domain ontology information (entities and their relationship(s)) from class diagrams and further refines the extracted information using diagrams that express dynamic interactions among entities such as sequence diagram. A proof of concept implementations is also developed as a Plug-in over a commercial development environment IBM’s Rational Software Architect.


Author(s):  
Jon Hael Simon Brenas ◽  
Mohammad S. Al-Manir ◽  
Kate Zinszer ◽  
Christopher J. Baker ◽  
Arash Shaban-Nejad

ObjectiveMalaria is one of the top causes of death in Africa and some other regions in the world. Data driven surveillance activities are essential for enabling the timely interventions to alleviate the impact of the disease and eventually eliminate malaria. Improving the interoperability of data sources through the use of shared semantics is a key consideration when designing surveillance systems, which must be robust in the face of dynamic changes to one or more components of a distributed infrastructure. Here we introduce a semantic framework to improve interoperability of malaria surveillance systems (SIEMA).IntroductionIn 2015, there were 212 million new cases of malaria, and about 429,000 malaria death, worldwide. African countries accounted for almost 90% of global cases of malaria and 92% of malaria deaths. Currently, malaria data are scattered across different countries, laboratories, and organizations in different heterogeneous data formats and repositories. The diversity of access methodologies makes it difficult to retrieve relevant data in a timely manner. Moreover, lack of rich metadata limits the reusability of data and its integration. The current process of discovering, accessing and reusing the data is inefficient and error-prone profoundly hindering surveillance efforts.As our knowledge about malaria and appropriate preventive measures becomes more comprehensive malaria data management systems, data collection standards, and data stewardship are certain to change regularly. Collectively these changes will make it more difficult to perform accurate data analytics or achieve reliable estimates of important metrics, such as infection rates. Consequently, there is a critical need to rapidly re-assess the integrity of data and knowledge infrastructures that experts depend on to support their surveillance tasks.MethodsIn order to address the challenge of heterogeneity of malaria data sources we recruit domain specific ontologies in the field (e.g. IDOMAL (1)) that define a shared lexicon of concepts and relations. These ontologies are expressed in the standard Web Ontology Language (OWL).To over come challenges in accessing distributed data resources we have adopted the Semantic Automatic Discovery & Integration framework (SADI) (2) to ensure interoperability. SADI provides a way to describe services that provide access to data, detailing inputs and outputs of services and a functional description. Existing ontology terms are used when building SADI Service descriptions. The services can be discovered by querying a registry and combined into complex workflows. Users can issue SPARQL syntax to a query engine which can plan complex workflows to fetch actual data, without having to know how target data is structured or where it is located.In order to tackle changes in target data sources, the ontologies or the service definitions, we create a Dashboard (3) that can report any changes. The Dashboard reuses some existing tools to perform a series of checks. These tools compare versions of ontologies and databases allowing the Dashboard to report these changes. Once a change has been identified, as series of recommendations can be made, e.g. services can be retired or updated so that data access can continue.ResultsWe used the Mosquito Insecticide Resistance Ontology (MIRO) (5) to define the common lexicon for our data sources and queries. The sources we created are CSV files that use the IRbase (4) schema. With the data defined using we specified several SPARQL queries and the SADI services needed to answer them. These services were designed to enabled access to the data separated in different files using different formats. In order to showcase the capabilities of our Dashboard, we also modified parts of the service definitions, of the ontology and of the data sources. This allowed us to test our change detection capabilities. Once changes where detected, we manually updated the services to comply with a revised ontology and data sources and checked that the changes we proposed where yielding services that gave the right answers. In the future, we plan to make the updating of the services automatic.ConclusionsBeing able to make the relevant information accessible to a surveillance expert in a seamless way is critical in tackling and ultimately curing malaria. In order to achieve this, we used existing ontologies and semantic web services to increase the interoperability of the various sources. The data as well as the ontologies being likely to change frequently, we also designed a tool allowing us to detect and identify the changes and to update the services so that the whole surveillance systems becomes more resilient.References1. P. Topalis, E. Mitraka, V Dritsou, E. Dialynas and C. Louis, “IDOMAL: the malaria ontology revisited” in Journal of Biomedical Semantics, vol. 4, no. 1, p. 16, Sep 2013.2. M. D. Wilkinson, B. Vandervalk and L. McCarthy, “The Semantic Automated Discovery and Integration (SADI) web service design-pattern, API and reference implementation” in Journal of Biomedical Semantics, vol. 2, no. 1, p. 8, 2011.3. J.H. Brenas, M.S. Al-Manir, C.J.O. Baker and A. Shaban-Nejad, “Change management dashboard for the SIEMA global surveillance infrastructure”, in International Semantic Web Conference, 20174. E. Dialynas, P. Topalis, J. Vontas and C. Louis, "MIRO and IRbase: IT Tools for the Epidemiological Monitoring of Insecticide Resistance in Mosquito Disease Vectors", in PLOS Neglected Tropical Diseases 2009


2018 ◽  
Vol 2 ◽  
pp. e25614 ◽  
Author(s):  
Florian Pellen ◽  
Sylvain Bouquin ◽  
Isabelle Mougenot ◽  
Régine Vignes-Lebbe

Xper3 (Vignes Lebbe et al. 2016) is a collaborative knowledge base publishing platform that, since its launch in november 2013, has been adopted by over 2 thousand users (Pinel et al. 2017). This is mainly due to its user friendly interface and the simplicity of its data model. The data are stored in MySQL Relational DBs, but the exchange format uses the TDWG standard format SDD (Structured Descriptive DataHagedorn et al. 2005). However, each Xper3 knowledge base is a closed world that the author(s) may or may not share with the scientific community or the public via publishing content and/or identification key (Kopfstein 2016). The explicit taxonomic, geographic and phenotypic limits of a knowledge base are not always well defined in the metadata fields. Conversely terminology vocabularies, such as Phenotype and Trait Ontology PATO and the Plant Ontology PO, and software to edit them, such as Protégé and Phenoscape, are essential in the semantic web, but difficult to handle for biologist without computer skills. These ontologies constitute open worlds, and are expressed themselves by RDF triples (Resource Description Framework). Protégé offers vizualisation and reasoning capabilities for these ontologies (Gennari et al. 2003, Musen 2015). Our challenge is to combine the user friendliness of Xper3 with the expressive power of OWL (Web Ontology Language), the W3C standard for building ontologies. We therefore focused on analyzing the representation of the same taxonomic contents under Xper3 and under different models in OWL. After this critical analysis, we chose a description model that allows automatic export of SDD to OWL and can be easily enriched. We will present the results obtained and their validation on two knowledge bases, one on parasitic crustaceans (Sacculina) and the second on current ferns and fossils (Corvez and Grand 2014). The evolution of the Xper3 platform and the perspectives offered by this link with semantic web standards will be discussed.


2004 ◽  
Vol 1 (2) ◽  
pp. 127-151 ◽  
Author(s):  
Dragan Gasevic

This paper gives the Petri net ontology as the most important element in providing Petri net support for the Semantic Web. Available Petri net formal descriptions are: metamodels, UML profiles, ontologies and syntax. Metamodels are useful, but their main purpose is for Petri net tools. Although the current Petri-net community effort Petri Net Markup Language (PNML) is XML-based, it lacks a precise definition of semantics. Existing Petri net ontologies are partial solutions specialized for a specific problem. In order to show current Petri net model sharing features we use P3 tool that uses PNML/XSLT-based approach for model sharing. This paper suggests developing the Petri net ontology to represent semantics appropriately. This Petri net ontology is described using UML, Resource Description Framework (Schema) RDF(S) and the Web Ontology Language-OWL.


Author(s):  
Souad Bouaicha ◽  
Zizette Boufaida

Although OWL (Web Ontology Language) and SWRL (Semantic Web Rule Language) add considerable expressiveness to the Semantic Web, they do have expressive limitations. For some reasoning problems, it is necessary to modify existing knowledge in an ontology. This kind of problem cannot be fully resolved by OWL and SWRL, as they only support monotonic inference. In this paper, the authors propose SWRLx (Extended Semantic Web Rule Language) as an extension to the SWRL rules. The set of rules obtained with SWRLx are posted to the Jess engine using rewrite meta-rules. The reason for this combination is that it allows the inference of new knowledge and storing it in the knowledge base. The authors propose a formalism for SWRLx along with its implementation through an adaptation of different object-oriented techniques. The Jess rule engine is used to transform these techniques to the Jess model. The authors include a demonstration that demonstrates the importance of this kind of reasoning. In order to verify their proposal, they use a case study inherent to interpretation of a preventive medical check-up.


2008 ◽  
pp. 3309-3320
Author(s):  
Csilla Farkas

This chapter investigates the threat of unwanted Semantic Web inferences. We survey the current efforts to detect and remove unwanted inferences, identify research gaps, and recommend future research directions. We begin with a brief overview of Semantic Web technologies and reasoning methods, followed by a description of the inference problem in traditional databases. In the context of the Semantic Web, we study two types of inferences: (1) entailments defined by the formal semantics of the Resource Description Framework (RDF) and the RDF Schema (RDFS) and (2) inferences supported by semantic languages like the Web Ontology Language (OWL). We compare the Semantic Web inferences to the inferences studied in traditional databases. We show that the inference problem exists on the Semantic Web and that existing security methods do not fully prevent indirect data disclosure via inference channels.


Sign in / Sign up

Export Citation Format

Share Document