1 / 11

Preparation for SWS Solution (WP5)

The project focuses on developing Semantic Web Services (SWS) technologies for a federated Learning Content Management System (LCMS) to improve the discovery, retrieval, sharing, and reuse of medical educational content across EU higher education institutions. By addressing the difficulty of accessing such content, the initiative aims to determine best practices for brokerage mechanisms in handling educational resources. Key tasks include defining functional requirements, designing a federated architecture, prototyping services, and evaluating automatic, context-aware discovery capabilities.

hasana
Télécharger la présentation

Preparation for SWS Solution (WP5)

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. Preparation for SWS Solution (WP5) Stefan Dietze, Hong Qing Yu, Neil Benn, John Domingue Knowledge Media Institute, The Open University, UK

  2. WP5: Semantic Web Services (SWS) technologies for federated LCMS Vision • Motivation: Currently not easy to discover and retrieve medical educational content across EU HE institutions • Solution: Federated LCMS to enable DISCOVERY, RETRIEVAL, SHARING, REUSE of medical educational content • Research Question: What is the best practice regarding the brokerage mechanism for medical educational resources?

  3. WP5: Semantic Web Services (SWS) technologies for federated LCMS Four main tasks • Functional requirements and scenarios • Design federated services-based architecture (Cf. LUISA project --- Context-Aware delivery of LOs) • Prototyping • Evaluation

  4. Automatic, context-aware: Discovery, Composition, Metadata mediation SWS vision – Service brokering architecture Application logic / Client application SWS B roker Web Service Web Service Web Service Data Data Data

  5. Applying SWS to eLearning – LUISA

  6. Results to be (partially) reused in WP5 Ontology stack for SWS-based eLearning (e.g. LPMO) SWS-based architecture (using IRS-III) Integration with IMS LD & ADL SCORM runtime environments Protoype applications, e.g. http://luisa.open.ac.uk/demo/luisa2go, http://luisa.open.ac.uk/demo/luisa Applying SWS to eLearning – LUISA project as basis for WP5

  7. But, what is a “service”? Any software functionality accessible via HTTP (e.g. to query or retrieve metadata). Simple case: http request, which produces a structured response (e.g. xml) rather than a html page SWS vision – everything is a service… Application logic / Client application SWS B roker Web Service Web Service Web Service

  8. OU Learning Object feed service example: XML feed http://gdata.youtube.com/feeds/api/users/oulearn/uploads?max-results=50 The response data is produced as a xml message “Medal” Body Mass Index Calculator (referred by AUTH): http://www.medal.org/OnlineCalculators/ch2/ch2.05/ch2.05.02.php (But non-structured response so not strictly YET a service) Web Trace (UNICT) Enroll Student Unenroll Student SWS vision – everything is a service… Application logic / Client application

  9. ... 2nd Step – Abstracting from services (3/3) … Currently we are also trying to develop a online service annotation and registration editor/form which allow service providers to publish their services with semantic annotations. However, this is an on going work. SWS vision – everything is a service… Application logic / Client application

  10. Outlook – Next steps & open issues WP5 roles: OU: Interoperability between services & metadata via SWS brokerage WP5 participants: provisioning of services (particularly all content providers), use case scenarios Further tasks: application layer/GUI, evaluation… ? Open questions: Individual partner responsibilities? Input/collaboration with other WPs, particular WP4? 10

  11. [ http://kmi.open.ac.uk ] [ http://www.open.ac.uk ] 11

More Related