1. July 06, 2006DB&IS 20061 Building Web Information Systems using Web Services Flavius Frasincar frasincar@few.eur.nl Erasmus University Rotterdam Eindhoven University of Technology

2. July 06, 2006DB&IS 20062 Contents Motivation Solution I Hera Methodology –Conceptual Model –Application Model –Presentation Model –Adaptation Model II Hera Web Service-Oriented Architecture –Data Service –Presentation Service –Profile Service –Adaptation Service Conclusions

3. July 06, 2006DB&IS 20063 Motivation There is a large amount of data that needs to be presented by Web Information Systems (WIS) The user wants to access a WIS using different devices There is an increasing need to personalize WIS based on the user preferences There is a need to make WIS interoperable: –Information available outside the organization –Computational power outside the organization

4. July 06, 2006DB&IS 20064 Solution Model-driven methodology for designing WIS: –Better understanding of the system by stakeholder –Reuse of previously defined models –Checking the validity/consistency of/between models –Automatic presentation generation –System’s maintainability Distributed architecture based on Web Services (WS): –Cross-platform applications –Cross-language applications –Loosely coupled components: robust applications –Reuse of existing WS

5. July 06, 2006DB&IS 20065 I Hera Methodology Conceptual Model: –Specifies the input data Application Model: –Defines the navigational aspects of the presentation of the input data Presentation Model: –Describes the layout and style information of the presentation Adaptation Model: –Gives the presentation customization based on user/platform features All models are represented in RDF(S)

6. July 06, 2006DB&IS 20066 RDF(S) The foundation language of the Semantic Web Flexible (schema refinement and descriptions enrichment) Extensible (allows the definition of new resources/properties) Fosters interoperability (makes model semantics explicit) Compact representations (intensional information) Reuse of existing vocabularies: –Domain models (museum descriptions from TOPIA project) –User profiles (User Agent Profile from mobile phone industry)

7. July 06, 2006DB&IS 20067 Adaptation Model User/Platform Profile: stores device capabilities and user preferences User/Platform Profile is an extended version of the User Agent Profile (UAProf), a Composite Capability/Preference Profile (CC/PP) vocabulary Appearance conditions: presence/absence of an element in a model Hera models are overlay models: presence/absence of an element in a model implies its presence/absence in all subsequent models

8. July 06, 2006DB&IS 20068 User/Platform Model

9. July 06, 2006DB&IS 20069 Conceptual Model (CM) Describes the data’s schema Based on the notion of a concept, an entity specific to a particular domain CM is a hierarchy of concepts relevant within the given domain Concept properties are: –Attributes: refer to media items that characterize a concept (media types are based on MPEG-7) –Relationships: refer to other concepts

10. July 06, 2006DB&IS 200610 Conceptual Model (CM)

11. July 06, 2006DB&IS 200611 Adaptation in CM

12. July 06, 2006DB&IS 200612 Application Model (AM) Captures the logical (navigational) aspects of the presentation Based on the concept of a slice, a meaningful presentation unit which contains attributes and possibly other slices AM is a hierarchy of slices A slice is associated to a concept from CM Slice properties are: –Aggregations: a slice embeds another slice or a set of slices –References: link abstraction

13. July 06, 2006DB&IS 200613 Application Model (AM)

14. July 06, 2006DB&IS 200614 Adaptation in AM

15. July 06, 2006DB&IS 200615 Presentation Model (PM) Defines the look-and-feel aspects of the presentation Based on the concept of a region, an abstraction for a rectangular part of a display area PM is a hierarchy of regions A region is associated to a slice from AM, and has a layout and a style: –A layout defines the positioning of regions in another region –A style defines the font characteristics (size, color, etc.) Region relationships are: –Aggregations: a region embeds another region or a set of regions –References: link abstraction

16. July 06, 2006DB&IS 200616 Presentation Model (PM)

17. July 06, 2006DB&IS 200617 Layout and Layout-related Region Attributes

18. July 06, 2006DB&IS 200618 Adaptation in PM

19. July 06, 2006DB&IS 200619 Presentation in Browsers (1/2) HTML for PCSMIL

20. July 06, 2006DB&IS 200620 Presentation in Browsers (2/2) HTML for PDAWML

21. July 06, 2006DB&IS 200621 II Web Services Shape: interface Color: data types Web Service

22. July 06, 2006DB&IS 200622 Hera Web Service-Oriented Architecture

23. July 06, 2006DB&IS 200623 Data Service - WSDL

24. July 06, 2006DB&IS 200624 Presentation Service

25. July 06, 2006DB&IS 200625 SOAP Messages

26. July 06, 2006DB&IS 200626 Implementation Data transformations: –Model adaptation (CM, AM, PM) –Convert one model instance into another model instance (CMI->AMI->PMI) –Presentation generation (PMI to HTML/SMIL/cHTML/WML) XSLT stylesheets specify the transformations between the RDF/XML serialization of RDF(S) models Java code operating on RDF models instead of their RDF/XML serialization

27. July 06, 2006DB&IS 200627 XSLT vs. Java XSLT stylesheetsJava code declarative imperative + loosely-coupled, changing the system can be done by changing one stylesheet –strongly-coupled, internal dependencies make the system harder to change + easy to understand–more difficult to understand – no IDE+many IDEs – limited exploitation of RDFS semantics +full exploitation of RDFS semantics – XSLT processor offers little support for optimization +custom software which can be optimized better

28. July 06, 2006DB&IS 200628 Tools Data transformations: –Saxon (XSLT processor) –Jena (for RDF processing) Java Web Services: Axis –SOAP monitor –Java2WSDL Servlets support: Tomcat Browsers: –Internet Explorer –Real Player –Microsoft Pocket PC –Deck-it

29. July 06, 2006DB&IS 200629 Conclusions Hera methodology: –Is a model-driven methodology for designing WIS –Facilitates adaptation at conceptual, navigation, and presentation level –Uses Semantic Web technologies: RDF, RDF(S) –Has an implementation based on Web Services Future work: –Separation of the current Presentation Service in two services: Application Service and Presentation Service –Implementation of conceptual model adaptation –Dynamic construction of a WIS based on existing WS