1 / 14

Learning Design System: Supporting IMS Transfer & Representation

The SLeD system aims to support learning transfer through IMS Learning Design, validating designs, generating variations, and modular architecture. It uses CopperCore service architecture for communication and rendering, with Java-based development. Implementation issues are addressed, such as technical challenges with AXIS and attachments. Development timelines and tools for investigating learning design and user interfaces are emphasized.

chione
Télécharger la présentation

Learning Design System: Supporting IMS Transfer & Representation

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. The Open University Patrick McAndrew Martin Weller Will Woods Alex Little + IET UserLab Pascale Hardy Andrew Brasher Open Universiteit Rob Koper Hubert Vogten Francis Brouns Harrie Martens + Learning Networks group SLeD: Service-based Learning Design system OUUK OUNL

  2. SLeD – domain position

  3. SLeD: Learning Design System • Overall aim to support and investigate the transfer and representation of learning using IMS Learning Design • Validation of designs • Generating variations in design • Representing generic ways to use tools • Modular architecture

  4. Use Cases

  5. Use Cases

  6. SLeD architecture

  7. CopperCore: Service Architecture

  8. SLeD: Systems view • CopperCore (OUNL) • Level A (existing) • Level B • Level C • Service communication • Player system (OUUK) • Built around CopperCore • Rendering • Description of environment – service descriptions • Interconnection via services (prototype uses Java) • Development will be in Java/JBoss/SQL

  9. CopperCore Service Progress • Done • Level B,C implemented • SOAP enabled including WSDL files • Inline documentation finished • Installation/making available via SourceForge • To do: • additional documentation

  10. SLeD: Implementation issues • Learning Design – open issues in standard – UNFOLD meeting helpful • Need for more examples • Sakai OSIDs – not as useful as hoped but interesting • Switch to services not completed yet

  11. CopperCore: Technical issues encountered • When using AXIS • difference between static generated WSDL file and run time generated WSDL file • Attachments different specifications are incompatible (SwA, MTOM, WS-Attachments using DIME). Our temporary solution: avoid attachments using base64binary

  12. Process issues • Development bay • used SourceForge • Development notes on website – praised • Timescale • Short and over summer • Good idea to try to work to six month • Reporting • UML/Use cases/Releasing software

  13. Usage • Tool for investigating Learning Design • Development of user tools • New User Interfaces • More accessible toolkit than CopperCore • E.g. link to Reload editor • Aim to investigate Learning Design and semantic description of tools • Link to pedagogic design and knowledge management

More Related