DOCSLIB.ORG

Exchanging Policies Between Web Service Entities Using Rule Languages

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Exchanging Policies Between Web Service Entities Using Rule Languages Exchanging Policies between Web Service Entities using Rule Languages Nima Kaviani1, Dragan Gašević2, Marek Hatala1, Gerd Wagner2, Ty Mey Eap1 1Simon Fraser University Surrey, Canada 2Athabasca University, Canada 2Brandenburg University of Technology at Cottbus, Germany {nkaviani, mhatala, teap}@sfu.ca, [email protected], [email protected] Abstract demonstrate the importance of using a rule language in addition to ontologies. This allows run-time discovery, Web rule languages with the ability to cover various composition, and orchestration of Semantic Web ser- types of rules have been recently emerged to make in- vices by defining preconditions or post-conditions for teractions between web resources and broker agents all Web service messages exchanged. For instance, possible. The chance of describing resources and users OWL-S recommends using OWL ontologies along with of a domain through the use of vocabularies is another different types of rule languages (SWRL, KIF, or feature of Web rule languages. Combination of these DRS), while SAWSDL is fully agnostic about the use two properties makes Web rule languages an appro- of a vocabulary (e.g., UML, ODM, OWL) or rule lan- priate medium to make a hybrid model of representing guage (e.g., OCL, SWRL, RuleML). It is worth noting both contexts and rules of a policy-aware system, such that there is no agreement upon which rule language to as a web service. In this paper, we describe how use for Semantic Web services or what type of reason- REWERSE Rule Markup Language (R2ML) can be ing (open or closed world assumption) to support. employed to bridge between different policy languages Besides satisfying clients’ goals when using Seman- using its rich set of rules, vocabulary, and built-in con- tic Web services, trust is another important aspect that structs. We show how the concepts of the KAoS and should be established between a client and a service. Rei policy languages can be transformed to R2ML and Addressing this problem, researchers proposed the use then from R2ML to the other policy languages. Follow- of policy languages. A policy is a rule that specifies ing these mappings, we have implemented transform- under which conditions a resource (or another policy) ers, which enable us not only to share policies between might be disclosed to a requester [13]. To define po- KAoS and Rei, but also to transform policies onto lices on the Semantic Web, various policy languages other rule languages (e.g., F-Logic) for which trans- have been proposed including KAoS [21], Rei [8], and formations from/to R2ML are already developed. PROTUNE [2]. As [13] reports, trust management poli- 1. Introduction cies are also defined as parts (most commonly precon- ditions) of Semantic Web service descriptions. Semantic Web services (SWS), as the augmentation It is obvious that besides various Semantic Web of Web service descriptions through Semantic Web service description languages, we have various policy annotations, facilitate the higher automation of service languages and rule languages. All these languages are discovery, composition, invocation, and monitoring on based on different syntactic representations and formal- the Web. Semantic Web ontologies and ontology lan- isms with no explicitly defined mapping between them. guages (OWL and RDF(S)) are recognized as the main This hampers the use of Semantic Web services from means of knowledge representation for Semantic Web two different perspectives. One is automatic negotia- services [18]. Such ontology-enriched web service de- tion between service client agents and service providers scriptions are later used during negotiation process and automatic matchmaking, where agents and match- between service clients and service providers, which is makers should be able to “understand” various defined by a set of abstract protocols of Semantic Web rule/policy/service web service description languages. Service Architecture (SWSA) [3]. Another perspective is that of a knowledge manage- However, the current proposed standards for de- ment worker who prefers to express the rules and poli- scribing Semantic Web services (i.e. OWL-S, WSDL- cies in a single form rather than in a broad variety of S, and Semantic Web Service Language – SWSL) forms. To attempt to represent the same rules and poli- cies in many forms is cumbersome, time consuming cies. In this scenario, we assume that the service pro- and error prone but it is the only choice available if a vider has its policies defined in Rei and the broker broad base of interoperability is required. agent has the policies defined in KAoS (cf. Section 3). In our approach, we propose the use of REWERSE Suppose that the broker agent has a policy which says: Rule Markup Language (R2ML) [23], which addresses “Client A can only communicate with service providers almost all use-cases and needs for a Rule Interchange that support authentication with X509 certificates and Format (RIF) [4], along with a set of transformations have already been approved as trusted entities for Cli- between Semantic Web service description (e.g., ent A to communicate with.” Figure 1 represents the WSDL-S), rules, and policy languages. We illustrate policy in KAoS defined by the broker agent. Now sup- the benefits of our approach using a Semantic Web pose that during the process of trust negotiation the Service Architecture example where R2ML is used to client needs to ask the service provider whether it could share policies in the process of matchmaking, trust ne- provide any support for the X509 certificate authentica- gotiation, and failure explanation. In the next section, tion. If there is no constraint on releasing the policy, we motivate our research by describing a trust negotia- this can possibly happen by sending the policy of Fig- tion scenario for using Web services. ure 1 to the service provider. In case that there is no understanding about Rei by the client or no knowledge 2. Motivations about KAoS by the service provider, the communica- Web services in general and Semantic Web services tion would fail. So, either the broker agent or the ser- in particular, are of the most important domains for vice provider must be able to exchange the policy to an applying Web policy rules. Policies can be regarded as equivalent Rei policy. The result of transformation can constraints to be combined with Web services to iden- be similar to the policy defined in Figure 2. <entity:Variable rdf:ID="ActorVar"/> tify explicitly conditions under which the use of a ser- <policy:Policy rdf:ID="policy_N100CE"> <deontic:actor rdf:resource="#ActorVar" /> vice is permitted or prohibited [7]. However, due to the <policy:grants rdf:resource="#Policy_CommunicationCertificate" /> <policy:context rdf:resource="#CommunicationActionConstraint" /> diversity of existing policy languages, chances are that </policy:Policy> <deontic:Permission rdf:ID="Policy_CommunicationCertificate"> the policies used to protect the services or resources are <deontic:action rdf:resource="&KAoSAction;CommunicationAction"/> <deontic:actor rdf:resource="#ActorVar"/> not defined in the same language, which makes the <deontic:constriant rdf:resource="#ActionApprovalConstraint"/> </deontic:Permission> process of communication impossible. <constraint:And rdf:ID="ActionApptovalConstraint"> As an example, let us consider a scenario in which a <!--Conjunction of Constraints for the preconditionst plus the CommunicationActor constraint--> </constraint:And> Web service provider and a broker agent, with two <!-- Constraints for the TrustedEntity and CarryMessage different policy languages, need to negotiate their poli- to control the behavior of the system --> <owl:Class rdf:ID="Policy_CommunicationCertificate_Action"> <constraint:SimpleConstriant rdf:ID="CommunicationActor"> <owl:intersectionOf> <constriant:subject rdf:resource="#ActorVar"/> <owl:Class rdf:about="&KAoSAction;CommunicationAction"/> <constriant:object rdf:resource="&rdfs;type"/> <owl:Class> <constraint:predicate rdf:resource="&KAoSActor;ClientA"/> <owl:Restriction> </constraint:SimpleConstriant> <owl:onProperty rdf:resource="&KAoSAction;performedBy"/> <owl:someValuesFrom> <constraint:SimpleConstriant rdf:ID=" CommunicationActionConstraint"> <owl:Class> <constriant:subject rdf:resource="#ActionVar"/> <owl:oneOf rdf:parseType="Collection"> <constriant:object rdf:resource="&KAoSActor; <owl:Thing rdf:about="&InstanceElem;ClientA"/> ServiceProviderSupportingX509Certificates"/> </owl:oneOf> <constraint:predicate rdf:resource="&KAoSPolicy;hasPartner"/> </owl:Class> </constraint:SimpleConstriant> </owl:someValuesFrom> </owl:Restriction> Figure 2. An equivalent Rei policy of Figure 1 </owl:Class> <owl:Restriction> <owl:onProperty rdf:resource="&KAoSPolicy;hasPartner"/> In a general case either the Web agent or the service <owl:allValuesFrom rdf:resource="&KAoSActor; #ServiceProviderSupportingX509Certificates"/> provider must be able to negotiate to the other re- </owl:Restriction> </owl:intersectionOf> sources and agents with different languages for sharing </owl:Class> <!--Checks on whether the entity that is receiving the request by Client their resources and policies as well. However, consid- A is a trusted entity--> <owl:Class rdf:about=" Policy_TrustedEntity "> ering the number of available policy languages and <owl:intersectionOf rdf:parseType="Collection"> <owl:Class rdf:about="&KAoSAction;ApproveAction"/> services, it would be a lot of effort to develop one-to- <owl:Restriction rdf:about="#checkOnCarryingMessages"> <!—Similar
Load more

Recommended publications
  • A General Markup Framework for Integrity and Derivation Rules
    A General Markup Framework for Integrity and Derivation Rules Gerd Wagner, Adrian Giurca, Sergey Lukichev Brandenburg University of Technology at Cottbus, {G.Wagner, Giurca, Lukichev}@tu-cottbus.de This paper discusses the design of integrity and derivation rules on the ba- sis of Rule Markup Language (RuleML) and Semantic Web Rule Language (SWRL). We propose a general markup framework for integrity and deriva- tion rules (R2ML). Rule concepts are defined with the help of MOF/UML, a subset of the UML class modeling language proposed by the Object Man- agement Group (OMG) for the purpose of ’meta-modeling’, i.e. for defin- ing languages conceptually on the level of an abstract (semi-visual) syntax. From these MOF/UML language models we can obtain concrete markup syntax by applying a mapping procedure for generating corresponding lan- guages from parameterized DTDs. Keywords:rule markup languages, in- tegrity rules derivation rules, rule meta-models 1 Introduction Rule markup languages will be the vehicle for using rules on the Web and in distrib- uted systems. They allow deploying, executing, publishing and communicating rules on the Web. They may also play the role of a lingua franca for exchanging rules between different systems and tools. It may be used: to express derivation rules for enriching Web ontologies by adding definitions of derived concepts or for defining data access permissions; to describe and publish the reactive behavior of a system in the form of reaction rules; and to provide a complete XML-based specification of a software agent. In a narrow sense, a rule markup language is a concrete (XML-based) rule syntax for the Web.
    [Show full text]
  • Towards Unifying Rules and Policies for Semantic Web Services
    Towards Unifying Rules and Policies for Semantic Web Services Nima Kaviani 1, Dragan Gaševi ć1, Marek Hatala 1, David Clement 2, Gerd Wagner 3 1Simon Fraser University Surrey, Canada 2Visiphor Corporation, Canada 3Brandenburg University of Technology at Cottbus, Germany {nkaviani, dgasevic, mhatala}@sfu.ca, [email protected], [email protected] Abstract However, the current proposed standards for describing Semantic Web services (i.e. OWL-S [14], Simplifying the discovery of web services on one hand WSDL-S [1], Web Service Modeling Ontology [7], and protecting them from misuse on the other hand has and Semantic Web Service Language – SWSL [2]) initiated several lines of research in the area of policy- demonstrate that it is important to use a rule language aware semantic web services. However, the diversity of in addition to ontologies. This allows run-time approaches, ontologies and languages chosen for discovery, composition, and orchestration of Semantic defining Semantic Web services and policies has made Web services by defining preconditions or post- the research area cluttered. It is now ambiguous how conditions for all Web service messages exchanged different registries and agents with different policy [13]. For example, OWL-S recommends using OWL languages and Semantic Web service ontologies would ontologies together with different types of rule share their information. In this paper we try to solve languages (SWRL, KIF, or DRS), WSMO uses F- the problem of exchanging information between the Logic, while WSDL-S is fully agnostic about the use of registries by defining an interchange framework to a vocabulary (e.g., UML, ODM, OWL) or rule transform business rules and concepts from one language (e.g., OCL, SWRL, RuleML).
    [Show full text]
  • Representation of Business Rules in UML&OCL Models for Developing
    Representation of Business Rules in UML&OCL Models for Developing Information Systems Lina Nemuraite, Lina Ceponiene, and Gediminas Vedrickas Kaunas University of Technology, Studentu 50-308, LT 51368 Kaunas, Lithuania {Lina.Nemuraite,Lina.Ceponiene}@ktu.lt, [email protected] Abstract. Currently Business Rules Approach has attained the great interest in business and software development communities. According to SBVR standard, business rules are the rules under business jurisdiction. Consequently, business rules should be managed by business people. However, acquiring and support- ing the correct and reconciled SBVR style rule sets is the difficult problem. In practice, business rules often are managed by software developers and system analysts; more straightforward and safer processes for capturing and modifying business rules are related with visual business process models. In this paper, possibilities of representing business rules by UML&OCL models and their ap- plicability in modern development processes are investigated1. Keywords: Business rule, UML, OCL, stereotype, constraint, invariant, event, action, condition. 1 Introduction Nowadays every complex and long-term information system has to deal with business rules (BR). Business process management, Service Oriented Architecture (SOA), Web Services, Component-based development, Semantic Web and ordinary databases – some day everyone working in these areas will confront with necessity to separate business rules from the rest of the considered domain. Currently business rules-based IS development methods are evolving rapidly; nevertheless the business rules are implemented mainly in the so called business rules engines that are suitable for spe- cific type of business rules (i.e. production rules). Business rules engines are appear- ing everywhere as a standalone tools (Blaze Advisor, ILOG Rules, Haley systems etc.) as well as components of the middleware, accompanying databases (Microsoft, IBM, Oracle), ERP tools (SAP) etc.
    [Show full text]
  • On Interchanging Between OWL/SWRL and UML/OCL
    On Interchanging Between OWL/SWRL and UML/OCL 1 2 3 3 Milan Milanović , Dragan Gašević , Adrian Giurca , Gerd Wagner , and Vladan Devedžić1 1 FON-School of Business Administration, University of Belgrade, Serbia [email protected], [email protected] 2 School of Interactive Arts and Technology, Simon Fraser University Surrey, Canada [email protected] 3 Institute of Informatics, Brandenburg Technical University at Cottbus, Germany [email protected], [email protected] Abstract. The paper presents a metamodel-driven model transformation approach to interchanging rules between the Semantic Web Rule Language along with the Web Ontology Language (OWL/SWRL) and Object Constraint Language (OCL) along with UML (UML/OCL). The solution is based on the REWERSE Rule Markup Language (R2ML), a MOF-defined general rule language, as a pivotal metamodel and the bi-directional transformations between OWL/SWRL and R2ML and between UML/OCL and R2ML. Besides describing mapping rules between three rule languages, the paper proposes the implementation by using ATLAS Transformation language (ATL) and describes the whole transformation process involving several MOF-based metamodels, XML schemas, and EBNF grammars. 1. Introduction The benefits of bridging Semantic Web and Model-Driven Architecture (MDA) technologies have been recognized by researchers awhile ago. On one hand, ontologies are a backbone of the Semantic Web defined for sharing knowledge based on explicit definitions of domain conceptualization. The Web Ontology Language (OWL) has been adopted as a de facto language standard for specifying ontologies on the Web. On the other hand, models are the central concepts of Model Driven Architecture (MDA).
    [Show full text]
  • SBVR to OWL 2 Mappings: an Automatable and Structural-Rooted Approach
    CLEI ELECTRONIC JOURNAL, VOLUME 17, NUMBER 3, PAPER 2, DECEMBER 2014 SBVR to OWL 2 Mappings: An Automatable and Structural-Rooted Approach Emiliano Reynares UTN FRSF, CIDISI Research Center, Santa Fe, Argentina, S3004EWB, e r eyna r [email protected]. e du.ar and Ma. Laura Caliusco UTN FRSF, CIDISI Research Center, Santa Fe, Argentina, S3004EWB, m c [email protected]. e du.ar and Ma. Rosa Galli INGAR-UTN-CONICET, Santa Fe, Argentina, S3002GJC, m r ga l li@santafe- c oni c et.gov.ar Abstract The wide applicability of mapping business rules expressions to ontology statements have been recently recognized. Some of the most important applications are: (1) using of on- tology reasoners to prove the consistency of business domain information, (2) generation of an ontology intended to be used in the analysis stage of a software development process, and (3) the possibility of encapsulate the declarative specification of business knowledge into information software systems by means of an implemented ontology. The Semantics of Business Vocabulary and Business Rules (SBVR) supports that approach by provid- ing business people with a linguistic way to semantically describe business concepts and specify business rules in an independent way of any information system design. Although previous work have presented some proposals, an exhaustive and automatable approach for them is still lacking. This work presents a broad and detailed set of transformations that allows the automatable generation of an ontology implemented in OWL 2 from the SBVR specifications of a business domain. Such transformations are rooted on the struc- tural specification of both standards and are depicted through a case study.
    [Show full text]
  • Meta-)Models in Multiple Application Domains (Oclapps 2006)
    Electronic Communications of the EASST Volume 5 (2006) Proceedings of the Sixth OCL Workshop OCL for (Meta-)Models in Multiple Application Domains (OCLApps 2006) Towards Sharing Rules Between OWL/SWRL and UML/OCL Milan Milanović, Dragan Gašević, Adrian Giurca, Gerd Wagner and Vladan Devedžić 18 Pages Guest Editors: Dan Chiorean, Birgit Demuth, Martin Gogolla, Jos Warmer Managing Editors: Tiziana Margaria, Julia Padberg, Gabriele Taentzer ECEASST Home Page: http://www.easst.org/eceasst/ ISSN 1863-2122 ECEASST Towards Sharing Rules Between OWL/SWRL and UML/OCL Milan Milanović1, Dragan Gašević2, Adrian Giurca3, Gerd Wagner3 and Vladan Devedžić1 [email protected], [email protected] FON-School of Business Administration, University of Belgrade, Serbia [email protected] School of Computing and Information Systems, Athabasca University, Canada School of Interactive Arts and Technology, Simon Fraser University Surrey, Canada [email protected], [email protected] Institute of Informatics, Brandenburg Technical University at Cottbus, Germany Abstract: The paper presents a metamodel-driven model transformation approach to interchanging rules between the Semantic Web Rule Language along with the Web Ontology Language (OWL/SWRL) and Object Constraint Language (OCL) along with UML (UML/OCL). The solution is based on the REWERSE Rule Markup Language (R2ML), a MOF-defined general rule language, as a pivotal metamodel and the bi- directional transformations between OWL/SWRL and R2ML and between UML/OCL and R2ML. Besides describing mapping rules between three rule languages, the paper proposes the implementation by using ATLAS Transformation language (ATL) and describes the whole transformation process involving several MOF-based metamodels, XML schemas, EBNF grammars.
    [Show full text]
  • Model Driven Architecture and Classification of Business Rules
    Proceedings of the Federated Conference on ISBN 978-83-60810-51-4 Computer Science and Information Systems pp. 949–952 Model Driven Architecture and classification of business rules modelling languages Bartłomiej Gaweł Iwona Skalna AGH University of Science and Technology AGH University of Science and Technology in Krakow in Krakow ul.Gramatyka 10, 30-067 Krakow, Poland ul.Gramatyka 10, 30-067 Krakow, Poland Email: [email protected] Email: [email protected] Abstract—An organisation’s activity under dynamic changes of II. BUSINESS RULES AND SEMANTICS WEB business processes requires continuous improvement of business practices. This implies the necessity of refining decision making The definition of a business rule, coming from GUIDE process. Business rules [6], [8] enable experts to transfer enter- [11], states that a business rule is "a statement that defines or prise strategy onto the operational level using simple sentences constraints some aspect of the business. It is intended to assert which, in turn, can automate reactions to subsequent events both business structure or to control or influence the behaviour of inside and outside the organisation. The main advantage of the the business." In [10], Ross describes several basic principles business rules is their simplicity and flexibility so they can be easily utilised by different organisations for different purposes. of business rules approach. He believes that a language has In order to represent knowledge in a pseudo-natural language the biggest impact on business rules expressiveness. Therefore, understandable to information systems (business rules engines) in the remaining part of this study business rules description notation and description standards are required.
    [Show full text]
  • Linked Rules: Principles for Rule Reuse on the Web ⋆
    Linked Rules: Principles for Rule Reuse on the Web ? Ankesh Khandelwal1, Ian Jacobi2, and Lalana Kagal2 1 Rensselaer Polytechnic Institute [email protected] 2 Massachusetts Institute of Technology fjacobi, [email protected] Abstract. Ontologies are information models which provide vocabulary terms or terminologies and associated meanings to allow the modeling of a domain. They are shared conceptualizations; this has never been more true, because in recent years they have been developed by commu- nity efforts, often including experts from academia as well as industry. Those efforts have been complemented by the standardization of for- mats and languages, such as RDF, OWL, and SPARQL, for representing and (re)using ontologies and data on the (Semantic) Web. Rules, on the other hand, are (seldom) used for knowledge representation (i.e. to de- fine the semantics or integrity constraints). Rules are also used for other intelligent reasoning tasks such as for defining business logic and policies. With the prevalence of shared information models, it is possible and may be necessary to share and reuse rules. Furthermore, with the advent of the Rule Interchange Format (RIF), rules can be shared across many rule systems. We propose a set of basic principles and features by which rules can be represented and shared over the web so that they may be effectively reused and demonstrate several methods of rule reuse. Finally, we discuss how some of these features work in practice in the N3-based AIR web rules language. Keywords: linked rules, online rules, web rules, rule reuse, AIR 1 Introduction The rise of Semantic Web technologies has enabled the publication, processing and analysis of structured data on the web through the use of standard vocabu- laries or terminologies (also known as ontologies) which are developed and shared by user communities.
    [Show full text]
  • A Model-Driven Method for Automatic Generation of Rule-Based Web Applications
    A Model-Driven Method for automatic generation of Rule-based Web Applications Joaqu´ınCa~nadas1, Jos´ePalma2 and Samuel T´unez1 1 Dept. of Languages and Computation. University of Almeria. Spain [email protected], [email protected] 2 Dept. of Information and Communication Engineering. University of Murcia. Spain [email protected] Abstract. Rule languages and inference engines incorporate reasoning capabilities in Web information systems. In this paper, a Model-Driven Development (MDD) approach for automatic code generation of rule- based Web applications is proposed. A rule-based model specifying do- main expert knowledge and business logic through production rules (if- condition-then-action) becomes the source model for the development approach. Demonstrating our proposal, a tool supports the creation of rule models and the automatic execution of model-to-model and model- to-code transformations. As a result, a rich, functional, rule-based Web architecture is generated, based on the Model-View-Controller architec- tural pattern and the JavaServer Faces technology, and integrating a Jess rule engine to perform inference tasks. Key words: Model-Driven Development, Web Applications, Rule-based systems 1 Introduction The design of rule languages and inference engines to provide Web information systems with reasoning capabilities is an important Semantic Web research topic [1] in which production rules (if-condition-then-action) play a leading role, since they enable a declarative representation of domain expert knowledge and busi- ness logic. Rule engines deal with rule bases and execute inference methods for firing the right rules in order to deduce information and conclude new results [2]. This paper addresses the development of rule-based systems embedded in Web applications to provide Web systems with inference capabilities, applying a model-driven approach to automate the development process of rule-based Web applications.
    [Show full text]
  • Logic Logic Logic Specializations of Logic Specializations of Logic
    logic importance - high-level language for expressing knowledge - high expressive power - well-understood formal semantics - precise notion of logical consequence - systems that can automatically derive statements syntactically from a set of premises lecture 17: semantic web rules of#35# ece#627,#winter#‘13# 2# of#35# logic logic importance (2) importance (3) - proof systems for which semantic logical - trace the proof that leads to a logical consequence coincides with syntactic derivation consequence within the proof system - logic can provide explanations for answers soundness & completeness by tracing a proof - predicate logic is unique in the sense that sound and complete proof systems do exist not the case for more expressive logics (higher-order logics) ece#627,#winter#‘13# 3# of#35# ece#627,#winter#‘13# 4# of#35# specializations of logic specializations of logic RDF and OWL Horn logic - RDF/S and OWL (Lite and DL) are specializations of predicate logic – they correspond (roughly) to a rule has the form: A1, . ., An → B a description logic - Ai and B are atomic formulas - they define reasonable subsets of logic - trade-off between the expressive power and the computational complexity (the more expressive the language, the less efficient the corresponding proof systems) ece#627,#winter#‘13# 5# of#35# ece#627,#winter#‘13# 6# of#35# specializations of logic logic: description vs Horn Horn logic OWL vs rules there are two ways of reading such a rule - deductive it is impossible to assert that a person X who is brother of Y is uncle
    [Show full text]
  • Sharing OWL/SWRL and UML/OCL Rules
    Sharing OWL/SWRL and UML/OCL Rules 1 2 3 3 Milan Milanović , Dragan Gašević , Adrian Giurca , Gerd Wagner , and Vladan Devedžić1 1 FON-School of Business Administration, University of Belgrade, Serbia [email protected], [email protected] 2 School of Interactive Arts and Technology, Simon Fraser University Surrey, Canada [email protected] 3 Institute of Informatics, Brandenburg Technical University at Cottbus, Germany [email protected], [email protected] Abstract. The paper presents a metamodel-driven model transformation approach to sharing rules between the Semantic Web Rule Language along with the Web Ontology Language (OWL/SWRL) and Object Constraint Language (OCL) along with UML (UML/OCL). The solution is based on the REWERSE Rule Markup Language (R2ML), a MOF-defined general rule language, as a pivotal metamodel and the bi-directional transformations between OWL/SWRL and R2ML and between UML/OCL and R2ML. 1. Introduction In this paper, we further extend the research in approaching the Semantic Web and MDA by proposing a solution to interchanging rules between two technologies. More specifically, we address the problem of mapping between the Object Constraint Language (OCL), a language for defining constrains and rules on UML and MOF models and metamodels, and the Semantic Web Rule Language (SWRL), a language complementing the OWL language with features for defining rules. In fact, our proposal covers the mapping between OCL along with UML (i.e., UML/OCL) and SWRL along with OWL (OWL/SWRL). In our solution, we use R2ML [1], a MOF-defined general rule language capturing integrity, derivation, production, and reaction rules, which covers almost all of the use cases requirements of the W3C RIF WG [4].
    [Show full text]
  • Towards Rule Interchange and Rule Verification
    Towards Rule Interchange and Rule Verification Von der Fakult¨atf¨ur Mathematik, Naturwissenschaften und Informatik der Brandenburgischen Technischen Universit¨atCottbus zur Erlangung des akademischen Grades Doktor der Ingenieurwissenschaften (Dr.-Ing.) genehmigte Dissertation vorgelegt von Magister der Mathematik in der Fachrichtung Angewandte Mathematik und Informatik Sergey Lukichev Geboren am 15. Februar 1979 in Temirtau (Kazachstan) Gutachter: Prof. Gerd Wagner Gutachter: Prof. Pascal Hitzler Gutachter: Prof. Grzegorz Nalepa Tag der m¨undlichen Pr¨ufung:11. Februar 2010 Abstract Rules are a critical technology component for the early adoption and applications of knowledge-based techniques in e-business, especially enterprize integration and B2B e- commerce. They also play an important role in information systems engineering, especially in the specification of functional requirements where business rules are the foundation for capturing and modeling business application logic. When using rules, companies may encounter obstacles with two issues: The problem of rule interoperability, which is caused by a variety of rule languages and rule systems, and the problem of rule quality as a consequence of a large amount of business rules created and used in an organization. A particular solution to the rule interoperability problem is a standardized way of per- forming rule interchange between different rule languages and tools. The thesis addresses the problem by considering a rule interchange mapping from the Object Constraint Lan- guage (OCL) into the Semantic Web Rule Language (SWRL). This mapping is useful for various communities. For instance, software developers, who actively use UML/OCL, may employ the mapping in order to translate their rules to SWRL and use them in a Semantic Web application.
    [Show full text]