{"product_id":"semantic-web-and-modeldriven-engineering-9781118004173","title":"Semantic Web and ModelDriven Engineering","description":"\u003cb\u003eBook Synopsis\u003c\/b\u003e\u003cbr\u003eThe next enterprise computing era will rely on the synergy between both technologies: semantic web and model-driven software development (MDSD). The semantic web organizes system knowledge in conceptual domains according to its meaning. It addresses various enterprise computing needs by identifying, abstracting and rationalizing commonalities, and checking for inconsistencies across system specifications. On the other side, model-driven software development is closing the gap among business requirements, designs and executables by using domain-specific languages with custom-built syntax and semantics. It focuses on using modeling languages as programming languages.\u003cbr\u003e \u003cbr\u003e   \u003cp\u003eAmong many areas of application, we highlight the area of configuration management. Consider the example of a telecommunication company, where managing the multiple configurations of network devices (routers, hubs, modems, etc.) is crucial. Enterprise systems identify and document the functional and physica\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTable of Contents\u003c\/b\u003e\u003cbr\u003e\u003c\/p\u003e\u003cp\u003eList of Figures xv\u003c\/p\u003e \u003cp\u003eList of Tables xix\u003c\/p\u003e \u003cp\u003eForeword xxi\u003c\/p\u003e \u003cp\u003ePreface xxiii\u003c\/p\u003e \u003cp\u003eAcronyms xxvii\u003c\/p\u003e \u003cp\u003e\u003cb\u003ePart I Fundamentals\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003e1 Introduction 3\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e1.1 Motivation 3\u003c\/p\u003e \u003cp\u003e1.2 Research Questions 5\u003c\/p\u003e \u003cp\u003e\u003cb\u003e2 Model-Driven Engineering Foundations 9\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e2.1 Introduction 9\u003c\/p\u003e \u003cp\u003e2.2 Model-Driven Engineering Structure 9\u003c\/p\u003e \u003cp\u003e2.2.1 Models 11\u003c\/p\u003e \u003cp\u003e2.2.2 Metamodels 11\u003c\/p\u003e \u003cp\u003e2.2.3 Modeling Languages 13\u003c\/p\u003e \u003cp\u003e2.2.4 Model Transformations 17\u003c\/p\u003e \u003cp\u003e2.2.5 Query Languages 17\u003c\/p\u003e \u003cp\u003e2.3 Technical Spaces 19\u003c\/p\u003e \u003cp\u003e2.4 Conclusion 20\u003c\/p\u003e \u003cp\u003e\u003cb\u003e3 Ontology Foundations 21\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e3.1 Introduction 21\u003c\/p\u003e \u003cp\u003e3.2 Ontology 22\u003c\/p\u003e \u003cp\u003e3.2.1 Ontology Modeling 22\u003c\/p\u003e \u003cp\u003e3.3 The Ontology Web Language 24\u003c\/p\u003e \u003cp\u003e3.3.1 OWL 2 Syntax 24\u003c\/p\u003e \u003cp\u003e3.3.2 OWL 2 Semantics 27\u003c\/p\u003e \u003cp\u003e3.3.3 World Assumption and Name Assumption 27\u003c\/p\u003e \u003cp\u003e3.4 Ontology Services 31\u003c\/p\u003e \u003cp\u003e3.4.1 Reasoning Services 31\u003c\/p\u003e \u003cp\u003e3.4.2 Querying 31\u003c\/p\u003e \u003cp\u003e3.5 Ontology Engineering Services 33\u003c\/p\u003e \u003cp\u003e3.5.1 Explanation 33\u003c\/p\u003e \u003cp\u003e3.5.2 Ontology Matching 34\u003c\/p\u003e \u003cp\u003e3.6 Rules 34\u003c\/p\u003e \u003cp\u003e3.7 Metamodels for Ontology Technologies 35\u003c\/p\u003e \u003cp\u003e3.7.1 OWL Metamodels 35\u003c\/p\u003e \u003cp\u003e3.7.2 SPARQL Metamodel 40\u003c\/p\u003e \u003cp\u003e3.8 Ontological Technical Spaces 41\u003c\/p\u003e \u003cp\u003e3.9 Conclusion 43\u003c\/p\u003e \u003cp\u003e\u003cb\u003e4 Marrying Ontology and Model-Driven Engineering 44\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e4.1 Introduction 44\u003c\/p\u003e \u003cp\u003e4.2 Similarities between OWL Modeling and UML Class-Based Modeling 45\u003c\/p\u003e \u003cp\u003e4.3 Commonalities and Variations 46\u003c\/p\u003e \u003cp\u003e4.3.1 Language 47\u003c\/p\u003e \u003cp\u003e4.3.2 Formalism 49\u003c\/p\u003e \u003cp\u003e4.3.3 Data Model 49\u003c\/p\u003e \u003cp\u003e4.3.4 Reasoning 50\u003c\/p\u003e \u003cp\u003e4.3.5 Querying 51\u003c\/p\u003e \u003cp\u003e4.3.6 Rules 51\u003c\/p\u003e \u003cp\u003e4.3.7 Transformation 52\u003c\/p\u003e \u003cp\u003e4.3.8 Mediation 52\u003c\/p\u003e \u003cp\u003e4.3.9 Modeling Level 53\u003c\/p\u003e \u003cp\u003e4.4 The State of the Art of Integrated Approaches 54\u003c\/p\u003e \u003cp\u003e4.4.1 Model Validation 54\u003c\/p\u003e \u003cp\u003e4.4.2 Model Enrichment 56\u003c\/p\u003e \u003cp\u003e4.4.3 Ontology Modeling 58\u003c\/p\u003e \u003cp\u003e4.5 Existing Work on Classifying Integrated Approaches 58\u003c\/p\u003e \u003cp\u003e4.6 Conclusion 59\u003c\/p\u003e \u003cp\u003eConclusion of Part I\u003c\/p\u003e \u003cp\u003e\u003cb\u003ePart II The TwoUse Approach\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003e5 The TwoUse Conceptual Architecture 65\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e5.1 Introduction 65\u003c\/p\u003e \u003cp\u003e5.2 Requirements for Integrating Ontology Technologies and Model-Driven Engineering 66\u003c\/p\u003e \u003cp\u003e5.2.1 Usage of Ontology Services in MDE 66\u003c\/p\u003e \u003cp\u003e5.2.2 Usage of MDE Techniques in OWL Ontology Engineering 67\u003c\/p\u003e \u003cp\u003e5.3 Addressing the Requirements with the TwoUse Approach 68\u003c\/p\u003e \u003cp\u003e5.4 Metamodeling Architecture 70\u003c\/p\u003e \u003cp\u003e5.4.1 The TwoUse Metamodel 70\u003c\/p\u003e \u003cp\u003e5.5 Syntax 72\u003c\/p\u003e \u003cp\u003e5.5.1 UML Profile for OWL 72\u003c\/p\u003e \u003cp\u003e5.5.2 Pure UML Class Diagrams 75\u003c\/p\u003e \u003cp\u003e5.5.3 Textual Notation 75\u003c\/p\u003e \u003cp\u003e5.6 Conclusion 77\u003c\/p\u003e \u003cp\u003e\u003cb\u003e6 Query Languages for Integrated Models 78\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e6.1 Introduction 78\u003c\/p\u003e \u003cp\u003e6.2 Combining Existing Approaches 78\u003c\/p\u003e \u003cp\u003e6.3 Querying Ontologies Using OWL Syntax: SPARQLAS 80\u003c\/p\u003e \u003cp\u003e6.3.1 SPARQLAS Concrete Syntax 80\u003c\/p\u003e \u003cp\u003e6.3.2 SPARQLAS Metamodel 81\u003c\/p\u003e \u003cp\u003e6.3.3 Transformation from SPARQLAS to SPARQL 81\u003c\/p\u003e \u003cp\u003e6.4 Querying Integrated Models: SPARQLAS4TwoUse 82\u003c\/p\u003e \u003cp\u003e6.5 Conclusion 84\u003c\/p\u003e \u003cp\u003e\u003cb\u003e7 The TwoUse Toolkit 86\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e7.1 Introduction 86\u003c\/p\u003e \u003cp\u003e7.2 Use Case Descriptions 87\u003c\/p\u003e \u003cp\u003e7.3 A Generic Architecture for MDE and Ontology Engineering 87\u003c\/p\u003e \u003cp\u003e7.3.1 Core Services 88\u003c\/p\u003e \u003cp\u003e7.3.2 Engineering Services 89\u003c\/p\u003e \u003cp\u003e7.3.3 Front-End 90\u003c\/p\u003e \u003cp\u003e7.4 Instantiating the Generic Model-Driven Architecture: The TwoUse Toolkit 90\u003c\/p\u003e \u003cp\u003e7.5 Conclusion 93\u003c\/p\u003e \u003cp\u003eConclusion of Part II\u003c\/p\u003e \u003cp\u003e\u003cb\u003ePart III Applications in Model-Driven Engineering\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003e8 Improving Software Design Patterns with Owl 99\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e8.1 Introduction 99\u003c\/p\u003e \u003cp\u003e8.2 Case Study 100\u003c\/p\u003e \u003cp\u003e8.2.1 Applying the Strategy Pattern 100\u003c\/p\u003e \u003cp\u003e8.2.2 Extending to the Abstract Factory 101\u003c\/p\u003e \u003cp\u003e8.2.3 Drawbacks 103\u003c\/p\u003e \u003cp\u003e8.3 Application of the TwoUse Approach 104\u003c\/p\u003e \u003cp\u003e8.3.1 OWL for Conceptual Modeling 104\u003c\/p\u003e \u003cp\u003e8.3.2 TwoUse for Software Design Patterns: The Selector Pattern 105\u003c\/p\u003e \u003cp\u003e8.4 Validation 109\u003c\/p\u003e \u003cp\u003e8.4.1 Participants and Collaborations 109\u003c\/p\u003e \u003cp\u003e8.4.2 Applicability 110\u003c\/p\u003e \u003cp\u003e8.4.3 Drawbacks 110\u003c\/p\u003e \u003cp\u003e8.4.4 Advantages 110\u003c\/p\u003e \u003cp\u003e8.5 Related Work 111\u003c\/p\u003e \u003cp\u003e8.6 Conclusion 111\u003c\/p\u003e \u003cp\u003e\u003cb\u003e9 Modeling Ontology-Based Information Systems 112\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e9.1 Introduction 112\u003c\/p\u003e \u003cp\u003e9.2 Case Study 113\u003c\/p\u003e \u003cp\u003e9.2.1 UML Class-Based Software Development 113\u003c\/p\u003e \u003cp\u003e9.2.2 Ontology-Based Software Development 116\u003c\/p\u003e \u003cp\u003e9.3 Application of the TwoUse Approach 117\u003c\/p\u003e \u003cp\u003e9.3.1 Concrete Syntax 118\u003c\/p\u003e \u003cp\u003e9.3.2 Abstract Syntax 119\u003c\/p\u003e \u003cp\u003e9.3.3 Querying 121\u003c\/p\u003e \u003cp\u003e9.4 Validation 121\u003c\/p\u003e \u003cp\u003e9.4.1 Limitations 123\u003c\/p\u003e \u003cp\u003e9.5 Conclusion 123\u003c\/p\u003e \u003cp\u003e\u003cb\u003e10 Enabling Linked Data Capabilities to MOF Compliant Models 124\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e10.1 Introduction 124\u003c\/p\u003e \u003cp\u003e10.2 Case Study 125\u003c\/p\u003e \u003cp\u003e10.2.1 Requirements 127\u003c\/p\u003e \u003cp\u003e10.3 Application of the TwoUse Approach 128\u003c\/p\u003e \u003cp\u003e10.3.1 Model Extension 128\u003c\/p\u003e \u003cp\u003e10.3.2 Model Transformation 130\u003c\/p\u003e \u003cp\u003e10.3.3 Matching 131\u003c\/p\u003e \u003cp\u003e10.3.4 Querying with SPARQLAS 131\u003c\/p\u003e \u003cp\u003e10.4 Validation 132\u003c\/p\u003e \u003cp\u003e10.4.1 Limitations 134\u003c\/p\u003e \u003cp\u003e10.5 Related Work 134\u003c\/p\u003e \u003cp\u003e10.6 Conclusion 135\u003c\/p\u003e \u003cp\u003eConclusion of Part III\u003c\/p\u003e \u003cp\u003e\u003cb\u003ePart IV Applications in the Semantic Web\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003e11 Model-Driven Specification of Ontology Translations 141\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e11.1 Introduction 141\u003c\/p\u003e \u003cp\u003e11.2 Case Study 142\u003c\/p\u003e \u003cp\u003e11.3 Application of the TwoUse Approach 145\u003c\/p\u003e \u003cp\u003e11.3.1 Concrete Syntax 145\u003c\/p\u003e \u003cp\u003e11.3.2 Metamodels 146\u003c\/p\u003e \u003cp\u003e11.3.3 Model Libraries 148\u003c\/p\u003e \u003cp\u003e11.3.4 Semantics 148\u003c\/p\u003e \u003cp\u003e11.3.5 Ontology Translation Process 148\u003c\/p\u003e \u003cp\u003e11.3.6 Implementation 149\u003c\/p\u003e \u003cp\u003e11.4 Examples 150\u003c\/p\u003e \u003cp\u003e11.5 Analysis 153\u003c\/p\u003e \u003cp\u003e11.6 Related Work 154\u003c\/p\u003e \u003cp\u003e11.7 Conclusion 155\u003c\/p\u003e \u003cp\u003e\u003cb\u003e12 \u003c\/b\u003e\u003cb\u003eAutomatic Generation of OntologyAPIs156\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e12.1 Introduction 156\u003c\/p\u003e \u003cp\u003e12.2 Case Study 158\u003c\/p\u003e \u003cp\u003e12.3 Application of the TwoUse Approach 161\u003c\/p\u003e \u003cp\u003e12.3.1 Key Domain Concepts 161\u003c\/p\u003e \u003cp\u003e12.3.2 \u003ci\u003eagogo \u003c\/i\u003eConcrete Syntax by Example 163\u003c\/p\u003e \u003cp\u003e12.3.3 Implementation 166\u003c\/p\u003e \u003cp\u003e12.4 Analysis 167\u003c\/p\u003e \u003cp\u003e12.5 Related Work 169\u003c\/p\u003e \u003cp\u003e12.6 Conclusion 170\u003c\/p\u003e \u003cp\u003e\u003cb\u003e13 \u003c\/b\u003e\u003cb\u003eUsing Templates in Owl Ontologies 171\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e13.1 Introduction 171\u003c\/p\u003e \u003cp\u003e13.2 Case Study 172\u003c\/p\u003e \u003cp\u003e13.3 Application of the TwoUse Approach 174\u003c\/p\u003e \u003cp\u003e13.3.1 Extending the OWL Metamodel with Templates 174\u003c\/p\u003e \u003cp\u003e13.3.2 Semantics of Templates 177\u003c\/p\u003e \u003cp\u003e13.3.3 Notations for Templates in OWL 179\u003c\/p\u003e \u003cp\u003e13.3.4 Query Templates 180\u003c\/p\u003e \u003cp\u003e13.4 Analysis 181\u003c\/p\u003e \u003cp\u003e13.4.1 Limitations 182\u003c\/p\u003e \u003cp\u003e13.5 Related Work 182\u003c\/p\u003e \u003cp\u003e13.6 Conclusion 183\u003c\/p\u003e \u003cp\u003eConclusion of Part IV\u003c\/p\u003e \u003cp\u003e\u003cb\u003e14 Conclusion 187\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e14.1 Contributions 187\u003c\/p\u003e \u003cp\u003e14.2 Outlook 189\u003c\/p\u003e \u003cp\u003e14.2.1 Ongoing Research 189\u003c\/p\u003e \u003cp\u003e\u003cb\u003eAppendix A 191\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eA.1 EBNF Defi nition of the Concrete Textual Syntax for TwoUse 191\u003c\/p\u003e \u003cp\u003eA.2 EBNF Grammar of SPARQLAS Functional Syntax 192\u003c\/p\u003e \u003cp\u003eA.3 EBNF Grammar of SPARQLAS Manchester Syntax 197\u003c\/p\u003e \u003cp\u003eA.4 SPARQLAS Metamodel 202\u003c\/p\u003e \u003cp\u003eA.5 Ecore to OWL: Translation Rules 204\u003c\/p\u003e \u003cp\u003e\u003cb\u003eAppendix B206\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eB.1 Use Cases 206\u003c\/p\u003e \u003cp\u003eB.1.1 Design Integrated Models 206\u003c\/p\u003e \u003cp\u003eB.1.2 Design Integrated UML Class Diagram 206\u003c\/p\u003e \u003cp\u003eB.1.3 Design Integrated Ecore Model 207\u003c\/p\u003e \u003cp\u003eB.1.4 Specify SPARQLAS4TwoUse Query Operations 207\u003c\/p\u003e \u003cp\u003eB.1.5 Transform to OWL 207\u003c\/p\u003e \u003cp\u003eB.1.6 Compute Alignments 208\u003c\/p\u003e \u003cp\u003eB.1.7 Browse 208\u003c\/p\u003e \u003cp\u003eB.1.8 Explain Axioms 209\u003c\/p\u003e \u003cp\u003eB.1.9 Query UML Class-Based Models 209\u003c\/p\u003e \u003cp\u003eB.1.10 Query OWL Ontologies 209\u003c\/p\u003e \u003cp\u003eB.1.11 Design Ontology Engineering Services 209\u003c\/p\u003e \u003cp\u003eB.1.12 Design Ontology API 210\u003c\/p\u003e \u003cp\u003eB.1.13 Design Ontology Translation 210\u003c\/p\u003e \u003cp\u003eB.1.14 Design Ontology Template 210\u003c\/p\u003e \u003cp\u003eB.1.15 Generate Service 211\u003c\/p\u003e \u003cp\u003eB.2 Connecting Use Cases with Requirements 211\u003c\/p\u003e \u003cp\u003eReferences 212\u003c\/p\u003e \u003cp\u003eIndex 226             \u003c\/p\u003e","brand":"Wiley-Blackwell","offers":[{"title":"Default Title","offer_id":53515635261783,"sku":"9781118004173","price":62.06,"currency_code":"GBP","in_stock":true}],"url":"https:\/\/bookcurl.com\/products\/semantic-web-and-modeldriven-engineering-9781118004173","provider":"Book Curl","version":"1.0","type":"link"}