COLlaborative LeArning desiGn Editor

COLLAGE  - a high-level specialized Learning Design authoring tool for collaborative learning.

http://gsic.tel.uva.es/collage

HowTo: Configure SVN+SSH with Subclipse on Windows

 HowTo: Configure SVN+SSH with Subclipse on Window:
http://www.woodwardweb.com/java/000155.html

Other…help with SVN

SVN

First: Create the repository:

Putty or ssh into your student account or group area.
(You can apply for group area here: http://www.stud.ntnu.no/kundesenter/)

cd to where you want the repository and type “svnadmin create .”
or type “svnadmin create /path/to/repository”

E.g.:
cd /home/groups/sds_group/
mkdir svn
cd svn
svnadmin create .

or

svnadmin create /home/groups/sds_group/svn

Second: Install subclipse
(http://subclipse.tigris.org/install.html)

Third: Point subclipse to the repository
Create the project (if you haven’t already done so).
Right click on the project -> select team -> share project
Select SVN -> Next
Select “Create new repository” -> Next
Enter URL:
“svn+ssh://username@login.stud.ntnu.no/path/to/repository”
(E.g.: “svn+ssh://johndoe@login.stud.ntnu.no/home/groups/sds_group/svn”)

Importing an already existing project:
Import -> Checkout project from svn
Select “Create new repository” -> Next
Enter URL:
“svn+ssh://username@login.stud.ntnu.no/path/to/repository”
(E.g.: “svn+ssh://johndoe@login.stud.ntnu.no/home/groups/sds_group/svn”)
-> Next
Select project to check out -> Finish

Common problems:
File permission in group area.
Wrong version of subclipse.

Quick workaround:
Try turtoise svn instead of subclipse   Thanks to Vaskinn[vaskinn@stud.ntnu.no] this Tutorial. 

Creating OSGI Bundle

• Introductory tutorial to create simple OSGI bundles
• KnopflerfishOSGI Tutorial
• Peter Krien’s OSGI Tutorial

Model-Driven Software Developement

Rolv Bræk³  and Geir Melby⁴

(3)	NTNU Department of Telematics, Trondheim, Norway

(4)	Ericsson Norarc, Asker, Norway

Summary

Abstraction and platform are two of the most central concepts in MDA. To succeed with MDA means to build a clear, operational understanding of the two concepts. Two key questions are how to express the PIM and especially its behavior, and how to deal with implementation and platform dependent properties. In this chapter we offer some answers based on earlier work on model-driven development and current work on model-driven service engineering. A central aim of the latter work is to enable rapid, modular and incremental development and deployment of collaborative services. A model-driven solution supported by a layered execution framework is presented.

http://www.springerlink.com/content/xv8337515g781826/fulltext.pdf 

Description and Composition of e-learning Services

Oussama Kassem Zein and Yvon Kermarrec

Journal of Software Engineering Vol. 2 No. 5 November 2007

• Defines the meta-model for learning service descriptions
• Uses ontologies to index and store these models
• So that students, teachers, researchers can use this model to query and publish learning services

• Facilitator [along with Ontobroker- a inference engine (to trigger various processes and events) and for ontology management (add, delete, modify ontologies)] based on ontology is developed/used for service discovery and composition. It provides the interfaces that allows the client and servers to query(import function) and advertise (import function) learning services based on underlying ontologies. If search is successful, it invokes the service selected interacting with the provider and sends the result to the client. If service search is unsuccessful, allows the services to be composed automatically.

• Their own approach for semantic description of service behavior that includes input/output flows and post/pre-conditions
• Their own approach for service interface description

OWL-S Editor and Portege

• Service description, modeling and composition language : OWL-S. 
• Porrege Ontology Tool (working V 3.2.1) and OWL-S Editor
• (Note that: Later versions of the Portege looks like incompatible with OWL-S Editor. Install only vasic version of Portege - OWL plugin - instead of full version)

Journals and Conferences in Computer Science

Nice collection

http://dit.unitn.it/~ilya/conf.html

MyArtSpace

Myartspace enables students (as part of a school visit) to collect physical objects from a cultural venue using a mobile phone, learn more about the objects that they collect, and then publish their own gallery online.

http://www.myartspace.org.uk/web/index.php

Dual-T Project

This project belongs to a field referred to as computer-supported collaborative learning (CSCL). The focus of research in this field is the study of collaborative interactions and ways to influence them by the definition of a collaboration scripts and by the provision of realtime feedback through group mirrors

http://dualt.epfl.ch/page62923.html

Parlay

The provision of value-added telephony services is by now mainly in the hands of network operators. This might change soon: OSA and Parlay specify an open, secure interface to the telephony network, which can open the telephony network to 3^rd party service providers.

20 years ago, the implementation and deployment of value-added telephony services was the domain of manufacturers of telecom equipment. Telecom services of these days were, for example, call forwarding or televoting. Manufacturers were implementing the services according to the requirements from the network operator. Later, in the early nineties, the concept of Intelligent Networks (IN) was introduced and deployed in the networks. By this, network operators were getting the means to develop and deploy value-added services on their own. The creation of services is done with a Service Creation Environment (SCE). Services are created graphically by putting single service building blocks together to form the service logic chain, and by customising these building blocks. This is still the current method of how most of the value added services are created, both in fixed and mobile networks. Examples of such services are Freephone, Split Charging or Premium Rate services, Televoting, and also the Universal Personal Number.

Parlay: API for new service providers

The Intelligent Networks technology does not allow external service providers to create and deploy services on their own through the network of a network operator. The main reason is the missing security features in IN – a Service Creation Environment has full access to the network operator’s signalling network SS7. Moreover, the third party service provider would have to invest millions into the necessary equipment. To solve these issues, the Parlay group was founded in 1998 by BT, DGM&S (today: Ulticom), Microsoft, Nortel Networks, and Siemens. The goal of Parlay is the specification and realisation of an open, technology-independent Application Programming Interface (API) in telecommunication networks. The Parlay API shall enable network operators, independent software manufacturers and service providers to offer products and services, which use the functionality of existing networks. This should not be restricted to one network type, but comprise various networks (see figure 1).

Standardisation of the API

The efforts of the Parlay group to bring the API specification into standardisation bodies succeeded already one year later. The 3^rd Generation Partnership Project (3GPP), in charge of specifying 3G mobile networks, adapted Parlay as the method for creating services in UMTS. 3GPP introduced this API under the abbreviation OSA - Open Service Architecture - which recently was renamed to Open Service Access. The API thus is nowadays referred to as OSA/Parlay API (or vice versa). Meanwhile, the API has also been adapted by ETSI in order to cover the fixed network side. All three bodies jointly develop the standard. Although these bodies partly publish their own specifications, they are all aligned and compatible. In the second quarter of 2002, the most recent version was subject to approval: Parlay 3.1, and OSA 1.1 / 3GPP Rel. 4 in ETSI / 3GPP respectively (1), (2), (3).

Structure of the API

The OSA/Parlay API consists of two groups of interfaces: ‘Framework Interfaces’ and ‘Service Interfaces’ (see figure 2).

The Framework Interfaces provide basic mechanisms prior to the usage of actual network functions. They comprise, for instance, Authentication and Authorisation to identify the application that wants to access the API. After successful authentication, the Discovery function can be used to query information about availability of network functions. Further functions comprise Online Subscription of service features or network functions, and further contractual service usage agreements. The access to the Framework is always the first step for the use of the OSA/Parlay API. Following this, the Service Interfaces can be used, as far as the application is authorised.

The Service Interfaces enable client applications to access the so-called ‘Service Capability Features’ (SCF). They represent the available network functions that can be used to implement telecommunication services for the end-customer. The following list gives an overview of the components contained in Parlay version 3.0, approved in December 2001:

• Call Control: Setup and control of connections
• User Interaction: playing announcements, DTMF recognition, Sending of SMS etc.
• User Status / User Location: e.g. phone switched on/off?, Localisation of the phone
• Data Session Control: e.g. for volume-based tariffing in GPRS
• Terminal Capabilities: to query to terminal capabilities
• Generic Messaging: converting messages, connection to mailbox etc.
• Connectivity Management: Realising QoS etc.
• Content based charging: tariffing based on the content of the transmitted data
• Account Management: Management of prepaid cards in mobile networks

1. http://www.parlay.org
2. http://www.3gpp.org
3. http://portal.etsi.org
4. http://www.eurescom.de/public/Events/2002/osa-workshop/default.asp 
5. http://www.eurescom.de/public/projects/P1100-series/p1110