This document discusses integrating ontologies and rules. It provides an overview and outline of a tutorial on the topic. The tutorial aims to help the audience understand how to extract business knowledge from policy documents and model it using ontologies and rules. It will cover modeling business knowledge as ontologies and rules, different approaches to combining ontologies and rules, and how to choose the right approach for a given goal. The tutorial contents include sections on OWL 2 ontologies, logic programming and production rules, and integrating ontologies and rules. It will also include a demonstration.
Is TECH is a scientific research company devoted to sustainable development. It operates in Rome and Pisa, Italy in sectors like clean technologies, renewable energies, and information technologies. The company's vision is to provide future generations with healthy progress through scientific and technological development while preserving natural resources. Is TECH works to develop technologies through innovative approaches based on sustainability and balance. It has partnerships with other organizations and has received grants for its projects. The company aims to be a success through flexible strategies, relevant projects, integrated ecosystems, and creating value for stakeholders while respecting people and the planet.
Hans Petter Dahle: Programvareindustrien og fri programvare - erfaringer fra ...Friprogsenteret
The COSI project focused on distributed software development using both open source and proprietary components. It explored business models, development processes, and architectures for this type of collaborative development. The project achieved its goals of introducing agile and distributed development practices and improving understanding of open source collaboration.
The document then discusses some case studies from Norwegian companies involved in COSI, including how they selected and integrated open source components. It also describes how one company, Linpro, improved its development process by allowing nomadic and distributed revision-controlled development using Subversion and the tool SVK.
The document summarizes information about the Telecommunications Software and Systems Group (TSSG). TSSG is located in ArcLabs at Waterford Institute of Technology. It has over 125 projects, 150 academic and industrial partners, and has created 60 jobs through spin-off companies. TSSG performs basic research through Science Foundation Ireland and Higher Education Authority funding, applied research through EU funding, and commercialization through Enterprise Ireland funding. It is a leading research center in Ireland for telecommunications and ranks in the top 10 in Europe for future internet research.
Terminae and Semex are text-based knowledge acquisition tools that can be used to extract conceptual knowledge and rules from text documents. Terminae allows interactive development of domain ontologies by extracting terms from text and structuring them into concepts, concept definitions, and roles. Semex combines information extraction with manual modeling to acquire rules expressed in terms of the conceptual vocabulary. It supports selecting and transforming rule fragments from text as well as navigating and querying the extracted rules. The overall approach uses these tools to build ontologies and acquire rules from policy documents to integrate the knowledge into management systems while maintaining traceability to source texts.
The document discusses business rules and production rules. It defines business rules as requirements or definitions of business behavior. Production rules use a condition-action format to define system behavior. The RETE algorithm is described as an efficient way to match patterns in production rule conditions against working memory. OWL2 ontologies are also discussed as a way to ground business rules in rich logical knowledge descriptions using classes, properties, and axioms.
The document describes the ONTORULE standards-based architecture for rule engines and ontologies. It discusses the relationship between abstract concepts and concrete implementations, and how the platform brings together foundations like replicability, adaptability, and modularity through open standards. Various abstract components and implementations are presented for ontology extraction, modeling, authoring, execution, and quality assurance.
The document discusses the ONTORULE project, which aims to reconcile how business users write rules and policies using natural language with how rule engines require formal semantics and data models. It proposes formalizing vocabularies as ontologies to ground natural language policies and rules, separating domain knowledge from business rules and implementation details. This would allow rules and policies to be consistently applied across applications and organizations. The project seeks to develop standard-based tools to acquire, author, and execute rules grounded in ontology.
This document discusses Parrot and TELIX. Parrot is a tool for generating customizable, multilingual reports combining rules and ontologies. It supports multiple metadata and annotations. TELIX allows representation and interchange of linguistic knowledge as well as multi-layered linguistic annotations of texts using RDF graphs and its own ontology vocabulary.
Is TECH is a scientific research company devoted to sustainable development. It operates in Rome and Pisa, Italy in sectors like clean technologies, renewable energies, and information technologies. The company's vision is to provide future generations with healthy progress through scientific and technological development while preserving natural resources. Is TECH works to develop technologies through innovative approaches based on sustainability and balance. It has partnerships with other organizations and has received grants for its projects. The company aims to be a success through flexible strategies, relevant projects, integrated ecosystems, and creating value for stakeholders while respecting people and the planet.
Hans Petter Dahle: Programvareindustrien og fri programvare - erfaringer fra ...Friprogsenteret
The COSI project focused on distributed software development using both open source and proprietary components. It explored business models, development processes, and architectures for this type of collaborative development. The project achieved its goals of introducing agile and distributed development practices and improving understanding of open source collaboration.
The document then discusses some case studies from Norwegian companies involved in COSI, including how they selected and integrated open source components. It also describes how one company, Linpro, improved its development process by allowing nomadic and distributed revision-controlled development using Subversion and the tool SVK.
The document summarizes information about the Telecommunications Software and Systems Group (TSSG). TSSG is located in ArcLabs at Waterford Institute of Technology. It has over 125 projects, 150 academic and industrial partners, and has created 60 jobs through spin-off companies. TSSG performs basic research through Science Foundation Ireland and Higher Education Authority funding, applied research through EU funding, and commercialization through Enterprise Ireland funding. It is a leading research center in Ireland for telecommunications and ranks in the top 10 in Europe for future internet research.
Terminae and Semex are text-based knowledge acquisition tools that can be used to extract conceptual knowledge and rules from text documents. Terminae allows interactive development of domain ontologies by extracting terms from text and structuring them into concepts, concept definitions, and roles. Semex combines information extraction with manual modeling to acquire rules expressed in terms of the conceptual vocabulary. It supports selecting and transforming rule fragments from text as well as navigating and querying the extracted rules. The overall approach uses these tools to build ontologies and acquire rules from policy documents to integrate the knowledge into management systems while maintaining traceability to source texts.
The document discusses business rules and production rules. It defines business rules as requirements or definitions of business behavior. Production rules use a condition-action format to define system behavior. The RETE algorithm is described as an efficient way to match patterns in production rule conditions against working memory. OWL2 ontologies are also discussed as a way to ground business rules in rich logical knowledge descriptions using classes, properties, and axioms.
The document describes the ONTORULE standards-based architecture for rule engines and ontologies. It discusses the relationship between abstract concepts and concrete implementations, and how the platform brings together foundations like replicability, adaptability, and modularity through open standards. Various abstract components and implementations are presented for ontology extraction, modeling, authoring, execution, and quality assurance.
The document discusses the ONTORULE project, which aims to reconcile how business users write rules and policies using natural language with how rule engines require formal semantics and data models. It proposes formalizing vocabularies as ontologies to ground natural language policies and rules, separating domain knowledge from business rules and implementation details. This would allow rules and policies to be consistently applied across applications and organizations. The project seeks to develop standard-based tools to acquire, author, and execute rules grounded in ontology.
This document discusses Parrot and TELIX. Parrot is a tool for generating customizable, multilingual reports combining rules and ontologies. It supports multiple metadata and annotations. TELIX allows representation and interchange of linguistic knowledge as well as multi-layered linguistic annotations of texts using RDF graphs and its own ontology vocabulary.
Dr. Jochen Friedrich gave a presentation on open standards driving innovation for sustainability. He discussed how open standards promote interoperability, flexibility, and choice which creates an environment for fair competition and prevents vendor lock-in. Open standards are essential for modern IT infrastructures that can effectively offer electronic services. Collaboration between business, government, and citizens groups is needed to develop standards that balance interests. Public policy should ensure open standards are available and referenced for public procurement to foster innovation for smarter and more sustainable solutions.
The document discusses a roundtable meeting held by the Dutch Chemical Industry Association (VNCI) to discuss visions for the future of the Dutch chemical industry in 2030/50. Key topics discussed include presenting the current state and trends in the European and Dutch chemical industries, outlining possible scenarios for 2030/50, and discussing the impact of these scenarios on the vision for the Dutch chemical industry. The roundtable brought together representatives from major Dutch and international chemical companies to provide input on developing VNCI's long-term industry vision.
Revisiting Open Document Format and Office Open XML: The Quiet Revolution Con...Peter O'Kelly
It has been several years since the lively and highly polarized market debate about the relative merits and standards significance of the Open Document Format (ODF) and Office Open XML (OOXML) file format standards. Although ODF and OOXML have since largely faded from the mainstream technology industry press and blogosphere radar, both standards have continued to evolve and gain market support, with significant benefits for all organizations seeking to optimize their use of information contained in documents created with productivity applications.
This document provides an overview of the status and significance of ODF and OOXML. It starts with a summary of the business value of open and XML-based document formats, along with a review of the ODF/OOXML historical debate, including a recap of a widely-discussed January 2008 Burton Group report which included what were, at that time, considered provocative conclusions and market projections.
The document continues with a summary of some of the most impactful ODF- and OOXML-related industry changes during recent years, including Microsoft’s (surprising, to many market observers) commitment to support and contribute to both ODF and OOXML, as well as Oracle’s acquisition of Sun Microsystems, and the acquisition’s ramifications for OpenOffice.org (which served as the starting point for ODF, in 2000).
The analysis concludes with some market projections about likely next steps, as both ODF and OOXML continue to evolve.
ATI Technical CONOPS and Concepts Technical Training Course SamplerJim Jenkins
This three-day course is designed for engineers, scientists, project managers and other professionals who design, build, test or sell complex systems. Each topic is illustrated by real-world case studies discussed by experienced CONOPS and requirements professionals. Key topics are reinforced with small-team exercises. Over 200 pages of sample CONOPS (six) and templates are provided. Students outline CONOPS and build OpCons in class.
FITT Toolbox: Charter for IP & Technology TransferFITT
Within each research organization the adoption and dissemination of clear rules regarding technology transfer and the management of intellectual property greatly facilitate collaborations with industrial partners. A charter proposing guidelines for strategic management in this regard is available in the FITT toolbox. Without any legal constraints, it can easily be used by other research institutions. Based on the results of a European task force and already in force in many research institutions in France, this charter has received the support of the FITT consortium.
www.FITT-for-Innovation.eu
1) ALTER-NET is a network for long-term ecological research that needed to integrate data from many sources using SERONTO, a semantic framework and socio-ecological research ontology.
2) SERONTO includes a core ontology and domain ontologies for ecosystems, biodiversity, and socio-economics. It provides a common model for structuring ecological observations for data management.
3) Developing the ontologies required roles like working groups, experts, and a coordinator to create examples, document issues, and refine the process over time through workshops and a wiki decision forum. Clear coordination and documentation were essential.
My objective with this presentation is to introduce the key frameworks and standards that provide practical guidance when tackling an EA project or implementing an EA capability.
There is currently not a universality accepted definition of EA and therefore it is important to but context to the presentation, so before we start discussing standards and frameworks that address the challenges, I want to take a minute to state my definition of Enterprise Architecture.
Etui activities for wp oegb visitors jagodzinskiWerner Drizhal
The document discusses activities of the European Trade Union Institute (ETUI) concerning worker participation. It provides an overview of ETUI, its research programs including Europeanization of workers representation. It outlines ETUI's work on European Works Councils including developing and maintaining a database of EWC agreements. The database is being revamped to include additional features such as content analysis of EWC agreements, news, case law, and statistics. It also discusses ETUI's work supporting worker representatives in European Companies and training for employee involvement in Europe.
The document summarizes a charter for intellectual property and technology transfer adopted by 33 research laboratories and organizations in France known as the Carnot Institutes. The charter establishes harmonized principles for managing intellectual property and facilitating knowledge transfer with industry partners. It has three parts covering intellectual property policy, knowledge and technology transfer policy, and collaboration principles. The charter was drafted over two months and then adopted by each Carnot Institute over six months. It aims to improve the professionalism of the institutes and standardize practices.
CHOReOS European Project presented at OW2Con2011 in Parischoreos
The document summarizes the CHOReOS project, which aims to develop a choreography-centric service-oriented architecture (SOA) for large-scale systems in the future internet and internet of things.
In the first year, the project achieved establishing an initial architectural style for choreographies, a dynamic development model, specifications for the middleware and integrated development and runtime environment. It is using three use cases related to airports, mobile coordination, and transportation to test the approach.
The project is also focusing on community building by leveraging the OW2 open source software consortium. This includes establishing synergies between the CHOReOS work and OW2's initiatives on the future internet. The overall goal is to
CHOReOS Large Scale Choreographies, OW2con11, Nov 24-25, 2011, ParisOW2
The document summarizes the CHOReOS project, which aims to develop a choreography-centric service-oriented architecture (SOA) for large-scale systems in the future internet and internet of things.
In the first year, the project achieved establishing an initial architectural style for choreographies, a dynamic development model, specifications for the middleware and integrated development and runtime environment. It is using three use cases related to airports, mobile coordination, and transportation to test the approach.
The project is also focusing on community building through the OW2 open source consortium to help ensure the long-term sustainability of the work beyond the initial funding period. It sees leveraging the OW2 ecosystem as key to fostering
Fielt - Business models and the BMG Canvasfieltnotes
This document provides an introduction to business models and the Business Model Canvas. It discusses key concepts of business models, including value propositions, customer segments, channels, and revenue streams. The Business Model Canvas is introduced as a tool to conceptualize the key parts of a business model including the customer, offering, infrastructure, and finances. Examples are given of how each element of the Business Model Canvas can be defined for a business.
Documenting Enterprise Architectures Using OntologiesEugeneMorozov
Enterprise architecture efforts address the challenge of understanding large complex systems to respond to change effectively. Produced documentation, however, is English rather than machine-readable code, is difficult to maintain and reference, and is of limited practical use to the software developers on development projects. Use of enterprise architecture ontologies for organization modelling can help lower cost of creation and maintenance of the architecture descriptions and can make artefacts immediately useful on projects around regulatory compliance lowering the compliance costs.
This presentation was made at a UK APMG-International Showcase event. Join us in London, 20th June 2013 for keynote addresses, masterclasses and round table discussions with leading PPM visionaries. Free to attend if you pre-register. http://uk.apmg-showcase.com/
Paradoxes in standardisation of technologies for Learning, Education and Training - a frustration paper presented at ICCE 2013, Bali, Indonesia on November 21st
Lifecycle support in architectures for ontology-based information systems - iswcThanh Tran
The document presents an architecture for ontology-based information systems (OIS) that supports ontology lifecycles. It proposes a generic architecture with layered organization to support both ontology engineering and usage activities throughout the lifecycle. The architecture includes core ontology services like accessing and reasoning over ontologies, as well as higher-level services for ontology engineering, integration, and evaluation. It also describes the NeOn toolkit implementation of this architecture, which provides reusable components for developing OIS with lifecycle support.
The document introduces the Object Management Group (OMG) and its standards and initiatives. OMG develops modeling standards and specifications to facilitate distributed application integration and interoperability. Its Model Driven Architecture (MDA) promotes modeling applications from business goals to implementation. Key OMG standards include the Unified Modeling Language (UML), which is the most widely adopted modeling language, and standards for business process modeling, software quality assurance, and more.
This document provides an overview of a managerial economics and business strategy course, outlining the course content which will examine what determines the success and failure of firms from an international business perspective, analyzing the firm, industry, institutional environments and their interactions, applying the understanding through case research, and developing strategic thinking.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Dr. Jochen Friedrich gave a presentation on open standards driving innovation for sustainability. He discussed how open standards promote interoperability, flexibility, and choice which creates an environment for fair competition and prevents vendor lock-in. Open standards are essential for modern IT infrastructures that can effectively offer electronic services. Collaboration between business, government, and citizens groups is needed to develop standards that balance interests. Public policy should ensure open standards are available and referenced for public procurement to foster innovation for smarter and more sustainable solutions.
The document discusses a roundtable meeting held by the Dutch Chemical Industry Association (VNCI) to discuss visions for the future of the Dutch chemical industry in 2030/50. Key topics discussed include presenting the current state and trends in the European and Dutch chemical industries, outlining possible scenarios for 2030/50, and discussing the impact of these scenarios on the vision for the Dutch chemical industry. The roundtable brought together representatives from major Dutch and international chemical companies to provide input on developing VNCI's long-term industry vision.
Revisiting Open Document Format and Office Open XML: The Quiet Revolution Con...Peter O'Kelly
It has been several years since the lively and highly polarized market debate about the relative merits and standards significance of the Open Document Format (ODF) and Office Open XML (OOXML) file format standards. Although ODF and OOXML have since largely faded from the mainstream technology industry press and blogosphere radar, both standards have continued to evolve and gain market support, with significant benefits for all organizations seeking to optimize their use of information contained in documents created with productivity applications.
This document provides an overview of the status and significance of ODF and OOXML. It starts with a summary of the business value of open and XML-based document formats, along with a review of the ODF/OOXML historical debate, including a recap of a widely-discussed January 2008 Burton Group report which included what were, at that time, considered provocative conclusions and market projections.
The document continues with a summary of some of the most impactful ODF- and OOXML-related industry changes during recent years, including Microsoft’s (surprising, to many market observers) commitment to support and contribute to both ODF and OOXML, as well as Oracle’s acquisition of Sun Microsystems, and the acquisition’s ramifications for OpenOffice.org (which served as the starting point for ODF, in 2000).
The analysis concludes with some market projections about likely next steps, as both ODF and OOXML continue to evolve.
ATI Technical CONOPS and Concepts Technical Training Course SamplerJim Jenkins
This three-day course is designed for engineers, scientists, project managers and other professionals who design, build, test or sell complex systems. Each topic is illustrated by real-world case studies discussed by experienced CONOPS and requirements professionals. Key topics are reinforced with small-team exercises. Over 200 pages of sample CONOPS (six) and templates are provided. Students outline CONOPS and build OpCons in class.
FITT Toolbox: Charter for IP & Technology TransferFITT
Within each research organization the adoption and dissemination of clear rules regarding technology transfer and the management of intellectual property greatly facilitate collaborations with industrial partners. A charter proposing guidelines for strategic management in this regard is available in the FITT toolbox. Without any legal constraints, it can easily be used by other research institutions. Based on the results of a European task force and already in force in many research institutions in France, this charter has received the support of the FITT consortium.
www.FITT-for-Innovation.eu
1) ALTER-NET is a network for long-term ecological research that needed to integrate data from many sources using SERONTO, a semantic framework and socio-ecological research ontology.
2) SERONTO includes a core ontology and domain ontologies for ecosystems, biodiversity, and socio-economics. It provides a common model for structuring ecological observations for data management.
3) Developing the ontologies required roles like working groups, experts, and a coordinator to create examples, document issues, and refine the process over time through workshops and a wiki decision forum. Clear coordination and documentation were essential.
My objective with this presentation is to introduce the key frameworks and standards that provide practical guidance when tackling an EA project or implementing an EA capability.
There is currently not a universality accepted definition of EA and therefore it is important to but context to the presentation, so before we start discussing standards and frameworks that address the challenges, I want to take a minute to state my definition of Enterprise Architecture.
Etui activities for wp oegb visitors jagodzinskiWerner Drizhal
The document discusses activities of the European Trade Union Institute (ETUI) concerning worker participation. It provides an overview of ETUI, its research programs including Europeanization of workers representation. It outlines ETUI's work on European Works Councils including developing and maintaining a database of EWC agreements. The database is being revamped to include additional features such as content analysis of EWC agreements, news, case law, and statistics. It also discusses ETUI's work supporting worker representatives in European Companies and training for employee involvement in Europe.
The document summarizes a charter for intellectual property and technology transfer adopted by 33 research laboratories and organizations in France known as the Carnot Institutes. The charter establishes harmonized principles for managing intellectual property and facilitating knowledge transfer with industry partners. It has three parts covering intellectual property policy, knowledge and technology transfer policy, and collaboration principles. The charter was drafted over two months and then adopted by each Carnot Institute over six months. It aims to improve the professionalism of the institutes and standardize practices.
CHOReOS European Project presented at OW2Con2011 in Parischoreos
The document summarizes the CHOReOS project, which aims to develop a choreography-centric service-oriented architecture (SOA) for large-scale systems in the future internet and internet of things.
In the first year, the project achieved establishing an initial architectural style for choreographies, a dynamic development model, specifications for the middleware and integrated development and runtime environment. It is using three use cases related to airports, mobile coordination, and transportation to test the approach.
The project is also focusing on community building by leveraging the OW2 open source software consortium. This includes establishing synergies between the CHOReOS work and OW2's initiatives on the future internet. The overall goal is to
CHOReOS Large Scale Choreographies, OW2con11, Nov 24-25, 2011, ParisOW2
The document summarizes the CHOReOS project, which aims to develop a choreography-centric service-oriented architecture (SOA) for large-scale systems in the future internet and internet of things.
In the first year, the project achieved establishing an initial architectural style for choreographies, a dynamic development model, specifications for the middleware and integrated development and runtime environment. It is using three use cases related to airports, mobile coordination, and transportation to test the approach.
The project is also focusing on community building through the OW2 open source consortium to help ensure the long-term sustainability of the work beyond the initial funding period. It sees leveraging the OW2 ecosystem as key to fostering
Fielt - Business models and the BMG Canvasfieltnotes
This document provides an introduction to business models and the Business Model Canvas. It discusses key concepts of business models, including value propositions, customer segments, channels, and revenue streams. The Business Model Canvas is introduced as a tool to conceptualize the key parts of a business model including the customer, offering, infrastructure, and finances. Examples are given of how each element of the Business Model Canvas can be defined for a business.
Documenting Enterprise Architectures Using OntologiesEugeneMorozov
Enterprise architecture efforts address the challenge of understanding large complex systems to respond to change effectively. Produced documentation, however, is English rather than machine-readable code, is difficult to maintain and reference, and is of limited practical use to the software developers on development projects. Use of enterprise architecture ontologies for organization modelling can help lower cost of creation and maintenance of the architecture descriptions and can make artefacts immediately useful on projects around regulatory compliance lowering the compliance costs.
This presentation was made at a UK APMG-International Showcase event. Join us in London, 20th June 2013 for keynote addresses, masterclasses and round table discussions with leading PPM visionaries. Free to attend if you pre-register. http://uk.apmg-showcase.com/
Paradoxes in standardisation of technologies for Learning, Education and Training - a frustration paper presented at ICCE 2013, Bali, Indonesia on November 21st
Lifecycle support in architectures for ontology-based information systems - iswcThanh Tran
The document presents an architecture for ontology-based information systems (OIS) that supports ontology lifecycles. It proposes a generic architecture with layered organization to support both ontology engineering and usage activities throughout the lifecycle. The architecture includes core ontology services like accessing and reasoning over ontologies, as well as higher-level services for ontology engineering, integration, and evaluation. It also describes the NeOn toolkit implementation of this architecture, which provides reusable components for developing OIS with lifecycle support.
The document introduces the Object Management Group (OMG) and its standards and initiatives. OMG develops modeling standards and specifications to facilitate distributed application integration and interoperability. Its Model Driven Architecture (MDA) promotes modeling applications from business goals to implementation. Key OMG standards include the Unified Modeling Language (UML), which is the most widely adopted modeling language, and standards for business process modeling, software quality assurance, and more.
This document provides an overview of a managerial economics and business strategy course, outlining the course content which will examine what determines the success and failure of firms from an international business perspective, analyzing the firm, industry, institutional environments and their interactions, applying the understanding through case research, and developing strategic thinking.
Similar to How to Integrate Ontologies and Rules? (20)
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Generating privacy-protected synthetic data using Secludy and Milvus
How to Integrate Ontologies and Rules?
1. ONTOR UL E
Ontologies meet Business Rules
How to Integrate Ontologies and Rules?
Adeline Nazarenko Luis Polo Thomas Eiter Jos de Bruijn Antonia
Schwichtenberg Stijn Heymans
(Paris13, CTIC, TU Vienna, ontoprise)
12 July 2010 — AAAI 2010 Tutorial Forum
2. ONTOR UL E
Aim of this Tutorial
Ontologies meet Business Rules
You will understand:
1. How NLP can help to extract business knowledge from policy
documents
2. What type of business knowledge is typically modeled as an
ontology and what knowledge as rules (both logical and production
rules)
3. Which approaches to combining ontologies and rules are currently
available; which ones are implemented
4. How to choose the appropriate combination paradigm for your goals;
5. How to model a combination of ontologies and rules using mature
commercial tools
(2/221) c ONTORULE Consortium, all rights reserved
3. ONTOR UL E
Contents of the Tutorial
Ontologies meet Business Rules
1. From Business Policy Documents to a Business Model (1 hour 10
minutes)
2. Integrating Ontologies and Rules (2 hours 15 minutes)
2.1 OWL 2 ontologies (45 minutes)
2.2 Logic Programming and Production Rules (25 minutes)
2.3 Integration (50 minutes)
2.4 Demo (15 minutes)
(3/221) c ONTORULE Consortium, all rights reserved
4. ONTOR UL E
Acknowledgements
Ontologies meet Business Rules
The ONTORULE project consortium: ILOG (an IBM Company),
ontoprise, Free University of Bolzano, Vienna University of
Technology, PNA, Université Paris 13, Fundación CTIC, Audi and
ArcelorMittal
http://ontorule-project.eu
This tutorial is co-funded by the European Union (FP7)
(4/221) c ONTORULE Consortium, all rights reserved
5. ONTOR UL E
Business Vocabulary
Ontologies meet Business Rules
(5/221) c ONTORULE Consortium, all rights reserved
6. ONTOR UL E
Business Scenario
Ontologies meet Business Rules
Business knowledge
Ship to customer
Production process
Decision
(assignment)
Coil Repair
Scrap
(6/221) c ONTORULE Consortium, all rights reserved
7. Part I
From Business Policy Documents to a
Business Model
(7/221) c ONTORULE Consortium, all rights reserved
8. ONTOR UL E
Overview of Part I
Ontologies meet Business Rules
Building business models from written policies
State of the art
Ontology design
Ontology population
Information extraction
Corpus design
Ontology acquisition
Terminological analysis
Term normalization
Conceptualization
Relation identification
Business rule acquisition
Semantic Business Vocabulary and Rules
(8/221) c ONTORULE Consortium, all rights reserved
9. ONTOR UL E
Outline
Ontologies meet Business Rules
Building business models from written policies
State of the art
Corpus design
Ontology acquisition
Business rule acquisition
Semantic Business Vocabulary and Rules
(9/221) c ONTORULE Consortium, all rights reserved
10. ONTOR UL E
Why starting from texts?
Ontologies meet Business Rules
An alternative source of information
Expert knowledge is difficult to make explicit
Experts are seldom available for intensive interviews
Large amount of written information is available
A challenge for knowledge management
Business models must be documented (for traceability)
The source documents must be maintained together with the
business models
(10/221) c ONTORULE Consortium, all rights reserved
11. ONTOR UL E
What can be extracted from texts?
Ontologies meet Business Rules
Although
Documents do not contain all the relevant information
Domain knowledge is seldom explicit
Texts are precious source of information
Documents often express factual knowledge about the domain
entities, their properties, their evolution and their relations.
Documents also reflect the underlying domain knowledge : what are
the relevant concepts? how do they relate to each other?
Policy documents express the business rules that are relevant for
the domain.
(11/221) c ONTORULE Consortium, all rights reserved
12. ONTOR UL E
Example of text
Ontologies meet Business Rules
Domain concept? Domain entity? Business rule? Domaine relation?
(12/221) c ONTORULE Consortium, all rights reserved
13. ONTOR UL E
Outline
Ontologies meet Business Rules
Building business models from written policies
State of the art
Ontology design
Ontology population
Information extraction
Corpus design
Ontology acquisition
Business rule acquisition
Semantic Business Vocabulary and Rules
(13/221) c ONTORULE Consortium, all rights reserved
14. ONTOR UL E
Building a hierarchy of concepts
Ontologies meet Business Rules
Two main approaches
A distributional approach for "learning" ontologies
A terminological approach for assisting the conceptualization task
(14/221) c ONTORULE Consortium, all rights reserved
15. ONTOR UL E
Distributional approach
Ontologies meet Business Rules
Words with similar meanings tend to appear in similar contexts [Harris et
al., 1989].
Example
mechanical properties
mechanical strength
mechanical process
mechanical behaviour
Semantic classes of words can be built out of a distributional
analysis
They are supposed to represent domain concepts
The results are noisy and difficult to exploit
[Hindle, 1990][Dagan et al., 1993][Faure and Nédellec, 1999][Maedche and
Staab, 2001][Cimiano and Völker, 2005]
(15/221) c ONTORULE Consortium, all rights reserved
16. ONTOR UL E
Terminological approach
Ontologies meet Business Rules
Definition (Terms)
Words and compounds that form the domain vocabulary
Example
mechanical properties coil yield point elongation strength
The terms extracted from a text reflect the conceptual vocabulary
A lot of manual work is necessary for filtering, structuring, modeling
[Aussenac-Gilles et al., 2000] [Aussenac-Gilles et al., 2008] [Szulman et al.,
2009a]
(16/221) c ONTORULE Consortium, all rights reserved
17. ONTOR UL E
Ontology population
Ontologies meet Business Rules
Definition (Named entities)
Textual units that are similar to proper names whose meaning is built
through the operation of reference.
Example
STRIP BH2 2% Nitrogen
Given a conceptual model (ontological T-Box), named entity recognition
tools can be used to extract the concept and relation instances and thus
enrich the ontological A-Box.
[Magnini et al., 2006] [Giuliano and Gliozzo, 2008]
(17/221) c ONTORULE Consortium, all rights reserved
18. ONTOR UL E
Information extraction
Ontologies meet Business Rules
Definition (Information extraction)
A set of techniques for automatically extracting structured information
from unstructured textual documents (e.g. Who gives a conference,
when and where?)
[Sundheim, 1992][Grishman and Sundheim, 1996]
Goals
Extracting relations between entities
Discovering concepts properties and relations
[Hearst, 1992] [Aussenac-Gilles and Jacques, 2008]
Extracting business rules
(18/221) c ONTORULE Consortium, all rights reserved
19. ONTOR UL E
Information extraction method
Ontologies meet Business Rules
Information extraction relies on extraction patterns that must be carefully
designed to achieve good precision and recall.
Example
noun1 , noun2 , ... and other noun3 → noun1 < noun3
Hospitals, schools and other public buildings → school < public building
Difficulties
Extraction patterns are often corpus dependent
Manual design is tedious and error prone
Machine learning can help but requires large amount of annotated
data to extract relational information
[Califf M. E., 1998] [Brin, 1999]
(19/221) c ONTORULE Consortium, all rights reserved
20. ONTOR UL E
Building business models from texts
Ontologies meet Business Rules
Goal Combining state-of-the-art approaches
Bootstrapping and help business modeling
Enabling business experts to understand and author
business models
Anchoring business models in policies
Strategy Three major steps
Designing an acquisition corpus
Acquiring the domain conceptual model (ontology)
Modeling business rules
(20/221) c ONTORULE Consortium, all rights reserved
21. ONTOR UL E
Outline
Ontologies meet Business Rules
Building business models from written policies
State of the art
Corpus design
Ontology acquisition
Business rule acquisition
Semantic Business Vocabulary and Rules
(21/221) c ONTORULE Consortium, all rights reserved
22. ONTOR UL E
Corpus design
Ontologies meet Business Rules
Designing an acquisition corpus is a complex task [Atkins et al., 1992]
An acquisition corpus is application dependent
Identifying relevant documents is challenging in many organizations
The sources are heterogeneous (size, types, technicality, target
audience)
There may be missing or redundant pieces of knowledge
Some documents may be confidential
How to achieve a good representativity of the domain to model?
(22/221) c ONTORULE Consortium, all rights reserved
23. ONTOR UL E
In practice
Ontologies meet Business Rules
There is no stable methodology or acknowledged good practice to
design acquisition corpus: all use cases are different.
Knowledge engineers inventory the available documentation and
extract the most useful pieces.
Example (ArcelorMittal use case)
Extract from the product catalogue (10 pages, 3,500 words)
Use case description (2,000 words)
Description of the order Assignment at galvanization Line (1,000
words)
Email discussion with experts
(23/221) c ONTORULE Consortium, all rights reserved
24. ONTOR UL E
Outline
Ontologies meet Business Rules
Building business models from written policies
State of the art
Corpus design
Ontology acquisition
Terminological analysis
Term normalization
Conceptualization
Relation identification
Business rule acquisition
Semantic Business Vocabulary and Rules
(24/221) c ONTORULE Consortium, all rights reserved
25. ONTOR UL E
Ontology design
Ontologies meet Business Rules
The TERMINAE approach to ontology acquisition
[Aussenac-Gilles et al., 2008][Szulman et al., 2009b]
An interactive approach
A terminological approach
TERMINAE tool (http://www-lipn.univ-paris13.fr/~szulman/logi/index.html)
(25/221) c ONTORULE Consortium, all rights reserved
26. ONTOR UL E
From texts to domain model
Ontologies meet Business Rules
Texts reflect the underlying domain model . . .
Domain vocabulary: hardening element, iron crystal lattice
Controlled meaning: elements = chemical element
Situated communication (e.g. actors, locations, roles)
Explicit domain knowledge: The grain structure of steel influences
its mechanical behavior
Factual knowledge: Coil #13 is a coil, with length 670 meters,
currently located in Aviles factor.
But a partial and distorted view
Synonymy: defects = non-conformities
Polysemy: (lab test) results = result (of the assignment process)
Ellipses
Presuppositions
(26/221) c ONTORULE Consortium, all rights reserved
27. ONTOR UL E
From a corpus to an ontology
Ontologies meet Business Rules
Sublanguage model Domain model 1. NLP extraction
(semantic network) (ontology)
2. Selection and
3 disambiguation of
core meanings
3. Formalisation
2
concepts,
terms & roles &
terminological properties
relations
1
Corpus
(text)
word and term occurrences
syntactic relations, sentences
(27/221) c ONTORULE Consortium, all rights reserved
28. ONTOR UL E
Overall approach
Ontologies meet Business Rules
Terminological Termino-conceptual Conceptual
level level level (ontology)
Terms Termino-concepts Concepts
Acquisition
corpus
Terminological Termino-conceptual Conceptual
relations relations relations
(28/221) c ONTORULE Consortium, all rights reserved
29. ONTOR UL E
1st step: Terminological analysis
Ontologies meet Business Rules
Terminological Termino-conceptual Conceptual
level level level (ontology)
Terms Termino-concepts Concepts
Acquisition
corpus
Terminological Termino-conceptual Conceptual
relations relations relations
(29/221) c ONTORULE Consortium, all rights reserved
30. ONTOR UL E
Terminology extraction
Ontologies meet Business Rules
Definition (Terminology)
The body of words or terms relating to a particular subject, field of activity
or branch of knowledge.
Definition (Term Extractor)
Tools that take a domain specific acquisition corpus as input and output a
list of specialized term candidates (e.g. YaTeA [Aubin and Hamon, 2006])
Underlying hypothesis
The relevant terms of a corpus reflect the domain concepts
Terminological analysis can bootstrap the ontology design
(30/221) c ONTORULE Consortium, all rights reserved
31. ONTOR UL E
Terminology extraction and tagging
Ontologies meet Business Rules
Example
The Galvanization Line processes coils, long strips of steel, to provide
them a coating of zinc; this coating will give the product an improved
surface aspect as well as protection from corrosion. During the process
the mechanical properties, such as the yield strength, of the steel are
also changed due to the thermal cycle it goes through.
(31/221) c ONTORULE Consortium, all rights reserved
32. ONTOR UL E
2nd step: Term normalization
Ontologies meet Business Rules
Terminological Termino-conceptual Conceptual
level level level (ontology)
Terms Termino-concepts Concepts
Acquisition
corpus
Terminological Termino-conceptual Conceptual
relations relations relations
(32/221) c ONTORULE Consortium, all rights reserved
33. ONTOR UL E
Term normalization
Ontologies meet Business Rules
To abstract from language peculiarities
Term filtering and selection (noise)
Term variant clustering (synonymy)
Term disambiguation (polysemy)
Output
A semantic network of normalized terms and terminological relations
TERMINAE can export the result in SKOS1
1
(33/221) http://www.w3.org/2004/02/skos/ c ONTORULE Consortium, all rights reserved
34. ONTOR UL E
Term filtering and selection
Ontologies meet Business Rules
Term extractors provide noisy results (candidate terms) that must be
further filtered [Nazarenko and Zargayouna, 2009]
Terminology creation is a social process: there is a consensus
within a given community to use a term t with a specific meaning
Termhood cannot be fully captured through linguistic and statistical
properties
Validation interfaces allow for filtering based on
Characters
Lexical items
Various types of ranking (e.g. frequency, tf.idf)
(34/221) c ONTORULE Consortium, all rights reserved
35. ONTOR UL E
Term variant clustering
Ontologies meet Business Rules
In texts, a given term may appear under various forms. Each group of
(quasi-) synonymous terms must be clustered and associated to a single
termino-concept
Example
residual carbon precipitation thickness reduction rates
precipitation of residual carbon rate in thickness reduction
precipitations of residual carbon reduced thickness
carbon precipitations reduction rate of thickness
(35/221) c ONTORULE Consortium, all rights reserved
36. ONTOR UL E
Variant detection
Ontologies meet Business Rules
Some variants can be identified automatically
Typographical normalization: colour vs color
Morphological analysis
singular vs. plural forms
verbs vs. nominalizations
Syntactic analysis based on equivalent syntactic patterns [Jacquemin
and Tzoukermann, 1999]
Noun Noun ⇔ Noun of Noun
Synonymy propagation [Hamon et al., 1998]
If Noun1 ⇔ Noun2 then Noun1 Noun ⇔ Noun2 Noun
Other variants often have to be manually identified
Irregular morphology: datum vs. data
Semantic variation: defect vs. non-conformities
"... sometimes there are defects, non-conformities with regard to the
allowed ranges... "
(36/221) c ONTORULE Consortium, all rights reserved
37. ONTOR UL E
Term disambiguation
Ontologies meet Business Rules
Ambiguous terms must be disambiguated in such a way that each
relevant meaning be represented as a distinct termino-concept
Example (result)
result → lab test result = lab test data
result → assignment result = outcome of the assignment process
Method (for a given term)
Browse its occurrences
Identify its various meanings
For each relevant meaning, create a termino-concept
Assign the proper occurrences to each termino-concept
(37/221) c ONTORULE Consortium, all rights reserved
38. ONTOR UL E
Terminological forms (TERMINAE)
Ontologies meet Business Rules
(38/221) c ONTORULE Consortium, all rights reserved
39. ONTOR UL E
3rd step: Conceptualization
Ontologies meet Business Rules
Terminological Termino-conceptual Conceptual
level level level (ontology)
Terms Termino-concepts Concepts
Acquisition
corpus
Terminological Termino-conceptual Conceptual
relations relations relations
(39/221) c ONTORULE Consortium, all rights reserved
40. ONTOR UL E
From termino-concepts to concepts
Ontologies meet Business Rules
Once the relevant domain elements are identified, normalized and
disambiguated, the termino-conceptual level can be formalized into a
formal ontology.
At the conceptual level, the termino-concepts can be modeled as
concepts
instances of concepts
relations (object or data properties)
Those modeling choices depend on the domain and the aimed
application.
TERMINAE can export the ontological level in OWL.
(40/221) c ONTORULE Consortium, all rights reserved
41. ONTOR UL E
Traceability of concepts
Ontologies meet Business Rules
When a conceptual element is built out of a termino-concept, it is linked
to that termino-concept, which is itself associated to one or several
synonymous terms and to text occurrences.
The termino-concept/concept links ensure the traceability of the
conceptual level which is grounded in the source document.
(41/221) c ONTORULE Consortium, all rights reserved
42. ONTOR UL E
4th step: Relation identification
Ontologies meet Business Rules
Terminological Termino-conceptual Conceptual
level level level (ontology)
Terms Termino-concepts Concepts
Acquisition
corpus
Terminological Termino-conceptual Conceptual
relations relations relations
(42/221) c ONTORULE Consortium, all rights reserved
43. ONTOR UL E
Enriching the conceptual hierarchy with relations
Ontologies meet Business Rules
Two complementary strategies
Text driven approach where terminological relations
are extracted from the acquisition corpus
are normalized into termino-conceptual relations
are formalized into ontological elements at the conceptual level
Ontology driven approach
The knowledge engineer looks for specific relations
Each relation is associated with a set of characteristic extraction
patterns
The matching text fragments are occurrences of the searched
relations.
(43/221) c ONTORULE Consortium, all rights reserved
44. ONTOR UL E
Looking for relations
Ontologies meet Business Rules
Tools like TERMINAE propose facilities to design patterns and mine
texts
Frequent verbs are good clues
Co-occurring terms often bring relations into light
Example
Property isCharacterizedBy
Steel is characterized by the mechanical properties of products
sold. . .
Surface quality is characterized by surface topography, lubrication
and chemical treatment.
. . . the following parameters, which characterize the material: yield
stress, mechanical strength, fracture elongation. . .
(44/221) c ONTORULE Consortium, all rights reserved
45. ONTOR UL E
Ontology acquisition: conclusion
Ontologies meet Business Rules
A text-based approach of ontology acquisition
Automatic natural language processing of acquisition corpus
Normalization of the terminological output into a disambiguated
semantic network of termino-concepts
Formalization of that network into an ontology
Future developments
Enriching the corpus analysis with named entities recognition
Automatically clustering terms (distributional analysis of terms)
Integrating bottom-up relation extraction methods
(45/221) c ONTORULE Consortium, all rights reserved
46. ONTOR UL E
Ontology acquisition: conclusion
Ontologies meet Business Rules
TERMINAE , a tool to support that process
The modeling work is supported by specific interfaces (i.e.
terminological forms).
Linking concepts to termino-concepts and terms ensure the
traceability of the conceptual model to the source text.
The result is a complex knowledge base:
1. Ontology (OWL)
2. Associated normalized terminology (SKOS), which allows for the
recognition of new occurrences of conceptual elements
3. Ontology to text links, which allow for the visualization of the semantic
annotation of the source text
(46/221) c ONTORULE Consortium, all rights reserved
47. ONTOR UL E
Outline
Ontologies meet Business Rules
Building business models from written policies
State of the art
Corpus design
Ontology acquisition
Business rule acquisition
Semantic Business Vocabulary and Rules
(47/221) c ONTORULE Consortium, all rights reserved
48. ONTOR UL E
Overall approach of rule acquisition
Ontologies meet Business Rules
Structural Operative
1 rules rules
Documents
acquisition corpus
x
Ontology Index x
2 x
3
Documents
acquisition corpus
x
x
x
1 Rule extraction
2 Semantic annotation wrt. ontology 4
3 Extraction of relevant textual fragments Index
4 Rule editing and rephrasing R2
R1
R5 R4 R3
Business rule bases
(48/221) c ONTORULE Consortium, all rights reserved
49. ONTOR UL E
Fragment detection
Ontologies meet Business Rules
Information extraction can help the identification of fragments of text
stating rules, although business rules cannot be fully automatically
extracted from written policies
Precise extraction patterns are difficult to design as they are highly
corpus dependant
Clues and combinations of clues can be used to filter out some
relevant fragments and bootstrap the rule acquisition process
Modal verbs
Linguistic markers
Domain specific action verbs
(49/221) c ONTORULE Consortium, all rights reserved
50. ONTOR UL E
Example of rule fragments
Ontologies meet Business Rules
Example
Usually these targets are allowed to vary within a certain range,
specified in the order.
However, sometimes there are defects, non-conformities with
regard to the allowed ranges, that may make the coil unsuitable for
the order it is assigned to.
If a coil has a defect, mark it as ’defective’ scrap the coil and alert
the user of the defect.
When the line finishes the processing of each coil a decision must
be made regarding the assignment of the coil.
If nevertheless this is the result, the coil must be inspected by an
expert and the decision on the assignment be made manually.
(50/221) c ONTORULE Consortium, all rights reserved
51. ONTOR UL E
Fragment annotation
Ontologies meet Business Rules
Definition (Semantic annotation)
Semantic annotation is an ontology-driven interpretation of the document
content. Textual units (e.g. words, phrases, sentences, paragraphs) are
annotated with ontological ones (concepts, instances, roles, properties
instances) [Ma et al., 2010].
Where do annotations come from?
The corpus that has been used for ontology acquisition has been
annotated during the acquisition process (ontology to text links
output by TERMINAE)
New corpus can be semantically annotated using the combined
ontological-terminological resource output from the acquisition
process (OWL and SKOS output from TERMINAE)
(51/221) c ONTORULE Consortium, all rights reserved
52. ONTOR UL E
Fragment annotation: example
Ontologies meet Business Rules
Source document Ontology
The Galvanisation Line processes coils, long
strips of steel, to provide them a coating of zinc; SteelProduct
this coating will give the product an improved
surface aspect as well as protection from target yieldStrengh
corrosion. During the process the mechanical
Order hasLower Value Coil
properties, such as the yield strength, of the Extraction
steel are also changed due to the thermal cycle it of relevant hasUpper
goes through.
textual belongsTo
fragment
The actual yield strength of the coil should be within the tolerances indicated by the order the coil belongs to.
Semantic annotation wrt. ontology
The actual yield strength of the coil should be within the tolerances indicated by the order the coil belongs to.
The yield strength of the coil should be within the upper and lower values of the order the coil belongs to.
Rule editing
SBVR SE Rule
The yield strength of a coil that belongs to an order must be between the upper and lower
Statement
values of the order
(52/221) c ONTORULE Consortium, all rights reserved
53. ONTOR UL E
Fragment recomposition
Ontologies meet Business Rules
A fragment often cannot be interpreted in isolation
Example
The actual yield strength of the coil should be within the tolerances
indicated by the order the coil belongs to.
The yield strength of a coil that belongs to an order must be within
the upper and lower values of that order .
... if at any point the yield strength is outside of this range there exists a
mechanical defect.
→ The yield strength is a property of a sampling point of a coil (= coil).
The yield strength of a sampling point of a coil that belongs to an
order must be within the upper and lower values of that order .
(53/221) c ONTORULE Consortium, all rights reserved
54. ONTOR UL E
Grounding rules in texts and in the ontology
Ontologies meet Business Rules
Ontology
SteelProduct ChemicalComponent
target yieldStrengh isComposedOf
Order hasLower Value Coil
Steel Zinc
Rule base hasUpper
R3 belongsTo
R2
R1
The Galvanisation Line processes coils, long strips of steel, to provide them a coating of zinc; this coating
will give the product an improved surface aspect as well as protection from corrosion. During the process
the mechanical properties, such as the yield strength, of the steel are also changed due to the thermal
cycle it goes through.
The actual yield strength of the coil should be within the tolerances of the order the coil belongs to.
(54/221) c ONTORULE Consortium, all rights reserved
55. ONTOR UL E
Grounding rules in texts and in the ontology
Ontologies meet Business Rules
Rich index structure
Text
Semantic model (ontology + rules)
3 types of links
Text ↔ Ontology
Ontology ↔ Rules
Rules ↔ Text
Benefit
Explaining rules
Tracing inconsistencies
Updating policy documents
(55/221) c ONTORULE Consortium, all rights reserved
56. ONTOR UL E
Acquisition overall strategy
Ontologies meet Business Rules
Acquisition Term list Network of Ontology
corpus termino-concepts
t1
t2 ONTOLOGY
ACQUISITION
t3 &
... AUTHORING
tn
Extraction Normalisation Formalisation
CR2 RULE
R2 ACQUISITION
CR3
R4 R3 &
CR4 AUTHORING
Relevant
Acquisition fragments
corpus texts Candidate rules Formal rules
(56/221) c ONTORULE Consortium, all rights reserved
57. ONTOR UL E
Ontology and rule acquisition
Ontologies meet Business Rules
Two distinct processes
Rule updates are much more frequent than ontology revisions
The ontology and the business rule base might be authored by
different business people
Two interlinked processes
Rule editing relies on the ontological annotation of the acquisition
corpus
Rule editing might call for revision/extension of the underlying
ontology
The rule fragments can be exploited during the ontology acquisition
to focus on the rule vocabulary and the rule application
(57/221) c ONTORULE Consortium, all rights reserved
58. ONTOR UL E
Outline
Ontologies meet Business Rules
Building business models from written policies
State of the art
Corpus design
Ontology acquisition
Business rule acquisition
Semantic Business Vocabulary and Rules
(58/221) c ONTORULE Consortium, all rights reserved
59. ONTOR UL E
SBVR1
Ontologies meet Business Rules
Semantics of Business Vocabulary and Business Rules
OMG Request For Proposal issued by OMG in June 2003
An OMG standard since December 2007
Version 1.0 formally published in January 2008
Revision 1.1 underway
A business vocabulary contains all the specialized terms, names, and
fact type forms of concepts that a given organization or community uses
in their talking and writing in the course of doing business.
Business Rules form a set of explicit or understood regulations laws or
principles governing conduct or procedure within any business activity,
describing, or prescribing what is possible or allowable.
1
This section is based on the SBVR OMG specification, v1.0 [OMG, 2008] and
some
(59/221) elements are borrowed from a presentation from J. Hall ONTORULE Consortium, all rights reserved
c (Model systems).
60. ONTOR UL E
Basics
Ontologies meet Business Rules
Scope of an SBVR model
body of shared meanings of a semantic community
at least one vocabulary owned by a speech community within that
semantic community
Semantics of SBVR
A subset of SBVR can be expressed in 1st Order Logic
A small extension can only be expressed in modal logic
SBVR Structured English
SBVR proposes Structured English (SBVR SE) as one of possibly
many notations that can map to the SBVR Metamodel
(60/221) c ONTORULE Consortium, all rights reserved
61. ONTOR UL E
SBVR metamodel (1st part)
Ontologies meet Business Rules
SBVR is a (abstract) language in which one can describe
Object types to classify things on the basis of their common
properties (= concepts, also called "noun concepts")
Concept definitions to define the meaning of all the terms at the
ABox and the TBox levels (= concept definition)
Fact types to define relations involving object types and their
instances (= n-ary predicates, also called "verb concepts")
Fact type forms to enable speech community specific
communications (= patterns or templates of expressions of a fact
type)
(61/221) c ONTORULE Consortium, all rights reserved
62. ONTOR UL E
Example
Ontologies meet Business Rules
coil belongs to order
Synonymous form: order owns coil
Necessity: Each coil belongs to at most one order .
Note: If a coil fails to meet order targets it is de-assigned from the
order.
coil has been galvanised
unprocessed product
Definition: coil that belongs to an order and that has not been
galvanised
processed product
Definition: coil that belongs to an order and that has been galvanised
Concept Type: implicitly-understood concept
processed product has lab test
Necessity: Each lab test is of exactly one processed product .
lab-tested product
Definition: processed product that has had a lab test
(62/221) c ONTORULE Consortium, all rights reserved
63. ONTOR UL E
Terms and names
Ontologies meet Business Rules
Individual concepts (noun concepts) have names
ArcelorMittal Galvanization Line Coil #13 Gijon factory
Concepts (general noun concepts)
May have formal, part-formal or informal definitions
May be adopted
May be ’implicitly understood’ (terms used in their everyday sense)
Width Thickness Weight
(63/221) c ONTORULE Consortium, all rights reserved
64. ONTOR UL E
Concept intensional definition
Ontologies meet Business Rules
unprocessed product (defined concept)
coil (more general concept)
that belongs to an order and that has not been galvanised (delimiting
characteristic)
(64/221) c ONTORULE Consortium, all rights reserved
65. ONTOR UL E
Fact types
Ontologies meet Business Rules
Fact types define unary, binary or n-ary relations between concepts
coil has been galvanised
coil belongs to order
Concepts (general noun concepts) play roles in fact types
A role name may be:
an existing term: order
a specific role name
Coil is assigned to order
OrderAssignement
Fact symbols have meaning only in relation to the concept that play
the fact type roles
has has different meanings in Coil has Thickness and in
OrderTarget has LowerTolerance
(65/221) c ONTORULE Consortium, all rights reserved
66. ONTOR UL E
Constraints in fact types
Ontologies meet Business Rules
Fact type
Coil belongs to order
By itself, the fact type means
’a coil can belong to any number of orders (including zero),
and vice versaa’
A fact type can be constrained (’necessity’ structural rule)
Necessity: Each coil belongs to at most one order .
(66/221) c ONTORULE Consortium, all rights reserved
67. ONTOR UL E
Fact type forms
Ontologies meet Business Rules
Definition
representation of a fact type by a pattern
or template of expressions based on the fact type
A fact type may have multiple fact type forms
order has target yield strength (semantics in role name)
order targets yield strength (semantics in verb)
yield strength is target of order
(67/221) c ONTORULE Consortium, all rights reserved
68. ONTOR UL E
SBVR metamodel (2nd part)
Ontologies meet Business Rules
SBVR is a (abstract) language in which one can describe
Integrity rules to restrict the contents of the ABox and the content
transitions to the ones considered useful
Derivation rules to generate new assertions of facts (at the ABox
level) from existing assertions of facts
Operative business rules to specify prescribed, suggested or
self-imposed rules (may be violated)
(68/221) c ONTORULE Consortium, all rights reserved
69. ONTOR UL E
Creating business rules
Ontologies meet Business Rules
1. Select a base fact type
yield strength is between the upper and lower values of order
2. Apply a modal operator
’Necessity’ or ’Possibility’ for a structural rule
’Obligation’ or ’Permission’ for an operative rule.
It is obligatory that yield strength is between the upper and lower
values of order .
Alternatively: yield strength must be between the upper and lower
values order .
3. Use additional fact types to quantify and qualify the rule
The yield strength of a sampling point of a coil that belongs to an
order must be between the upper and lower values of the order .
(69/221) c ONTORULE Consortium, all rights reserved
70. ONTOR UL E
Level of enforcement
Ontologies meet Business Rules
The level of enforcement describes how strictly a rule will be
enforced
Some operative rules cannot be automated (or the enterprise has
decided not to automate them).
They require an enforcement regime:
Level of enforcement (strict, pre-authorized, post-justified . . . ) =
business rules
Detection of violations
Remediation of unacceptable activity
(Possibly) application of sanctions to offenders
An enforcement regime often leads to additional IS requirements
(70/221) c ONTORULE Consortium, all rights reserved
71. ONTOR UL E
Benefits of SBVR
Ontologies meet Business Rules
Unified business model combining the conceptual model (ontology)
and the rules
Business oriented presentation
Documented business model
Verbalization of the business model understandable to business
people
SBVR, a way to specify the expected behaviour of the rule system.
(71/221) c ONTORULE Consortium, all rights reserved
72. Part II
Integrating Ontologies and Rules
(72/221) c ONTORULE Consortium, all rights reserved
73. ONTOR UL E
Overview of Part II
Ontologies meet Business Rules
Modeling business knowledge using OWL2
Why use OWL for business knowledge?
OWL by example
Limitations
Conclusions
Rules: Logical and Production Rules
Logical Rules
Production Rules
Logical vs. Production
Rules vs. Ontologies
Integration of Rules and Ontologies
Integration of Logical Rules with Ontologies
Integration of Production Rules with Ontologies
Demo
(73/221) c ONTORULE Consortium, all rights reserved
74. ONTOR UL E
Outline
Ontologies meet Business Rules
Modeling business knowledge using OWL2
Why use OWL for business knowledge?
OWL by example
Limitations
Conclusions
Rules: Logical and Production Rules
Integration of Rules and Ontologies
Demo
(74/221) c ONTORULE Consortium, all rights reserved
75. ONTOR UL E
Outline
Ontologies meet Business Rules
Modeling business knowledge using OWL2
Why use OWL for business knowledge?
OWL by example
Limitations
Conclusions
Rules: Logical and Production Rules
Integration of Rules and Ontologies
Demo
(75/221) c ONTORULE Consortium, all rights reserved
76. ONTOR UL E
What is an ontology
Ontologies meet Business Rules
An ontology is a shared model of some domain of the world:
... introducing some vocabulary
... defining the meaning of the concepts
... relating the concepts using properties
... describing the individuals
(76/221) c ONTORULE Consortium, all rights reserved
77. ONTOR UL E
What is OWL
Ontologies meet Business Rules
OWL is the W3C recommended language for web ontologies
Based on the Description Logic SROIQ
History: OWL1 (2004) and OWL2 (2009)
Several syntaxes: RDF/XML (normative), DL, functional, XML,
Manchester
(77/221) c ONTORULE Consortium, all rights reserved
78. ONTOR UL E
Description Logics
Ontologies meet Business Rules
A Description Logic Knowledge Base consists of three parts:
1. TBox: the ontology axioms defining the concepts
2. RBox: the ontology axioms defining the properties
3. ABox: ground facts about the individuals, described using the
terminology
Description Logics is a subset of First Order Logic
Open World Assumption (OWA)
Not all statements about a domain can be formalized with a
Description Logic
(78/221) c ONTORULE Consortium, all rights reserved
79. ONTOR UL E
Why should I care about OWL
Ontologies meet Business Rules
Even if it is not possible to produce a complete model for a business
domain, using OWL has a number advantages:
Understability and clarity of the model
Easy maintenance of the model
Reusability of a model
(79/221) c ONTORULE Consortium, all rights reserved
80. ONTOR UL E
OWL advantages: Understability and Clarity
Ontologies meet Business Rules
OWL, as a Description Logic language, has an object-centered view.
It grasps the structure of the business domain:
Aggregation: “A steel product has a number of attributes: length,
weight, chemical composition”
Classification: “Steel products can be flat, long or stainless”
Generalization: “All steel products are produced in a steel factory ”
DL axioms are easier to understand than FOL formulas: “All coils are
steel products”
FOL: ∀x Coil(x) → SteelProduct(x)
DL: Coil SteelProduct
(80/221) c ONTORULE Consortium, all rights reserved
81. ONTOR UL E
OWL advantages: Easy Maintenance
Ontologies meet Business Rules
Logical implications of each statement are intuitive
Formal validation of the business model. Automatic consistency
checking using dedicated tools (DL reasoners)
Not looking for completeness or integrity, but just for absence of
contradictions
(81/221) c ONTORULE Consortium, all rights reserved
82. ONTOR UL E
OWL advantages: Reusability
Ontologies meet Business Rules
Ontologies capture the static knowledge of the domain
Changes are not frequent
Several applications can benefit from it as a business data model
Being a standard means:
No vendor lock-in. Applications are interoperable
Ontologies can be published and found in the web. OWL is built on
top of the web stack (URIs, HTTP, etc.).The default exchanged
format is RDF.
(82/221) c ONTORULE Consortium, all rights reserved
83. ONTOR UL E
Outline
Ontologies meet Business Rules
Modeling business knowledge using OWL2
Why use OWL for business knowledge?
OWL by example
Limitations
Conclusions
Rules: Logical and Production Rules
Integration of Rules and Ontologies
Demo
(83/221) c ONTORULE Consortium, all rights reserved
84. ONTOR UL E
OWL in a nutshell
Ontologies meet Business Rules
OWL vocabulary Properties
Concepts, Properties Subsumption and
and Individuals Equivalence
Concepts Disjointness
Domain and Range
Subsumption and
Inverse, Funct. and Inv.
Equivalence
Funct.
Disjointness
Symm., Asymm.,
Union, Intersection and
Reflex. and Irreflex.
Complement
Transitiveness and
Enumerations
Property Chains
Cardinality, Existential,
Universal and Other features
Individual restrictions
(84/221) c ONTORULE Consortium, all rights reserved
85. ONTOR UL E
Running Example
Ontologies meet Business Rules
Business statements from the steel domain will be examined individually
Each sentence will introduce a new modeling feature of OWL
The following slides have the same pattern:
1. Business sentence in natural language
2. Sentence formalization (DL and/or Functional Syntaxes)
3. Comments and consequences
(85/221) c ONTORULE Consortium, all rights reserved
86. ONTOR UL E
Concepts
Ontologies meet Business Rules
“There is a set of objects called coils”
Example
Coil
A new symbol (URI) is introduced in the ontology vocabulary for
each business concept
A DL concept represents a set of individuals of a business domain
(86/221) c ONTORULE Consortium, all rights reserved
87. ONTOR UL E
Concept Hierarchies
Ontologies meet Business Rules
“Coils are flat steel products which in turn are steel products”
Example
Coil FlatSteelProduct SteelProduct
Arbitrarily complex concept hierarchies can be defined
Multiple inheritance is allowed
(87/221) c ONTORULE Consortium, all rights reserved
88. ONTOR UL E
Concept Equivalence
Ontologies meet Business Rules
“Customer and product assignee are equivalent views of the
same concept”
Example
Customer ≡ ProductAssignee
The same set of objects are interpreted in two different points of
views (e.g. accounting and shipment)
Equivalence axioms may be used to align existing vocabularies
(88/221) c ONTORULE Consortium, all rights reserved
89. ONTOR UL E
Disjoint Concepts
Ontologies meet Business Rules
“Chemical elements are either carbon elements or
non-carbon elements”
Example
CarbonElement NonCarbonElement ≡ ⊥
With this kind of axioms, it is possible to explicitly forbid the
classification of a single domain object as an instance of two (or
more) incompatible concepts.
(89/221) c ONTORULE Consortium, all rights reserved
90. ONTOR UL E
Datatype Properties
Ontologies meet Business Rules
“Length is a measurable property”
Example
length
Datatype properties express attributes of the domain objects
Their values are literals (numbers, strings, booleans, etc.)
Most datatypes are taken from XML Schema
(90/221) c ONTORULE Consortium, all rights reserved
91. ONTOR UL E
Object Properties
Ontologies meet Business Rules
“Location is a property of physical objects”
Example
location
Object properties express relationships between domain objects
(91/221) c ONTORULE Consortium, all rights reserved
92. ONTOR UL E
Property Domain
Ontologies meet Business Rules
“Length is a property of coils”
Example
∀length− .Coil
Domain axioms are not checks, but inference rules, i.e. “all objects
that have a length are inferred to be coils”
Note for OO programmers: Properties are defined globally and
independently of concepts (classes). Domain declaration is
optional.
(92/221) c ONTORULE Consortium, all rights reserved
93. ONTOR UL E
Property Range
Ontologies meet Business Rules
“Length is measured numerically”
“Objects in the steel domain are located in factories”
Example
∀length.xsd : double
∀locatedIn.Factory
Same notes that in the previous slide apply here
(93/221) c ONTORULE Consortium, all rights reserved
94. ONTOR UL E
Properties Hierarchy
Ontologies meet Business Rules
“If a coil has been rejected by a QA team, then it has been
examined by that team”
Example
rejectedBy examinedBy
Arbitrarily complex property hierarchies can be defined
Multiple inheritance is allowed
Note for OO programmers: this feature is usually not available in OO
programming languages.
(94/221) c ONTORULE Consortium, all rights reserved
95. ONTOR UL E
Property Equivalence
Ontologies meet Business Rules
“The location property in system A is the same thing as the
place property in system B”
Example
location ≡ place
The same set of relationships are interpreted from two different
points of views (e.g. accounting and shipment)
Equivalence axioms may be used to align existing vocabularies
(95/221) c ONTORULE Consortium, all rights reserved
96. ONTOR UL E
Disjoint properties
Ontologies meet Business Rules
“Regarding Quality Assurance, a coil cannot be produced and
verified by the same team”
Example
DisjointObjectProperties( producedBy verifiedBy )
With this kind of axioms, it is possible to explicitly forbid certain pairs
of relationships
(96/221) c ONTORULE Consortium, all rights reserved
97. ONTOR UL E
Individual Positive Assertions
Ontologies meet Business Rules
“Coil #13 is a coil, with length 670 meters, currently located in
Aviles factory”
Example
Coil#13 ∈ Coil
(Coil#13, 670) ∈ length
(Coil#13, AvilesFactory) ∈ locatedIn
Individuals are classified in concepts using unary predicates
Values for properties of individuals are asserted using binary
predicates
Assertions about individuals populate the knowledge base (A-Box)
(97/221) c ONTORULE Consortium, all rights reserved
98. ONTOR UL E
Individual Negative Assertions
Ontologies meet Business Rules
“Coil #13 does not contain chromium in its chemical
composition”
Example
(Coil#13, Chromium) ∈ contains
/
This kind of assertions are useful to detect inconsistencies in the
description of individuals
Negative assertions can be made about datatype and object
properties, but not about classification
(98/221) c ONTORULE Consortium, all rights reserved
99. ONTOR UL E
Individual Equality and Inequality
Ontologies meet Business Rules
“Coil #13 and product #7 are the same physical object”
“Aviles factory and Gijon factory are different places”
Example
Coil#13 = product#7
AvilesFactory = GijonFactory
Individual equality means logical equality. No unification process is
involved
Be aware of OWA and the lack of Unique Name Assumption (UNA):
Gijon and Aviles factories are not different places unless you
explicitly declare them so
(99/221) c ONTORULE Consortium, all rights reserved
100. ONTOR UL E
Concept Intersection
Ontologies meet Business Rules
“Coils are ready to be shipped whenever they have passed the
Quality Assurance process”
Example
ShippableCoil ≡ Coil QACertifiedProduct
Complex concepts can be created using set-intersection
This mechanism is similar to the definition of multiple inheritances
(eg. ShippableCoil Coil; ShippableCoil QACertifiedProduct)
(100/221) c ONTORULE Consortium, all rights reserved
101. ONTOR UL E
Concept Union
Ontologies meet Business Rules
“Steel products can be flat steel products, long steel products
or stainless steel products”
Example
SteelProduct ≡ FlatProduct LongProduct StainlessSteelProduct
Complex concepts can be created using set-union
This mechanism is often used in disjointness axioms:
FlatProduct LongProduct ≡ ⊥,
FlatProduct StainlessSteelProduct ≡ ⊥,
LongProduct StainlessSteelProduct ≡ ⊥
(101/221) c ONTORULE Consortium, all rights reserved
102. ONTOR UL E
Enumeration of Individuals
Ontologies meet Business Rules
“Chemical elements involved in steel products are Iron, Carbon,
Manganese, Chromium, Vandium, Tungsten and Nickel”
Example
ChemicalElement ≡
{Iron, Carbon, Manganese, Chromium, Vandium, Tungsten, Nickel}
Concepts can be defined extensionally, i.e. enumerating the set of
individuals
(102/221) c ONTORULE Consortium, all rights reserved
103. ONTOR UL E
Concept Complement
Ontologies meet Business Rules
“Non-carbon elements are all except carbon and iron”
Example
NonCarbonElement ≡ ChemicalElement ¬{carbon, iron}
More details about negation in DLs will be addressed later in the
tutorial
(103/221) c ONTORULE Consortium, all rights reserved
104. ONTOR UL E
Cardinality Restrictions
Ontologies meet Business Rules
“A coil can be shipped to a customer if it contains
at most 12 minor defects”
Example
ShippableCoil ≤ 12contains.MinorDefect
Restriction on the number of relationships can be qualified (to a
certain concept) and non-qualified (to any concept)
Operator can be at most (≤), at least (≥) or exactly (=)
(104/221) c ONTORULE Consortium, all rights reserved
105. ONTOR UL E
Existential Restrictions
Ontologies meet Business Rules
“Alloy Steel is steel that contains non-carbon elements”
Example
AlloySteel ≡ Steel ∃contains.NonCarbonElement
Intensional concept definition based on the existence of
relationships between business objects
It is often used with subclassification axioms or to define new
concepts with equivalence axioms
(105/221) c ONTORULE Consortium, all rights reserved
106. ONTOR UL E
Universal Restriction on Property Expressions
Ontologies meet Business Rules
“An order is fulfilled if all the coils are shippable”
Example
SatisfiedOrder ∀comprises.ShippableCoil
Intensional concept definition based on the universality of
relationships between business objects
It is often used with subclassification axioms or to define new
concepts with equivalence axioms
It can be used to restrict the range of a property in the context of a
particular concept
(106/221) c ONTORULE Consortium, all rights reserved
107. ONTOR UL E
Individual Value Restriction
Ontologies meet Business Rules
“Maraging Steel is a kind of steel that contains nickel”
Example
MaragingSteel ≡ Steel ∃contains.{Nickel}
Intensional concept definition that relates business objects with a
single individual (eg. Nickel)
It is a particular case of the existential restrictions
(107/221) c ONTORULE Consortium, all rights reserved
108. ONTOR UL E
Inverse properties
Ontologies meet Business Rules
“If a product has a defect, the defect must be located in the
product”
Example
hasDefect ≡ locatedIn−
Some properties can be modeled in both directions (eg. hasPart and
isPartOf ). Declaring them as inverse simplifies the population of the
ontology, as it is possible to infer the other direction.
(108/221) c ONTORULE Consortium, all rights reserved
109. ONTOR UL E
Functional property
Ontologies meet Business Rules
“A coil can be shipped to exactly one customer”
“A coil has just one length”
Example
FunctionalObjectProperty( shippedTo )
FunctionalDatatypeProperty( length )
Object equality may be inferred as a consequence of a functional
property having multiple values (eg. “If coil #12 has been shipped to
customer A and customer B, then both customers are the same”)
(109/221) c ONTORULE Consortium, all rights reserved
110. ONTOR UL E
Inverse functional property
Ontologies meet Business Rules
“Two coils produced to meet the same order must be the same,
even if they are described by different systems”
Example
InverseFunctionalObjectProperty( hasOrder )
Object equality may be inferred as a consequence of an inverse
functional property having multiple values (eg. “If coil #12 and
inventory item #7 meet the same order #323, they are the same
object”)
Useful for integrating data coming from different knowledge bases
(110/221) c ONTORULE Consortium, all rights reserved
111. ONTOR UL E
Keys
Ontologies meet Business Rules
“Each coil has a product ID which uniquely identifies the coil”
Example
HasKey( Coil ( ) ( productId ) )
Similar to keys in databases
Compound keys (using both object and datatype properties) are
allowed
As inverse functional properties, keys are also useful to integrate
data coming from different sources
(111/221) c ONTORULE Consortium, all rights reserved
112. ONTOR UL E
Reflexive and Symmetrical Properties
Ontologies meet Business Rules
“Several coils can be related because they come from the
same steel casting”
Example
ReflexiveObjectProperty( sameCastingAs )
SymmetricObjectProperty( sameCastingAs )
Reflexive properties relates a domain object with itself
Symmetric properties create “mirror” relationships
(112/221) c ONTORULE Consortium, all rights reserved
113. ONTOR UL E
Irreflexive and Asymmetrical Properties
Ontologies meet Business Rules
“Steel production is arranged in a sequence of production steps
which follow each other”
Example
IrreflexiveObjectProperty( follows )
AsymmetricalObjectProperty( follows )
Irreflexive: objects can not be related with themselves
Asymmetrical: objects can be related just in one direction, but not in
the other one
(113/221) c ONTORULE Consortium, all rights reserved
114. ONTOR UL E
Transitive Property
Ontologies meet Business Rules
“All metallurgical steps that follow a given one are considered
to be downstream in the processing chain”
Example
follows downstream
downstream∗ downstream
Transitivity is not inherited in the property hierarchy
(114/221) c ONTORULE Consortium, all rights reserved
115. ONTOR UL E
Property Chains
Ontologies meet Business Rules
“If a shippable coil is assigned to an order, the coil is shipped to
the customer who placed the order”
Example
assignedTo ◦ placedBy shippedTo
Coil
placedBy Customer
assignedTo Order
shippedTo
Simple rules can be implemented using this mechanism. Chaining
can be arbitrarily long, but the properties are required to be chained:
range(pi ) dom(pi+1 ) = ⊥
(115/221) c ONTORULE Consortium, all rights reserved
116. ONTOR UL E
Metamodeling
Ontologies meet Business Rules
“Coils and wire are entries in the company product catalog.
Coil #13 is a coil. ”
Example
Coil ∈ ProductCatalogEntry
Wire ∈ ProductCatalogEntry
Coil#13 ∈ Coil
Metamodeling introduces two levels of terminology description
Metamodeling is useful to provide additional domain information
about concepts
Be careful with metamodeling. Sometimes it is preferable to use an
alternative modeling or even annotations
(116/221) c ONTORULE Consortium, all rights reserved
117. ONTOR UL E
Datatype Restrictions and Definitions
Ontologies meet Business Rules
“Order IDs in Aviles start with prefix 033 plus another 10 digits”
Example
Declaration( Datatype ( OrderId ) )
DatatypeDefinition( OrderId
DatatypeRestriction( xsd : string xsd : pattern ”033[0 − 9]{10}” ) )
DataPropertyRange( hasOrderID OrderId )
XML Schema provides the basic datatypes for OWL
User-defined datatypes are allowed
Some validation data rules can be implemented using restrictions
(eg. numerical ranges)
(117/221) c ONTORULE Consortium, all rights reserved
118. ONTOR UL E
Resource Annotations
Ontologies meet Business Rules
“Spanish word for coil is bobina”
Example
AnnotationAssertion(rdfs : labelCoil”bobina”@es)
Annotations are not relevant for reasoning
A few annotation properties are predefined in OWL
Multilingual capabilities are inherited from RDF
Annotation properties can have domain, range and hierarchies
(118/221) c ONTORULE Consortium, all rights reserved
119. ONTOR UL E
Outline
Ontologies meet Business Rules
Modeling business knowledge using OWL2
Why use OWL for business knowledge?
OWL by example
Limitations
Conclusions
Rules: Logical and Production Rules
Integration of Rules and Ontologies
Demo
(119/221) c ONTORULE Consortium, all rights reserved
120. ONTOR UL E
What is Open World Assumption
Ontologies meet Business Rules
In OWA, no assumptions are made about the truth value of statements
that we do not know.
OWA ...
... assumes incomplete information by default
... is good for reusability. If we extend an ontology, all existing true
statements remain true (monotonic logic)
... does not make the Unique Name Assumption.
(120/221) c ONTORULE Consortium, all rights reserved
121. ONTOR UL E
Why should I care about OWA
Ontologies meet Business Rules
Side effects of OWA (counterintuitive behavior):
If two individuals have different names (IDs), they can be inferred to
be the same resource
Data validation for incorrect or missing values (i.e. integrity) is not
possible
Sometimes it is mandatory to explicitly declare even silly business
statements (eg. People and Places are disjoint concepts)
(121/221) c ONTORULE Consortium, all rights reserved
122. ONTOR UL E
Integrity Constraints
Ontologies meet Business Rules
“All coils must have a relation to the factory where they were
produced ”
Example
Coil ∃producedIn.Factory
Coil#12 ∈ Coil
This description is consistent even if we do not know where coil #12 was
produced. This is a side-effect of OWA.
Proposed solution:
Escalation to a Closed World Assumption (CWA) system,
implementing integrity constraints with either rules, query languages
or modal languages (K-operator)
(122/221) c ONTORULE Consortium, all rights reserved
123. ONTOR UL E
N-ary Predicates
Ontologies meet Business Rules
“Coil #12 completed production step #7 at 2010/03/12 15:20
and completed production step #14 at 2010/03/12 18:57”
OWL lacks support for n-ary predicates.
Proposed solutions:
Reification of the n-ary predicate
Change the modeling point of view
Consequences of using reification (More details later in the tutorial):
Introducing non-intuitive, non-business concepts
Syntactic verbosity
Non-transparent for applications (eg., rules or query languages)
(123/221) c ONTORULE Consortium, all rights reserved
124. ONTOR UL E
Procedural Knowledge
Ontologies meet Business Rules
“Shipment distance is the linear distance between the location
of the coil and the shipment destination. ”
Shipment distance is a calculated property, which value can not be
obtained from OWL reasoning.
Proposed solution:
Use a procedural language in combination with OWL, either an
imperative programming language such as JAVA or a declarative
one such as LP.
(124/221) c ONTORULE Consortium, all rights reserved
125. ONTOR UL E
Dynamic Knowledge
Ontologies meet Business Rules
OWL ontologies describe a stateless picture of a given business
domain. Therefore it is difficult to represent changes, business
processes, states, transitions, events, etc.
This limitation is shared with pure LP
Production rules fit much better for this purpose
(125/221) c ONTORULE Consortium, all rights reserved
126. ONTOR UL E
Outline
Ontologies meet Business Rules
Modeling business knowledge using OWL2
Why use OWL for business knowledge?
OWL by example
Limitations
Conclusions
Rules: Logical and Production Rules
Integration of Rules and Ontologies
Demo
(126/221) c ONTORULE Consortium, all rights reserved
127. ONTOR UL E
OWL in practice
Ontologies meet Business Rules
Mature authoring tools. Both commercial and open source
DL reasoners continously improving (eg.: performance)
Publicly available business ontologies are scarce (exception: Health
Science).
Internal usage of ontologies inside companies is difficult to measure
(127/221) c ONTORULE Consortium, all rights reserved
128. ONTOR UL E
OWL2 Profiles
Ontologies meet Business Rules
OWL 2 DL is a very expressive Description Logic (although
decidable).
However complexity of the reasoning algorithms (N2ExpTime)
hampers scalability
Subsets (profiles) of OWL 2 have been identified:
Still sufficiently expressive
Lower complexity (PTime/logspace)
Already available profiles:
EL profile, optimized for large terminologies
QL profile, optimized for queries
RL profile, can be implemented with rule systems
(128/221) c ONTORULE Consortium, all rights reserved
129. ONTOR UL E
OWL and SBVR
Ontologies meet Business Rules
SBVR is a very expressive language to capture complete business
models using a controlled natural language
Some parts of the SBVR business model can be formalized using
OWL ontologies
Business experts can take advantage of formal reasoning
techniques to guarantee model consistency
Business experts can take advantage of web nature of OWL and
OWA assumption for reusability of business models in several
scenarios
(129/221) c ONTORULE Consortium, all rights reserved
130. ONTOR UL E
OWL and combinations with other languages
Ontologies meet Business Rules
OWL is commonly used to build expressive, shared and reusable data
models. However OWL is not a language for writing applications.
(130/221) c ONTORULE Consortium, all rights reserved