Development of a Logic Layer in the Semantic Web: Research Issues

The ontology layer of the semantic web is now mature enough (i.e. standards like RDF, RDFs, OWL, OWL 2) and the next step is to work on a logic layer for the development of advanced reasoning capabilities for knowledge extraction and efficient decision making. Adding logic to the web means using rules to make inferences. Rules are a means of expressing business processes, policies, contracts etc but most of the studies have focused on the use of monotonic logics in layered development of the semantic web which provides no mechanism for representing or handling incomplete or contradictory information respectively. This paper discusses argumentation, semantic web and defeasible logic programming with their distinct features and identifies the different research issues that need to be addressed in order to realize defeasible argumentative reasoning in the semantic web applications

Medical Virtual Public Services

The healthcare enterprises are very disconnected. This paper intends to propose a solution that will provide citizens, businesses and medical enterprises with improved access to medical virtual public services. Referred medical services are based on existing national medical Web services and which support medically required services provided by physicians and supplementary health care practitioners, laboratory services and diagnostic procedures, clinics and hospitals’ services. Requirements and specific rules of these medical services are considered, and personalization of user preferences will to be supported. The architecture is based on adaptable process management technologies, allowing for virtual services which are dynamically combined from existing national medical services. In this way, a comprehensive workflow process is set up, allowing for service-level agreements, an audit trail and explanation of the process to the end user. The process engine operates on top of a virtual repository, providing a high-level semantic view of information retrieved from heterogeneous information sources, such as national sources of medical services. The system relies on a security framework to ensure all high-level security requirements are met. System’s architecture is business oriented: it focuses on Service Oriented Architecture - SOA concepts, asynchronously combining Web services, Business Process Management – BPM rules and BPEL standards.Business Process Management, Service Oriented Architecture, Application Integration, Web services, information technologies, virtual repository, database.

Advanced eGovernment Information Service Bus (eGov-Bus)

The eGov-Bus project provides citizens and businesses with improved access to virtual public services, which are based on existing national eGovernment Web services and which support cross-border life events. Requirements and specific rules of these life events are considered, and personalization of user preferences is supported. eGov-Bus is based on adaptable process management technologies, allowing for virtual services which are dynamically combined from existing national eGovernment services. In this way, a comprehensive workflow process is set up, allowing for service-level agreements, an audit trail and explanation of the process to the end user. The eGov-Bus process engine operates on top of a virtual repository, providing a high-level semantic view of information retrieved from heterogeneous information sources, such as eGovernment Web services. Further, eGov-Bus relies on a security framework to ensure all high-level security requirements are met. The eGov-Bus architecture is business oriented, it focuses on Service Oriented Architecture (SOA) concepts, asynchronously combining Web services and providing a Service Bus.Frameworks and Guidelines, eGovernment Ontologies, Admininistrative Process Design, Life Events, Web Services, Service Bus Integration

Semantic derivation of enterprise information architecture from riva-based business process architecture

Contemporary Enterprise Information Architecture (EIA) design practice in the industry still suffers from issues that hamper the investment in the EIA design. First and foremost of these issues is the shortcoming of EIA design research to bridge the gap between business and systems (or information) architectures. Secondly, contemporary developed business process architecture methods, and in particular object-based ones have not been fully exploited for EIA design and thus widening the gap between business processes and systems. In practice, knowledge-driven approaches have been thoroughly influencing EIA design. Thirdly, the lack of using knowledge representation methods adversely affected the automation (or semi-automation) of the EIA design process. Software Engineering (SE) technologies and Knowledge Representation using ontologies continue to prove instrumental in the design of domain knowledge. Finally, current EIA development methods have often resulted in complex designs that hampered both adopting and exploiting EIA in medium to large scale organisations.This research is aimed at investigating the derivation of the EIA from a given semantic representation of object-based Business Process Architecture (BPA), and in particular Riva-based BPA using the design science research-based methodology. The key design artefact of this research is the development of the BPAOntoEIA framework that semantically derives EIA from a semantic representation of Riva-based BPA of an enterprise. In this framework, EIA elements were derived from the semantic Riva BPA elements and associated business process models, with forward and backward traceability from/to the derived EIA to/from the original BPA. The BPAOntoEIA framework has been evaluated using the semantic Cancer Care and Registration BPA in Jordan. This framework has been validated using an authentic concern-based evaluation framework employing both static and dynamic validation approaches.The BPAOntoEIA framework contributes to bridging the gap between the business and systems world by providing a business/IT alignment through the EIA derivation process, and using the semantic knowledge of business processes within the resultant EIA. A major novel contribution is the introduction of new evaluation metrics for EIA design, which are quantitative, and are not only indicative of the quality of the semantic EIA derivation from the associated BPA but also the extent of utilisingbusiness process knowledge and traceability amongst EIA elements.Amongst other novel contributions is the semantic EIA derivation process that comprises a suite of the Semantic Web Rules Language (SWRL) rules applied on the semantic BPA elements. The derivation scheme utilises the generic EIA (gEIAOnt) ontology that was developed in this research and represents a semantic meta-model of EIA elements of a generic enterprise. The resultant EIA provides a highly coherent semantic information model that is in-line with the theory of EIA design, semantically enriched, and fully utilises the semantic knowledge of business processes.Benefits of this research to industry include the semantic EIA derivation process and a resultant information model that utilises the semantic information of business processes in the enterprise. Therefore, this enables the enterprise strategic management to plan for a single, secure and accessible information resource that is business process driven, and enabled in an agile environment. The semantic enrichment of the EIA is a starting point for a simplistic design of a domain-independent semantic enterprise architecture for the development of systems of systems in loosely coupled enterprises

Towards a Rule Interchange Language for the Web

This articles discusses rule languages that are needed for a a full deployment of the SemanticWeb. First, it motivates the need for such languages. Then, it presents ten theses addressing (1) the rule and/or logic languages needed on the Web, (2) data and data processing, (3) semantics, and (4) engineering and rendering issues. Finally, it discusses two options that might be chosen in designing a Rule Interchange Format for the Web