1 / 7

Extensible LD Service Element & Hybrid P2P/Server Runtime Architecture

Extensible LD Service Element & Hybrid P2P/Server Runtime Architecture. Bill Olivier Development Director, Systems and Technology JISC. Extensible Service Proposal. The problem: Many new services are becoming available… How many can we support in LD?

shalom
Download Presentation

Extensible LD Service Element & Hybrid P2P/Server Runtime Architecture

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. Extensible LD Service Element&Hybrid P2P/ServerRuntime Architecture Bill Olivier Development Director,Systems and TechnologyJISC

  2. Extensible Service Proposal The problem: • Many new services are becoming available… • How many can we support in LD? • How should a new service be included in LD? • Does the LD spec have to be regularly updated? • Will all runtime environments support all services? 2 proposals: • An extensible service element for the LD Spec • A registry for LD Services

  3. The LD Conference spec Essentially maps (open) LD roles to (fixed) Conference roles

  4. The LD Generic spec Essentially maps (open) LD roles to (open) service roles

  5. Extensible Service Proposal • This allows the Service element to be extended • Service Vocabularies can independent of LD spec • Need a common registry of Service Definitions • Type • Supported roles • Where service can be obtained • As Software • As Online Service/s • Service interface/s supported (if any) • Setup • Runtime

  6. Hybrid P2P and Server Architecture Peer 1 Personal LD engine Multi-player LD Co-ordination Service (PeerServer) Peer2 Personal LD engine Web Server / LMS 2 Web Server / LMS 1 Session Servlet 1 Session Servlet 2 Session Servlet 3 Session Servlet 4 Personal LD engine Personal LD engine Personal LD engine Personal LD engine

  7. Learning Design Components • Search Store & Retrieve LD Components – Why? • LD spec defines Metadata for: • LD Units of Learning • Activities • Environments • Resources • Plays, Acts, Role parts, Activity-Structures? • This allows them to be indexed and searched for – and hence reused in higher-level assemblies. • These can be reused • Also enable high-level Drag’n’Drop Learningflow Editors (as in LAMS authoring)

More Related