Developing pedagogically sound ples

734
-1

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
734
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Developing pedagogically sound ples

  1. 1. Developing pedagogically sound PLEs – a practical introduction<br />Martin Friedrichmartin.friedrich@fit.fraunhofer.de<br />July 12, 2011<br />
  2. 2. Pedagogically Sound PLEs<br />28.02.09<br /><ul><li>Current existing LMSs or LCMSs provide basic personalization features
  3. 3. learners have to deal with fixed structures
  4. 4. no personalization of the learning processes
  5. 5. customize your own learning environment
  6. 6. E.g. by mashing up widgets
  7. 7. pushes the PLE approach into LMSs
  8. 8. current mash up solutions do not provide self-reflection or adaption mechanism based on the learners' learning experiences
  9. 9. ROLE shows two ways of how to provide responsive personalization features:
  10. 10. (1) Building one’s own learning environment according to one’s own preferences
  11. 11. (2) by providing pedagogical features
  12. 12. This Workshop:
  13. 13. Presentation of approaches and technologies developed as part of the ROLE project to build a pedagogically sound PLE
  14. 14. No hands-on session - only information provision (concepts and demos)</li></li></ul><li>OpenSocial<br />28.02.09<br /><ul><li>OpenSocial is a set of common application programming interfaces (APIs) for web-based social network applications
  15. 15. AllowstheusageofOpenSocial Gadgets (Widgets)
  16. 16. OpenSocialdefines a common API for social applications across multiple websites
  17. 17. http://code.google.com/apis/opensocial/
  18. 18. http://www.opensocial.org/</li></li></ul><li>Widget Definition<br />28.02.09<br /><ul><li>Widgets are mini-applications built using HTML, with JavaScript, Flash or Silverlight for dynamic behaviors.
  19. 19. Widgets are defined via XML
  20. 20. Browser based, Desktop, Mobile, Web</li></li></ul><li>WidgetSpecifications (Overview)<br />28.02.09<br /><ul><li>W3C Widgets 1.0
  21. 21. specified by the World Wide Web Consortium (W3C)
  22. 22. Used in Apache Wookie Server
  23. 23. Set of files packed as .zip (widget preferences and start files)
  24. 24. not many widgets written in this format
  25. 25. OpenAjaxMetadata 1.0 Specification
  26. 26. developed by the OpenAjax Alliance
  27. 27. uncertain whether the specification will be continued
  28. 28. OpenSocial Gadgets
  29. 29. previously a vendor specific format (Google Gadgets)
  30. 30. Now a more independent specification managed by the OpenSocial Foundation
  31. 31. OpenSocial widgets are able to connect to the social graph of the widget container
  32. 32. Supported by several widget stores, e.g. iGoogle, Netvibes, XING, …
  33. 33. Supported by several widget containers, e.g. iGoogle, Linkedin, …
  34. 34. Single .xml file</li></ul>Further proprietary Definitions are existing<br />
  35. 35. WidgetGettingStarted Guide<br /><ul><li>Tutorialand First Steps
  36. 36. http://code.google.com/apis/gadgets/
  37. 37. Sandbox
  38. 38. Google Gadget Editor (http://www.google.com/ig/modules/gge.xml)
  39. 39. Add toyouriGooglespaceandplayaround</li></ul>28.02.09<br /><?xmlversion="1.0" encoding="UTF-8"?><Module> <ModulePrefs title="helloworldexample" /> <Content type="html"><![CDATA[ <input type="button" id="refresh" onclick="alert('Hello, world!')" value="alert"> ]]></Content></Module><br />
  40. 40. Summary<br />28.02.09<br /><ul><li>Buildingpedagogicallysound PLEs with ROLE
  41. 41. OpenSocial
  42. 42. Gadget Mash-Up
  43. 43. Learners customize their learning environment
  44. 44. Missing: Add more pedagogically sound features like
  45. 45. Responsiveness
  46. 46. Openess
  47. 47. self-reflection
  48. 48. Recommendation
  49. 49. Organization
  50. 50. …</li></li></ul><li>Part II: ROLE Core Components <br /><ul><li>Spaces: (10 min)
  51. 51. Inter-widget Communication: (10 min)
  52. 52. User Monitoringand User Profile services (10 min)
  53. 53. Widget Store: (10 min) 
  54. 54. ROLE SDK (10 min)</li></ul>28.02.09<br />
  55. 55. Spaces<br />28.02.09<br />
  56. 56. Spaces<br /><ul><li>Definition
  57. 57. abstract concept that shapes the context in which user is currently placed.
  58. 58. People
  59. 59. Applications
  60. 60. Resources
  61. 61. Structure a learning environments into separate categories
  62. 62. for different courses
  63. 63. group of people
  64. 64. companydivision
  65. 65.
  66. 66. comprises several widgets personally mashed up by a learner
  67. 67. create portable collaborative learning environments
  68. 68. offers access to further technologies such as inter-widget communication and space resources
  69. 69. ImplementedasOpenSocial 2.0 JS API Extension
  70. 70. can be shared across learning platforms and learners</li></ul>28.02.09<br />
  71. 71. Demo<br /><ul><li>Spaces Demo on Graaasp
  72. 72. http://graaasp.epfl.ch/#item=space_447
  73. 73. http://graaasp.epfl.ch/#item=space_790</li></ul>28.02.09<br />
  74. 74. How to access spaces and resources in OS Gadgets<br /><ul><li>Snippets:
  75. 75. currentviewer:osapi.people.getViewer().execute(function(viewer){ viewerId = viewer.id;viewerName = viewer.displayName;});
  76. 76. Resourcesosapi.context.get().execute(function(context){contextId = context.contextId; contextType = context.contextType; // ifgadgetbelongsto a space { contextType: "@space", contextId: "23"} });
  77. 77. Getspace-resourcesosapi.applications.get({contextId:'4', contextType:"@space"}).execute(function(response){ // returns list of resources that belong to a space with id=4 });
  78. 78. http://sourceforge.net/apps/mediawiki/role-project/index.php?title=Space</li></ul>28.02.09<br />
  79. 79. Inter-widget Communication<br />28.02.09<br />
  80. 80. Inter-widget Communication<br /><ul><li>Definition
  81. 81. Inter-widget communication allows interaction and data exchange between the separate widgets
  82. 82. creates a flexible environment where the widgets can react on the current user’s focus
  83. 83. React on user actions
  84. 84. Implementedas JavaScript Library (OpenApp)</li></ul>28.02.09<br />
  85. 85. Example Scenario<br /><ul><li>A user is reading news stories as part of learning a foreign language
  86. 86. His space comprises the following widgets
  87. 87. RSS news feed reader
  88. 88. Portfolio
  89. 89. Translator
  90. 90. Map (e.g., based on Google Maps)
  91. 91. The user selects a news story  an event is published (broadcast)
  92. 92. The portfolio widget receives the event  displays an “Add” button that the user can add the resource
  93. 93. The map widget also receives the event it automatically moves the view to the news story's coordinates</li></ul>28.02.09<br />
  94. 94. Inter-widget Communication<br /><ul><li>IWC events are JSON structures that contain an administrative envelope and a message in some format
  95. 95. Selecting a news feed could look like this:{ event: "select“, type: "namespaced-properties“,uri: "http://www.example.com/news0001’’, message: { "http://purl.org/dc/elements/1.1/title": "News story“, “http://simile.mit.edu/2005/05/ontologies/location#coordinates”,"64.10,-051.45” } }
  96. 96. IWC events are published via broadcasting (Each widget receives all IWC events)
  97. 97. IWC uses the principle of partial semantic interoperability
  98. 98. widget developers are encouraged to use a combination of established vocabularies in a simplified format
  99. 99. Developers of receiving widgets are encouraged to ignore parts of events which are either unrelated or not understood
  100. 100. No communication between widgets should be initiated without the user performing a relevant action
  101. 101. Widgets should not react in a way that has side-effects, without involving the user (“User in control” balanced with “Automatic”)</li></ul>28.02.09<br />
  102. 102. Demo<br /><ul><li>http://www.google.de/#t_4 (language Learning)</li></ul>28.02.09<br />
  103. 103. Snippet<br />// init IWC eventcallback<br />gadgets.openapp.connect(callback);<br />…<br />// processincoming IWC events<br />varcallback = function(envelope, message){<br /> //TODO: process IWC event<br />}<br />…<br />// publish IWC events<br />gadgets.openapp.publish(envelope, message)<br />28.02.09<br />
  104. 104. Remote IWC (Extension)<br /><ul><li>Current IWC approach only allows local IWC (i.e. within one space)
  105. 105. What if user wants to do some real-time collaboration task?
  106. 106. watching videos
  107. 107. Whiteboard or document writing
  108. 108. Teacher wants to discuss course exercise
  109. 109. Remote Presentation (like from Martin Ebner)
  110. 110. RIWC is realized via XMPP Open-Source
  111. 111. Work in Progress
  112. 112. Goal: combine local and remote IWC</li></ul>28.02.09<br />
  113. 113. User Monitoringand User Profile services<br />28.02.09<br />
  114. 114. User Monitoringand User Profile services<br /><ul><li>Definition
  115. 115. serves as basic approach to provide
  116. 116. personalization
  117. 117. recommendation
  118. 118. self-reflection
  119. 119. User Monitoring
  120. 120. Based on IWC
  121. 121. User activity over time
  122. 122. The learner can activate/deactivate user monitoring within his learning environment
  123. 123. UsesContextualized Attention Metadata (CAM) format
  124. 124. User Profile
  125. 125. competences, goals, the learning progress, certificates, preferences, …
  126. 126. more user-centred, and less activity-centred
  127. 127. Work in progress
  128. 128. integrate current pedagogical findings (e.g. by providing a pedagogical recommender)</li></ul>28.02.09<br />
  129. 129. Recommender Approaches<br /><ul><li>Used for certain functionality, like the psycho-pedagogical recommender adapts navigation according to user attributes
  130. 130. To access user resources (like competences)
  131. 131. psycho-pedagogical recommender for planning & navigation
  132. 132. based on learner characteristics and competences, support along PPIM phases
  133. 133. URL: http://widgetstore.role-demo.de/content/navigation-tool-widget</li></ul>28.02.09<br />
  134. 134. Recommender Approaches<br /><ul><li>Binocs: Collaborative recommendations within a federated search widget
  135. 135. URL: http://widgetstore.role-demo.de/content/binocs
  136. 136. PLEShare: PLE recommendations based on data voluntarily shared by users
  137. 137. URLs: http://widgetstore.role-demo.de/content/pleshare or https://addons.mozilla.org/en-US/firefox/addon/pacman-176479/</li></ul>28.02.09<br />
  138. 138. User Monitoring<br /><ul><li>Implementedas Web Service
  139. 139. Store & Query MonitoredActivity in PLE
  140. 140. https://sites.google.com/site/camschema/home
  141. 141. Authorization via Oauth in Progress </li></ul>28.02.09<br />var post = {statement:query, token:myToken, livedb: livedb};<br />varparams = {}; params[gadgets.io.RequestParameters.METHOD] = gadgets.io.MethodType.POST; params[gadgets.io.RequestParameters.POST_DATA]= gadgets.io.encodeValues(post); params[gadgets.io.RequestParameters.CONTENT_TYPE] = <br />gadgets.io.ContentType.JSON;<br />// execute POST Method Call; resultavailable via callback<br />gadgets.io.makeRequest(wsUrl, queryCamCallback, params);<br />
  142. 142. Demo<br /><ul><li>SJTU (Activity Meter)
  143. 143. http://202.120.34.34/web/french-i/french-tools
  144. 144. WKM (Navigation Support)
  145. 145. http://role-is.dbis.rwth-aachen.de/role/wkm/</li></ul>28.02.09<br />
  146. 146. Widget Store<br />28.02.09<br />
  147. 147. Widget Store<br /><ul><li>Definition
  148. 148. central repository to explore and search widgets
  149. 149. market place to upload and share new widgets with a broad learner community
  150. 150. Standard social features like tagging, rating, commenting included
  151. 151. URL: http://www.role-widgetstore.eu/</li></ul>28.02.09<br />
  152. 152. Summary<br /><ul><li>Spaces for Organizing and accessing features like IWC
  153. 153. IWC to enable react on current user actions and collaboration
  154. 154. Monitoring to generate user profiles over Time and as basis for Self Reflectoion, Recommendation and personalization features
  155. 155. Widget Store as central repository of Tools, to share and search tools/best practices</li></ul>28.02.09<br />
  156. 156. ROLE SDK<br />28.02.09<br />
  157. 157. ROLE SDK<br /><ul><li>Definition
  158. 158. ROLE SDK as entry point into ROLE technology
  159. 159. Downloadable bundle
  160. 160. https://sourceforge.net/projects/role-project/files/role-m1-sdk/
  161. 161. Runs out of the box
  162. 162. Sample widgets included
  163. 163. Can be used for
  164. 164. Widget Development
  165. 165. Enable your PLE with ROLE Technology (includes some Reference Implementation)
  166. 166. https://sourceforge.net/apps/mediawiki/role-project/index.php?title=ROLE_SDK
  167. 167. Alpha Version (first bundle, will be improved)</li></ul>28.02.09<br />
  168. 168. The End<br />28.02.09<br />
  169. 169. The first<br />WidgetEnchantment<br />Jointhecompetition.<br /> Create a widget.<br />Win a prize!<br />Deadline: August 31th, 2011<br />The winner will beannounced September 15th, 2011http://www.role-project.eu/?page_id=1291<br />
  170. 170. Part III: Closing & Feedback <br /><ul><li>Questionaire
  171. 171. http://tinyurl.com/3jh45cl
  172. 172. Link Summary
  173. 173. ROLE Enchantment - http://www.role-project.eu/?page_id=1291
  174. 174. ROLE Homepage - http://www.role-project.eu/
  175. 175. ROLE Wiki - https://sourceforge.net/apps/mediawiki/role-project/index.php?title=Main_Page
  176. 176. ROLE SDK - http://sourceforge.net/projects/role-project/files/ROLE%20SDK%20M1/
  177. 177. Widgetstore - http://widgetstore.role-demo.de/
  178. 178. Showcase Platform - http://www.role-showcase.eu/
  179. 179. ROLE Developer Group Contact - https://groups.google.com/group/role-dev</li></ul>28.02.09<br />
  180. 180. Questions?<br />28.02.09<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×