Ontology as a Service (OaaS): a case for sub-ontology merging on the cloud

Flahive, Andrew; Taniar, David; Rahayu, Wenny

doi:10.1007/s11227-011-0711-4

Cited by 31 publications

(20 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The support for Cloud platforms such as OpenStack and EUCALYPTUS (Nurmi et al, 2009) also needs to be provided, along with support for application hosting, job distribution and concurrency. The infrastructure interoperability across disparate platforms also needs a solution for semantic interfaces in Clouds and Grids (Flahive et al, 2009;Flahive et al, 2011) and this is one of the services that we need to integrate in the Glueing Platform in future.…”

Section: Discussionmentioning

confidence: 99%

Glueing grids and clouds together: a service-oriented approach

Anjum

Hill

McClatchey

et al. 2012

IJWGS

View full text Add to dashboard Cite

Section: Discussionmentioning

confidence: 99%

Glueing grids and clouds together: a service-oriented approach

Anjum

Hill

McClatchey

et al. 2012

IJWGS

View full text Add to dashboard Cite

“…As witnessed in [19,20] , in the near future, there is a second wave of cloud computing, which allows multi-cloud providers to provide an interoperable services to customers. Following this wave, we propose that ontologies that build up the CMKB be composed/merged from different cloud vendors based on the specific application domain and the business process modelling/execution language used, which we call COaaS.…”

Section: Compliance Ontology As a Service (Coaas)mentioning

confidence: 99%

“…In order to build the CMKB of this application, services from these providers need to be merged, extended and tailored to the specific needs of the application. This work direction is ongoing work, where merging techniques from [19] and the applicability and utility of this approach needs to be explored and validated.…”

Section: Compliance Ontology As a Service (Coaas)mentioning

confidence: 99%

Lifecycle Business Process Compliance Management: A Semantically-Enabled Framework

Elgammal

Türetken

2015

2015 International Conference on Cloud Computing (ICCC)

View full text Add to dashboard Cite

Abstract-Following the crisis in 2008, different industrial sectors has faced growing numbers of laws and regulations globally. The number and complexity of these regulations is creating significant issues for governance, risk and compliance management especially for heavily-regulated sectors, such as the financial industry. This paper proposes a semanticallyenabled compliance management framework that backs up the entire business process compliance lifecycle, i.e., design-time verification, runtime and offline monitoring and analysis. In the heart of the framework is an integrated semantic repository incorporating domain, business and regulatory knowledge, at different levels of abstraction, which provides a shared conceptualization of the interrelated compliance and business specifics. Furthermore, given the technological revolution caused by cloud computing, we draw our vision on providing compliance-related ontologies as a service (COaaS) on the cloud. As an initial validation step, we have considered the financial sector with an Anti-Money Laundering (AML) case study and applied our semantic-based approach on.

show abstract

“…Although some ambitious ontology automation [12], [13] works on reducing the time and complexity, however, it is not yet mature enough to be adopted. Putting in to account that the current ontology automation methods are failing to merge different ontologies to produce new mature one [14], [15]. Another ontology platform representation limitation, is it lack flexible validators that capable to validate all different type of platform ontologies.…”

Section: Related Workmentioning

confidence: 99%

Model Driven Atchitecture in to Support of Software Product Line

Elsawi¹,

Sahibuddin²

2015

IJCEE

View full text Add to dashboard Cite

Product management is focusing on variation description; as current and future possible market positioning, acceptable limitations, business opportunity, etc. On the other hand, the Architectural Modeling is concentrating on creation and description of software platform and how it extends and evolves to deliver and support all or any of these product management and product line scenarios. In product line engineering software features are always defined by the variability model. While the requirements specifications, architectural, design, implementation and testing are normally captured by the solution space. In this work we are utilizing the architectural modeling concept of the Model Driven Architecture (MDA) as a complementary of the software product line concerning the solution space part. Aiming to improve software quality and productivity the MDA principles has been adopt. We explicitly employed the Platform Model (PM) designed by the Entity-Attribute-Value (EAV) concept, to provision the transformation between Platform Specific Models (PSM) to the targeted platforms from side, and to manage the platforms diversity and volatility from other side. A case study presented to demonstrate the software productivity under the orthogonal relationship between the MDA and the SPL at the later solution space side.

show abstract

Ontology as a Service (OaaS): a case for sub-ontology merging on the cloud

Cited by 31 publications

References 21 publications

Glueing grids and clouds together: a service-oriented approach

Glueing grids and clouds together: a service-oriented approach

Lifecycle Business Process Compliance Management: A Semantically-Enabled Framework

Model Driven Atchitecture in to Support of Software Product Line

Contact Info

Product

Resources

About