Case Studies for Semantic Web Portal Technologies

1. Case Studies for Semantic Web Portal Technologies Anna V. Zhdanova DERI-Innsbruck, 8 March 2004

2. Overview • Introduction • Case study 1 (semanticweb.org) • Case study 2 (eTourism) • Case study 3 (PeopleSearch&Compare) • Conclusions Note: Case study is also referred as CS further

3. General Picture We are here, thus applications of SW-portal technologies are needed

4. Why case studies and specifications are mutually useful Specifications help case studies to become real Case studies help specifications to become perfect

5. Basic FacilitiesCase Study 1: SemanticWeb.org • “We aim to bring together research groups, research projects, software developers and user communities in the Semantic Web area.” – Mission statement • Basic facilities should support whatever was meant

6. Target Domain/Our Expertise in It Case Study 1: SemanticWeb.org • Domain is not really popular, very narrow (but deep ) • P2P • We are the experts here! No external expertise is needed

7. What’s Cool?Case Study 1: SemanticWeb.org • It will be possible to say that semanticweb.org is a Semantic Web portal 

8. How Will It Be Achieved? Case Study 1: SemanticWeb.org DERI-Galway will take care and do all the work with assistance of DERI-Innsbruck on common parts/technologies in intersection-of(CS1, union-of(CS2, CS3)) .

9. ExtensionsCase Study 1: SemanticWeb.org • Extensive merging into “institute” (DERI) portal • Reuse of the same techniques in any other research community portal

10. Basic FacilitiesCase Study 2: eTourism • Allow tourism businesses to advertise themselves effectively (semantic annotation) • Allow tourist to find precisely what they want (intelligent search) For: Satisfying specific tourist needs, e.g. “I want a room with kitchen facilities In a hotel in Tirol not far from Axamer Lizum and with a boat rental nearby.”

11. Target Domain/Our Expertise in It Case Study 2: eTourism • Domain of tourism is popular, broad, especially relevant to Austria • B2C • We are not experts in tourism => Austrian companies working in tourism are to be involved for ontology adaptation, development and usage of portal in general

12. What’s Cool?Case Study 2: eTourism • Usefulness of having a semantic annotation for a specific hotel, restaurant or other tourist businesses • WORM: Modify it once, and the changes are automatically communicated to all systems that use this data • It can be used by services that generate/update automatically businesses’ web-pages – isn’t it nice? • It will be used in the eTourism portal to advertise businesses • Businesses will get annotated easily (relatively): usage of linguistic tools is expected • Multilingual access

13. How Will It Be Achieved?Case Study 2: eTourism • DERI-Innsbruck will take care and do all the work with assistance of DERI-Galway on common parts/technologies in intersection-of(CS1, union-of(CS2, CS3)) . • Cooperation with Mondeca on using ITM and with VisioLab on using general ontology on tourism • Cooperation with local Austrian tourist companies on local tourism issues

14. ExtensionsCase Study 2: eTourism • Web-services: This case study is planned to be aligned with the eTourism case study in WSMO. WSMO eTourism case study will enrich eTourism SW portal case study with dynamic features such as support for making reservations for train tickets or hotels.

15. Basic FacilitiesCase Study 3: PeopleSearch&Compare • Allow users to say whatever they want about themselves (semantic annotation, collaborative ontology engineering) • Allow users to find whatever whoever said about themselves (intelligent search) For: search of a friend, date, boss, employee, relative, ex-classmate, etc. compare anyone with others: self-assessment, staff evaluation, etc.

16. Target Domain/Our Expertise in It Case Study 3: PeopleSearch&Compare • Domain is highly popular, also the most broad domain of the existing ones • P2P • We are not really experts… but have understanding why people may need to search over and compare people’s profiles => external expertise is not necessary (at least in the beginning)

17. Usefulness of having a personal semantic annotation WORM: Modify it once, and the changes are automatically communicated to all systems that use your personal data It can be used by services that generate/update automatically your web-page or CV – isn’t it nice? It will be used in the people’s portal to connect people High flexibility in what can be specified Users do not just passively fill in specified slots, but also collaborativelyextend an ontology that describes anyimaginable aspect of a class “Person” What’s Cool? Case Study 3: PeopleSearch&Compare

18. How Will It Be Achieved?Case Study 3: PeopleSearch&Compare DERI-Innsbruck will take care and do all the work with assistance of DERI-Galway on common parts/technologies in intersection-of(CS1, union-of(CS2, CS3)) .

19. Web-services: Using Web-services to search/compare people’s profiles Extensive merging into “institute” (DERI) portal – in terms of representation of information about people, their skills Personal information exchange and personnel evaluation at an enterprise ExtensionsCase Study 3: PeopleSearch&Compare

20. Added value of metadata(Adapted to CS3)

21. Directions for Developmentin CS1, CS2, CS3 (more or less)

22. The end (so far)