Interactive Knowledge Stack A Software Architecture for Semantic Content Management Systems

Transcription

1 Interactive Stack A Software Architecture for Semantic Content Management Systems Fabian Christ July 2, 2012

2 Interactive Stack - IKS Started in January 2009 ends in December 2012 Funded in part by a 6.58m grant from the European Union Consortium of 7 research and 6 industrial partners 2

3 IKS Project Goals A software architecture for semantically enabled content management systems. SCMS - Semantic Content Management System Semantic User Interface Content User Interface Semantic User Interaction Presentation & Interaction Service Layer RESTful Interface Content Access Access Content Administration Content Management Content Data Model Extraction Pipelines Reasoning Models Administration Semantic Lifting Representation and Reasoning Enhancer Enhancement Engines EntityHub Ontology Manager Reasoners Rules ContentHub FactStore CMS Adapter Component Layer Content Repository Repository Persistence An open-source community to bring semantic technologies to content management system platforms. 3

4 IKS Features User Interface Library & Widgets Content Enhancement Lorem Hans dolor Entity Management Linked Data Cloud Ontology Management & Reasoning Indexing & Search 4

5 Short Demo of IKS 7.0 Content Enhancement Demo with and a VIE-based user interface. IKS Demo Server 5

6 Influence Factors on the IKS Software Architecture The design of the IKS software architecture is influenced by three factors: Functionality Implement functional requirements Technology Use state-of-the-art web technologies Support semantic web standards People Support distributed development where people can work independently 6

7 What is Semantic CMS? Functionality Traditional CMS Semantic CMS Atomic Unit Document Entity Meta Data as Strings Defined Entity Types Linked Entities Search for Strings Entities and their relations Manage Documents and their workflow Entities and their domain model 7

8 Top-Down Top-Down Requirements Functionality Requirements Analysis Architecture IKS Alpha 8

9 Functional Layers from the Description of Work Functionality Presentation and Interaction Semantic Lifting Representation and Reasoning Persistence 9

10 Content Management Functionality Functionality Content User Interface Content Access Content Administration Content Management Content Data Model Content Repository 10

11 Management Functionality Functionality Semantic User Interaction Presentation & Interaction Access Extraction Pipelines Reasoning Models Repository Administration Semantic Lifting Representation and Reasoning Persistence 11

12 Design IKS Functional Building Blocks Semantic User Interface Functionality Content User Interface Semantic User Interaction Presentation & Interaction Content Access Access Content Administration Content Management Content Data Model Extraction Pipelines Reasoning Models Administration Semantic Lifting Representation and Reasoning Content Repository Repository Persistence 12

13 Influence Factors on the IKS Software Architecture The design of the IKS software architecture is influenced by three factors: Functionality Content enhancement, entity management, ontology management, reasoning, Technology Use state-of-the-art web technologies Support semantic web standards People Support distributed development where people can work independently 13

14 Bottom-Up Bottom-Up Technology Development Technology IKS Alpha INTERPRET KReS Persistence Store FISE 14

15 Do Not Replace But Extend Technology No need to replace existing systems for content management IKS components offer service oriented integration Extend by Using Semantic Services Traditional CMS IKS Technology Stack 15

16 Service Orientation Technology The IKS offers RESTful web service interfaces Each feature is available via a simple HTTP request Enhancer Entity Manager Ontology Manager Open Linked Data Reasoner IKS Store Search 16

17 RESTful Interfaces Technology Representational State Transfer (REST) [is an] architectural style for distributed hypermedia systems. Key Aspects Stateless services Resource oriented organization of data and services Resource Client Stateless Service Call /enhancer IKS Source: Roy Thomas Fielding, Architectural Styles and the Design of Network-based Software Architectures, PhD Thesis,

18 Representation of Resources Technology REST applied to HTTP Each resource has an URI By accessing the URI the resource can be retrieved in different representations (formats) GET /enhancer Host: localhost:8080 Accept: text/html HTML GET /enhancer Host: localhost:8080 Accept: application/json JSON 18

19 RESTful Integration Technology RESTful interfaces make integration easy Required technology for sending HTTP requests is available in any traditional CMS Support for standards like the Resource Description Framework (RDF), JSON for Linked Data (JSON-LD) Traditional CMS HTTP Request HTTP Response as RDF, JSON-LD RESTful API IKS Technology Stack 19

20 Influence Factors on the IKS Software Architecture The design of the IKS software architecture is influenced by three factors: Functionality Content enhancement, entity management, ontology management, reasoning, Technology RESTful HTTP interfaces Standards like RDF, JSON-LD, People Support distributed development where people can work independently 20

21 Development Team People Distributed Germany, Turkey, Italy, Austria, Swiss, France, (Finland) Different Interests Researchers want to follow their own research topics Industrial partners want working software No central lead Map 2009 Ezilon.com Know how Java, JavaScript, Web technologies Semantic web standards 21

22 OSGi for Flexibility People IKS components are OSGi bundles REST API R Enhancer Team 1 Export E Import Enhancement Engine Team 2 R R R Entityhub Contenthub Ontology Manager Team 3 Team 4 Team 5 22

23 Common Basis People R R R Entityhub Contenthub Ontology Manager Dependency Management E E E Library A Library B Library C 23

24 Different Release Configurations People R R R IKS Variant 1 Ontology Manager Reasoner Rules R R R IKS Variant 2 Enhancer Entityhub Contenthub 24

25 Summary on Influence Factors The IKS software architecture for semantic content management systems supports Functionality Content enhancement, entity management, ontology management, reasoning, Technology RESTful HTTP interfaces Standards like RDF, JSON-LD, People OSGi bundles for distributed development OSGi bundlists for releases packaging 25

26 IKS Software Architecture VIE VIE Widgets User Interface Layer RESTful Service Layer Enhancer Reasoners Ontology Manager EntityHub FactStore Enhancement Engines Rules ContentHub CMS Adapter Common Bundles Library A Library B... Bundle Layer 26

27 Integration Patterns at Service Level Search based on enhanced content 1. Entityhub to specify entities of interest 2. Enhancer to retrieve metadata for entities 3. Contenthub storage service to store content plus enhancements 4. Contenthub keyword search service to search for previously stored content and enhancements Client 1. R R R Entityhub Enhancer Contenthub 27

28 Bottom-Up Top-Down Iterative Development Requirements Analysis Architecture Middle- Out IKS Alpha IKS 3.0, 4.0,, 7.0 IKS 8.0 INTERPRET KReS Persistence Store FISE 28

29 Lessons Learned Pros Each partner was able to contribute his functionality No central lead Ship stable configurations Allow lab mode for components Adopters select functionality they like to use Modularity big plus from industrial perspective Impact Cons Less integration at component level No shared storage Sometimes duplicate functionalities Collection of features instead of a consistent stack 29

30 Thank you for your attention. Follow s-lab Software Quality Lab Universität Paderborn Zukunftsmeile Paderborn Tel.: (05251) / info@s-lab.upb.de 30