PLES UPA · Title: PLES UPA Author: David Created Date: 20100127201314Z
Developing pedagogically sound ples
-
Upload
martin-friedrich -
Category
Technology
-
view
675 -
download
0
Transcript of Developing pedagogically sound ples
© www.role-project.eu
Developing pedagogically sound PLEs – a practical introduction
Martin [email protected]
July 12, 2011
Pedagogically Sound PLEs
28.02.09
Current existing LMSs or LCMSs provide basic personalization features learners have to deal with fixed structures
no personalization of the learning processes
customize your own learning environment E.g. by mashing up widgets
pushes the PLE approach into LMSs
current mash up solutions do not provide self-reflection or adaption mechanism based on the learners' learning experiences
ROLE shows two ways of how to provide responsive personalization features: (1) Building one’s own learning environment according to one’s own preferences
(2) by providing pedagogical features
This Workshop: Presentation of approaches and technologies developed as part of the ROLE project to build a
pedagogically sound PLE No hands-on session - only information provision (concepts and demos)
OpenSocial
28.02.09
OpenSocial is a set of common application programming interfaces (APIs) for web-based social network applications
Allows the usage of OpenSocial Gadgets (Widgets)
OpenSocial defines a common API for social applications across multiple websites
http://code.google.com/apis/opensocial/ http://www.opensocial.org/
Widget Definition
28.02.09
Widgets are mini-applications built using HTML, with JavaScript, Flash or Silverlight for dynamic behaviors.
Widgets are defined via XML Browser based, Desktop, Mobile, Web
Widget Specifications (Overview)
28.02.09
W3C Widgets 1.0 specified by the World Wide Web Consortium (W3C) Used in Apache Wookie Server Set of files packed as .zip (widget preferences and start files) not many widgets written in this format
OpenAjax Metadata 1.0 Specification developed by the OpenAjax Alliance uncertain whether the specification will be continued
OpenSocial Gadgets previously a vendor specific format (Google Gadgets) Now a more independent specification managed by the OpenSocial Foundation OpenSocial widgets are able to connect to the social graph of the widget container Supported by several widget stores, e.g. iGoogle, Netvibes, XING, … Supported by several widget containers, e.g. iGoogle, Linkedin, … Single .xml file
Further proprietary Definitions are existing
Widget Getting Started Guide
Tutorial and First Steps http://code.google.com/apis/gadgets/
Sandbox Google Gadget Editor (http://www.google.com/ig/modules/gge.xml) Add to your iGoogle space and play around
28.02.09
<?xml version="1.0" encoding="UTF-8"?><Module>
<ModulePrefs title="hello world example" /><Content type="html"><![CDATA[
<input type="button" id="refresh" onclick="alert('Hello, world!')" value="alert">]]></Content>
</Module>
Summary
28.02.09
Building pedagogically sound PLEs with ROLE OpenSocial Gadget Mash-Up
Learners customize their learning environment Missing: Add more pedagogically sound features like
Responsiveness Openess self-reflection Recommendation Organization …
Part II: ROLE Core Components
Spaces: (10 min)
Inter-widget Communication: (10 min)
User Monitoring and User Profile services (10 min)
Widget Store: (10 min)
ROLE SDK (10 min)
28.02.09
Spaces
28.02.09
Spaces
Definition abstract concept that shapes the context in which user is currently placed.
People Applications Resources
Structure a learning environments into separate categories for different courses group of people company division …
comprises several widgets personally mashed up by a learner create portable collaborative learning environments offers access to further technologies such as inter-widget communication and space
resources Implemented as OpenSocial 2.0 JS API Extension can be shared across learning platforms and learners
28.02.09
Demo
Spaces Demo on Graaasp
http://graaasp.epfl.ch/#item=space_447
http://graaasp.epfl.ch/#item=space_790
28.02.09
How to access spaces and resources in OS Gadgets
Snippets: current viewer:
osapi.people.getViewer().execute(function(viewer){ viewerId = viewer.id;viewerName = viewer.displayName;
});
Resourcesosapi.context.get().execute(function(context){
contextId = context.contextId; contextType = context.contextType; // if gadget belongs to a space { contextType: "@space", contextId: "23"}
});
Get space-resourcesosapi.applications.get({contextId:'4', contextType:"@space"}).execute(function(response){
// returns list of resources that belong to a space with id=4 });
http://sourceforge.net/apps/mediawiki/role-project/index.php?title=Space
28.02.09
Inter-widget Communication
28.02.09
Inter-widget Communication
Definition Inter-widget communication allows interaction and data exchange between the
separate widgets creates a flexible environment where the widgets can react on the current user’s focus React on user actions Implemented as JavaScript Library (OpenApp)
28.02.09
Example Scenario
A user is reading news stories as part of learning a foreign language
His space comprises the following widgets RSS news feed reader Portfolio Translator Map (e.g., based on Google Maps)
The user selects a news story an event is published (broadcast)
The portfolio widget receives the event displays an “Add” button that the user can add the resource
The map widget also receives the event it automatically moves the view to the news story's coordinates
28.02.09
Inter-widget Communication
IWC events are JSON structures that contain an administrative envelope and a message in some format
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”
}}
IWC events are published via broadcasting (Each widget receives all IWC events) IWC uses the principle of partial semantic interoperability
widget developers are encouraged to use a combination of established vocabularies in a simplified format
Developers of receiving widgets are encouraged to ignore parts of events which are either unrelated or not understood
No communication between widgets should be initiated without the user performing a relevant action
Widgets should not react in a way that has side-effects, without involving the user (“User in control” balanced with “Automatic”)
28.02.09
Snippet
// init IWC event callback
gadgets.openapp.connect(callback);
…
// process incoming IWC events
var callback = function(envelope, message){
//TODO: process IWC event
}
…
// publish IWC events
gadgets.openapp.publish(envelope, message)
28.02.09
Remote IWC (Extension)
Current IWC approach only allows local IWC (i.e. within one space) What if user wants to do some real-time collaboration task?
watching videos Whiteboard or document writing Teacher wants to discuss course exercise Remote Presentation (like from Martin Ebner)
RIWC is realized via XMPP Open-Source Work in Progress Goal: combine local and remote IWC
28.02.09
User Monitoring and User Profile services
28.02.09
User Monitoring and User Profile services
Definition serves as basic approach to provide
personalization recommendation self-reflection
User Monitoring Based on IWC User activity over time The learner can activate/deactivate user monitoring within his learning environment Uses Contextualized Attention Metadata (CAM) format
User Profile competences, goals, the learning progress, certificates, preferences, … more user-centred, and less activity-centred Work in progress
integrate current pedagogical findings (e.g. by providing a pedagogical recommender)
28.02.09
Recommender Approaches
Used for certain functionality, like the psycho-pedagogical recommender adapts navigation according to user attributes
To access user resources (like competences)
psycho-pedagogical recommender for planning & navigation based on learner characteristics and competences, support along PPIM phases URL: http://widgetstore.role-demo.de/content/navigation-tool-widget
28.02.09
Recommender Approaches
Binocs: Collaborative recommendations within a federated search widget URL: http://widgetstore.role-demo.de/content/binocs
PLEShare: PLE recommendations based on data voluntarily shared by users URLs: http://widgetstore.role-demo.de/content/pleshare or
https://addons.mozilla.org/en-US/firefox/addon/pacman-176479/
28.02.09
User Monitoring
Implemented as Web Service Store & Query Monitored Activity in PLE
https://sites.google.com/site/camschema/home
Authorization via Oauth in Progress
28.02.09
var post = {statement:query, token:myToken, livedb: livedb};var params = {}; 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; result available via callbackgadgets.io.makeRequest(wsUrl, queryCamCallback, params);
Demo
SJTU (Activity Meter) http://202.120.34.34/web/french-i/french-tools
WKM (Navigation Support) http://role-is.dbis.rwth-aachen.de/role/wkm/
28.02.09
Widget Store
28.02.09
Widget Store
Definition central repository to explore and search widgets market place to upload and share new widgets with a broad learner community Standard social features like tagging, rating, commenting included
URL: http://www.role-widgetstore.eu/
28.02.09
Summary
Spaces for Organizing and accessing features like IWC
IWC to enable react on current user actions and collaboration
Monitoring to generate user profiles over Time and as basis for Self Reflectoion, Recommendation and personalization features
Widget Store as central repository of Tools, to share and search tools/best practices
28.02.09
ROLE SDK
28.02.09
ROLE SDK
Definition ROLE SDK as entry point into ROLE technology Downloadable bundle
https://sourceforge.net/projects/role-project/files/role-m1-sdk/
Runs out of the box Sample widgets included Can be used for
Widget Development Enable your PLE with ROLE Technology (includes some Reference Implementation) https://sourceforge.net/apps/mediawiki/role-project/index.php?title=ROLE_SDK
Alpha Version (first bundle, will be improved)
28.02.09
The End
28.02.09
The first
Widget Enchantment
Join the competition.Create a widget.
Win a prize!
Deadline: August 31th, 2011The winner will be announced September 15th, 2011http://www.role-project.eu/?page_id=1291
Part III: Closing & Feedback
Questionaire http://tinyurl.com/3jh45cl
Link Summary ROLE Enchantment - http://www.role-project.eu/?page_id=1291
ROLE Homepage - http://www.role-project.eu/
ROLE Wiki - https://sourceforge.net/apps/mediawiki/role-project/index.php?title=Main_Page
ROLE SDK - http://sourceforge.net/projects/role-project/files/ROLE%20SDK%20M1/
Widgetstore - http://widgetstore.role-demo.de/
Showcase Platform - http://www.role-showcase.eu/
ROLE Developer Group Contact - https://groups.google.com/group/role-dev
28.02.09
Questions?
28.02.09