PLEs and textmining for lifelong learning
Download as PPT, PDF0 likes448 views
The document outlines the objectives and tasks related to the integration of personal learning environments (PLEs) and language technology resources. It discusses planning competencies, qualitative interviews with stakeholders, and the architecture and functionalities of PLEs, while also emphasizing interwidget communication and service integration. The conclusion highlights the ongoing efforts to enhance interoperability among PLE and language technology services.
PLEs and textmining for lifelong learning
- 1. WP 2: Infrastructure Fridolin Wild, Thomas Ullmann, Bernhard Hoisl OU | The Open University 2 , WU | Vienna University of Economics and Business Katja Buelow (OU), Robert Koblischke (WUW), Markus Essl (BIT MEDIA), Traian Rebedea (PUB-NCIT), Vlad Posea (PUB-NCIT), Thomas Markus (UU), Eline Westerhout (UU), Sonia Mandin (UPMF), Hendrik Drachsler (OUNL), Gaston Burek (UTU), Hristo Kostov (IPP-BAS), Alex Simov (IPP-BAS)
- 2. Objectives O1 | Integration guidelines O2 | Access to language technology resources O3 | Adaptation of existing language technology O4 | Service integration (from WP4-6) O5 | Technical validation of the services # Task 1: PLE Task 2: LT
- 3. PLEs A landscape of tools (institutionally offered or personally chosen) that brings a learner together with others and content artefacts in activities that support in constructing and processing information and knowledge. #
- 4. Competences motivated by PLEs Planning competence refers to those skills, abilities, habits, attitudes, and knowledge that fix how goals, schedules, and paths are set. Reflection is creative sense making of the past and enables planning. Monitoring refers to how progress control is performed. Last but not least, the pair acting and interacting group social & collaboration and information & tool competences. (Wild et al., 2009) Qualitative Interviews with stakeholders (learners, facilitators, learning designers, researchers): 15 persons in 5 sessions (each 40 min to 1 hour) # plan reflect monitor act interact
- 5. PLE Architecture Users involve in use-cases . Each case deploys widgets in support of the given task. Widgets use infrastructure services & data (from within the PLE container or from the Web 2.0). A directory serves the management and deployment of the portfolio. Interoperability standards secure the flexible recombination of widgets, services, and data. #
- 6. #
- 13. LTfLL PLE # + (Wild et al., 2009b; Wild et al., 2010)
- 14. PLE runtime container directory service DPpedia WP 6 fossa RSS transf CONSPECT http://augur.wu.ac.at/elgg #
- 16. Example of Interwidget Communication #
- 17. Authentication openID to avoid lock-in Challenges for protected exchange of data
- 18. Corporate Design & Localisation Example: Pensum #
- 19. Next steps: Widget Arrangements Model dependencies (by type, by token) Patterns and Pattern Exchange Set-Up and wiring with IWC # thread1 PenSum Conspect PolyCAFe PenSum PenSum PenSum PolyCAFe PolyCAFe
- 20. Achievements Service integration of WP4/5/6 into one PLE (side by side) Documentation of services of WP4/5/6 Complete rewrite of Elgg plug-in Apache Wookie extensions Interwidget communication OpenID authentication mechanisms Corporate Design Localisation facilities Started: widget arrangements Explored: deep integration #
- 21. Impact Elgg plug-in three public releases: 2.0, 2.1, 2.2 2.3 is being prepared 440 downloads as of April 22, 2010 Wookie server fork released Apache incubator workshop planned, negotiating with the Apache Software Foundation Workshop MUPPLE’09 at EC-TEL Special Issue on Mash-Up Personal Learning Environments in the International Journal of Technology Enhanced Learning (May 21 st ) # http://wiki.apache.org/concom-planning/WookieLondonJuly2010
- 22. Conclusion The upcoming threads will supervise us in deepening interoperability of the PLE/LT services Task 1: PLE Task 2: LT
- 24. PLE Implementation Strategies Coordinated Use e.g. with the help of browser bookmarks to involved web apps Simple Connectors for Data Exchange and service interoperability Abstracted Connectors that form Conduits e.g. those supported by the social browser Flock e.g. by the service-oriented PLE Plex (Wilson et al., 2007)