1 / 20

Modeling User Input and Hypermedia Dynamics in Hera

Modeling User Input and Hypermedia Dynamics in Hera. Databases and Hypermedia Group. Outline. Modern WIS Hypermedia Dynamics Hera Modeling Dynamics in Hera (Example) Implementation Conclusion. Modern WIS. Have broad and heterogeneous audience

lindachandler
Download Presentation

Modeling User Input and Hypermedia Dynamics in Hera

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Modeling User Input and Hypermedia Dynamics in Hera Databases and Hypermedia Group

  2. Outline • Modern WIS • Hypermedia Dynamics • Hera • Modeling Dynamics in Hera (Example) • Implementation • Conclusion

  3. Modern WIS • Have broad and heterogeneous audience • Have typically distributed and heterogeneous data sources • Provide complex services • Adapt to concrete users, groups • Adapt to concrete environments (communication channels, user devices)

  4. Hypermedia Dynamics • What is the functionality of WIS, what services do they offer (business logic) • How users interact with WIS, what is the navigation structure, how users input information (navigation structure) • How user’s actions influence hypermedia presentation of WIS (e.g. personalization)

  5. Hera Methodology • Model-driven methodology, defines design phases: • Conceptual Design that results in Conceptual Model (CM, describes data content used for generation of hypermedia presentations) construction • Application Design that results in Application Model (AM, describes the navigation structure and functionality) construction • Presentation Design that results in Presentation Model (PM, describes spatial layout and rendering of hypermedia presentations) construction

  6. Hera Models • Fully specify dynamic hypermedia applications; hence, there is no need of additional programming • Are used by a generic Hera engine for generation of hypermedia application pages (by on-demand instantiations of model subsets)

  7. Conceptual Model • Defines the data content in terms of RDFS (concepts, attributes, properties)

  8. Application Model • Navigation structure of a hypermedia application on top of CM • Hypermediadynamics (navigation structure updates and application functionality) of a hypermedia application

  9. Navigation Structure in Application Model • Navigation nodes (pages) specification in terms of slices (collections of concepts’ attributes to be displayed) • Node composition in terms of slice aggregation relationships • Navigation edges (hyperlinks) in terms of slice references

  10. Dynamics in Application Model • User input specification in terms of Input Forms • Application context (state) specification in terms of Application Context Model • Context manipulation specification in terms of queries

  11. Application Context Model • Extends CM with additional data structures needed for application functionality (to store application/navigation state, user inputs, user model, etc.) • Example: storing the user selection (shopping basket)

  12. Slices • Meaningful collection of attributes of one or more related concepts • Represent a presentation page or its part

  13. Input Forms • Specify user data entries; contain sets of input fields with: • Input method (selection from offered items, text input, etc.) • How the offered items are created (for selections) • Determine data manipulation operation associated with a form (form processing)

  14. AM Example

  15. Data Manipulations • Update application context information • Defined as SeRQL queries • Used for processing forms (handle user input) • Q1 creates instances of SelectedPainting according to the SelectForm form content CONSTRUCT {P}<rdf:type>{acm:SelectedPainting>} FROM {P}<rdf:type>{cm:Painting}; <cm:aname>{Paname} WHERE Paname IN SELECT Faname FROM {SF}<form:aname>{Faname}, {SF}<rdf:ID>{FormName} WHERE FormName = “SelectForm” creates

  16. Hera Architecture • Defines how the models are used for automatic generation of hypermedia presentation

  17. Hera Implementation • HPG 2.0 (Hera Presentation Generator, dynamic version) implemented in Java as a servlet • Uses RDF API HP Jena for RDF data transformations based on RDFS models (CM, AM) • Can use XForms processor • Uses Sesame as main content repository and application context repository; uses SeRQL/RQL as query languages • Set of graphical tools for designers for CM and AM based on Visio

  18. Conclusion • Advantages of Hera approach: • It is Model-driven; leads to a good separation of concerns • Uses Semantic Web specification languages; models are flexible and have explicit semantics, easy to check for consistency and correctness • No need of extra programming; all aspects of a designed system are captured in high-level models

  19. Future Work • Going towards higher level functional specification, e.g. rules instead of queries • Using OWL (DL) model specification for higher expressive power and possibility of reasoning on models (consistency and correctness checking) • Incorporating web services into WIS applications • Using possible separate (configurable) Hera components, like adaptation component, presentation component in different legacy systems

  20. Questions?

More Related