1. Developing pedagogically sound PLEs – a practical introduction Martin Friedrichmartin.friedrich@fit.fraunhofer.de July 12, 2011

3. learners have to deal with fixed structures

4. no personalization of the learning processes

5. customize your own learning environment

6. E.g. by mashing up widgets

7. pushes the PLE approach into LMSs

8. current mash up solutions do not provide self-reflection or adaption mechanism based on the learners' learning experiences

9. ROLE shows two ways of how to provide responsive personalization features:

10. (1) Building one’s own learning environment according to one’s own preferences

11. (2) by providing pedagogical features

12. This Workshop:

13. Presentation of approaches and technologies developed as part of the ROLE project to build a pedagogically sound PLE

15. AllowstheusageofOpenSocial Gadgets (Widgets)

16. OpenSocialdefines a common API for social applications across multiple websites

17. http://code.google.com/apis/opensocial/

19. Widgets are defined via XML

21. specified by the World Wide Web Consortium (W3C)

22. Used in Apache Wookie Server

23. Set of files packed as .zip (widget preferences and start files)

24. not many widgets written in this format

25. OpenAjaxMetadata 1.0 Specification

26. developed by the OpenAjax Alliance

27. uncertain whether the specification will be continued

28. OpenSocial Gadgets

29. previously a vendor specific format (Google Gadgets)

30. Now a more independent specification managed by the OpenSocial Foundation

31. OpenSocial widgets are able to connect to the social graph of the widget container

32. Supported by several widget stores, e.g. iGoogle, Netvibes, XING, …

33. Supported by several widget containers, e.g. iGoogle, Linkedin, …

34. Single .xml fileFurther proprietary Definitions are existing

36. http://code.google.com/apis/gadgets/

37. Sandbox

38. Google Gadget Editor (http://www.google.com/ig/modules/gge.xml)

39. Add toyouriGooglespaceandplayaround28.02.09 <?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>

41. OpenSocial

42. Gadget Mash-Up

43. Learners customize their learning environment

44. Missing: Add more pedagogically sound features like

45. Responsiveness

46. Openess

47. self-reflection

48. Recommendation

49. Organization

51. Inter-widget Communication: (10 min)

52. User Monitoringand User Profile services (10 min)

53. Widget Store: (10 min)

54. ROLE SDK (10 min)28.02.09

55. Spaces 28.02.09

57. abstract concept that shapes the context in which user is currently placed.

58. People

59. Applications

60. Resources

61. Structure a learning environments into separate categories

62. for different courses

63. group of people

64. companydivision

65. …

66. comprises several widgets personally mashed up by a learner

67. create portable collaborative learning environments

68. offers access to further technologies such as inter-widget communication and space resources

69. ImplementedasOpenSocial 2.0 JS API Extension

70. can be shared across learning platforms and learners28.02.09

72. http://graaasp.epfl.ch/#item=space_447

73. http://graaasp.epfl.ch/#item=space_79028.02.09

75. currentviewer:osapi.people.getViewer().execute(function(viewer){ viewerId = viewer.id;viewerName = viewer.displayName;});

76. Resourcesosapi.context.get().execute(function(context){contextId = context.contextId; contextType = context.contextType; // ifgadgetbelongsto a space { contextType: "@space", contextId: "23"} });

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. http://sourceforge.net/apps/mediawiki/role-project/index.php?title=Space28.02.09

79. Inter-widget Communication 28.02.09

81. Inter-widget communication allows interaction and data exchange between the separate widgets

82. creates a flexible environment where the widgets can react on the current user’s focus

83. React on user actions

84. Implementedas JavaScript Library (OpenApp)28.02.09

86. His space comprises the following widgets

87. RSS news feed reader

88. Portfolio

89. Translator

90. Map (e.g., based on Google Maps)

91. The user selects a news story  an event is published (broadcast)

92. The portfolio widget receives the event  displays an “Add” button that the user can add the resource

93. The map widget also receives the event it automatically moves the view to the news story's coordinates28.02.09

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. IWC events are published via broadcasting (Each widget receives all IWC events)

97. IWC uses the principle of partial semantic interoperability

98. widget developers are encouraged to use a combination of established vocabularies in a simplified format

99. Developers of receiving widgets are encouraged to ignore parts of events which are either unrelated or not understood

100. No communication between widgets should be initiated without the user performing a relevant action

101. Widgets should not react in a way that has side-effects, without involving the user (“User in control” balanced with “Automatic”)28.02.09

103. Snippet // init IWC eventcallback gadgets.openapp.connect(callback); … // processincoming IWC events varcallback = function(envelope, message){ //TODO: process IWC event } … // publish IWC events gadgets.openapp.publish(envelope, message) 28.02.09

105. What if user wants to do some real-time collaboration task?

106. watching videos

107. Whiteboard or document writing

108. Teacher wants to discuss course exercise

109. Remote Presentation (like from Martin Ebner)

110. RIWC is realized via XMPP Open-Source

111. Work in Progress

112. Goal: combine local and remote IWC28.02.09

113. User Monitoringand User Profile services 28.02.09

115. serves as basic approach to provide

116. personalization

117. recommendation

118. self-reflection

119. User Monitoring

120. Based on IWC

121. User activity over time

122. The learner can activate/deactivate user monitoring within his learning environment

123. UsesContextualized Attention Metadata (CAM) format

124. User Profile

125. competences, goals, the learning progress, certificates, preferences, …

126. more user-centred, and less activity-centred

127. Work in progress

128. integrate current pedagogical findings (e.g. by providing a pedagogical recommender)28.02.09

130. To access user resources (like competences)

131. psycho-pedagogical recommender for planning & navigation

132. based on learner characteristics and competences, support along PPIM phases

133. URL: http://widgetstore.role-demo.de/content/navigation-tool-widget28.02.09

135. URL: http://widgetstore.role-demo.de/content/binocs

136. PLEShare: PLE recommendations based on data voluntarily shared by users

137. URLs: http://widgetstore.role-demo.de/content/pleshare or https://addons.mozilla.org/en-US/firefox/addon/pacman-176479/28.02.09

139. Store & Query MonitoredActivity in PLE

140. https://sites.google.com/site/camschema/home

141. Authorization via Oauth in Progress 28.02.09 var post = {statement:query, token:myToken, livedb: livedb}; 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] = gadgets.io.ContentType.JSON; // execute POST Method Call; resultavailable via callback gadgets.io.makeRequest(wsUrl, queryCamCallback, params);

143. http://202.120.34.34/web/french-i/french-tools

144. WKM (Navigation Support)

145. http://role-is.dbis.rwth-aachen.de/role/wkm/28.02.09

146. Widget Store 28.02.09

148. central repository to explore and search widgets

149. market place to upload and share new widgets with a broad learner community

150. Standard social features like tagging, rating, commenting included

151. URL: http://www.role-widgetstore.eu/28.02.09

153. IWC to enable react on current user actions and collaboration

154. Monitoring to generate user profiles over Time and as basis for Self Reflectoion, Recommendation and personalization features

155. Widget Store as central repository of Tools, to share and search tools/best practices28.02.09

156. ROLE SDK 28.02.09

158. ROLE SDK as entry point into ROLE technology

159. Downloadable bundle

160. https://sourceforge.net/projects/role-project/files/role-m1-sdk/

161. Runs out of the box

162. Sample widgets included

163. Can be used for

164. Widget Development

165. Enable your PLE with ROLE Technology (includes some Reference Implementation)

166. https://sourceforge.net/apps/mediawiki/role-project/index.php?title=ROLE_SDK

167. Alpha Version (first bundle, will be improved)28.02.09

168. The End 28.02.09

169. The first WidgetEnchantment Jointhecompetition. Create a widget. Win a prize! Deadline: August 31th, 2011 The winner will beannounced September 15th, 2011http://www.role-project.eu/?page_id=1291

171. http://tinyurl.com/3jh45cl

172. Link Summary

173. ROLE Enchantment - http://www.role-project.eu/?page_id=1291

174. ROLE Homepage - http://www.role-project.eu/

175. ROLE Wiki - https://sourceforge.net/apps/mediawiki/role-project/index.php?title=Main_Page

176. ROLE SDK - http://sourceforge.net/projects/role-project/files/ROLE%20SDK%20M1/

177. Widgetstore - http://widgetstore.role-demo.de/

178. Showcase Platform - http://www.role-showcase.eu/

179. ROLE Developer Group Contact - https://groups.google.com/group/role-dev28.02.09

180. Questions? 28.02.09