1. Dynamic Hypermedia Generations through a Mediator using CRM and Web Service Jen-Shin Hong National ChiNan University,Taiwan jshong@ncnu.edu.tw

2. From digital archives to aesthetic hypermedia exhibitions Integrating distributed digital archives –focus on exhibition semantic template design methodology for developing auxiliary tools for exhibition design –using CRM as a mediating ontology –integrate the digital archives into E-Commerce chain using Web Service Styling for aesthetic hypermedia presentations –transform XML-based exhibition document into aesthetic hypermedia exhibitions –based on a fine-grained modularization framework for hypermedia authoring –now marching towards intelligent styling technologies Example scenario: Find, in all digital archives, all the photos and descriptions of Chang Kai-shek, the photos of his mother, …, and then automatically generate aesthetic hypermedia exhibitions.

3. DEMO Framework for generating exhibition XML document

4. Modularization framework for hypermedia presentations

5. Intelligent styling

6. Overall Framework

7. Web Service, SOAP, WSDL, UDDI Client Server SOAP Client SOAP Service WSDL document interact

8. Approach 1 for mediator design transform digital archives into repositories of RDF statements each digital archive need a mapping from its XML schema this approach facilitates the implementation of the mediator

9. Example scenario in approach 1 –A client send a request to the mediator to ask for information about a “E21.person” instance –The mediator extract and integrate all relevant RDF statements relevant to the E21.person instance Client (C) Mediator Museum DA SOAP RDF statements embedded in SOAP SOAP RDF statements embedded in SOAP WSDL E21.Person person’s name

10. each digital archive implements a Web Service based on its own XML metadata schema such Web Service for each archive is easy to implement need complex query rewriting in the mediator for querying each digital archive Approach 2 for mediator design

11. Query model design in detail Step 1: define essential atomic concepts for each CRM entity ( e.g., E21.person: mother, sibling, children, photographer, photo, text…) Step 2: map each atomic concept to a CRM path and choose essential constraints for each concept Step 3: formulate the query by concatenating the primitive daily concepts and specify the value of the constraints –e.g.: photo((mother(a person))) Constraint: taken at 1965 –e.g.: text(sibling(mother(a person))) Constraint: male –e.g: a person’s child’s photographer’s mother’s text descriptions …

12. Example scenario 1 example query: find the mother’s name of John Doe atomic concept: mother CRM path for mother –E21.Person (John Doe)  P98B.was_born  E67.Birth  P96F.by_mother  E21.Person (mother’s name) Constraint- not necessary in such query

13. query: find the children’s names of John Doe atomic concept: child CRM path for child –E21.Person (John Doe)  P96B.gave_birth  E67.Birth  P98F.brought_into_life  E21.Person (child’s name) constraints E67.Birth: –P7F.took_place_at (birth place- who was born at Taiwan) –P10F.falls_within (birth time- who was born within 2nd war) –… E21.Person (2nd) –P76F.has_contact_point (current address: who currently stay in Taiwan) –P107B.is_current_or_former_member_of (organization, who is with National Taiwan University) –… Example scenario 2

14. Issues to be explored further derive the CRM paths and choose essential constraints for more atomic concepts mapping digital archives to CRM based on WSDL? temporal and spatial reasoning performance and scalability issue approach 2: query rewriting in the mediator