Five years for five perspectives on TELOS

Ioan Rosca, PhD. in educational technology telecommunication, computer, information and instructional systems engineer

researcher and conceptual architect at LICEF, Teleuniversity, Montréal

ioan.rosca@licef.teluq.uquam.ca

LOR06, Montreal, 10 November, 2006

Summary

• Introduction : history of a conceptual quest

• Main objectives: produce, deliver, intermediate

• Vision 1: extending the resources space; emergent mode

• Vision 2: reproducing processes; orchestrating mode

• Vision 3: distributing services; technical match

• Vision 4: managing knowledge evolution; semantic match

• Vision 5: managing production cascades; administrative match

• Current work: managing service negotiation

History of a conceptual quest: a retrospective perspective

MOT, Explora, Adisa, IONVal, Gadisa, SavoirNet

Conceptual quest

GEFOTELOS0

TELOS dev

20062005

Technical architecture

Conceptual refinement

consolidation

200820031999

Previouswork

conceptualarchitecture

104

Data

SchEd DataEdAdisa f

schema

LinkEd

xxxschema

2.5fa(104)ha(212)h

a(214)h

104d1

212d1

a(104212,214)i

P1

e104ge212gexxxg

data

library

edstyleGADISA

104d22.5g

f(104e,212,214)

data

functioneditor

functional aggregation

2.2 aVALfunction

explorer

metaf

2.2 b

b Adisa1 online/offline

ADISA

d104

e104e212

d104

exxx

MOT

EXPLORA

MISA (DE104,212,214,xxx)

35 editors

e104a

exxxa

2.1a

dxxx

semnatic “bus”2.4

K ref

serviceclient

data adaptor

adviserExplora

adviserepiphyte

service bus

Adisaserviceserver

kernel

2.3a

2.3b

e104de212de214d

d104d212d214

Adisa d 1d

e104be212b

Adisa 1+

exxxb

2.1b

d104

e104c

exxxc

user context

Rins

Rpro

Racc

central context

SREnv

PRwsc

Fa

Ba

designer context

ION resources aggregator

Adisac

ResEdit ResMan ResCon DocMan

D

2.1c

2.1c

LKMA(lesson)

LKMP C(K)

D(K) P(K)

T F(K)

LKMS(platform)D manager

T manager

P manager

F manager

K manager

LKMA manager LKMP manager

1 Produce

Core factory Core libraries

Resources andservices provider

2 Deliver

LKMA(lesson)

LKMS(platform)

C(K)LKMP

Resources and services obtainer

3 Mediate

Resource repositories

Serviceproviders

C(K)

LKMS(platform)

LKMA(lesson)

LKMPMain objectives: produce, deliver, mediate

us

TELOS

agcofi us pu

1 using and extending resources repositories

e

TELOS

e

e

e

e

E

TELe

2 modeling, managing, andreproducing processes

P

S

Mm

m

uTELOS

tata’

si disw

di

dis

uaa,r

sa

us

ob

sa

d,d

3 distributing objectsand services

4e1 e3e2

e4

TELOS

n

pr

irdo

fu

d ip

ed

u r,p

ac

fi

us

R

4 managing global knowledge evolution

a2Sa1

a4a3

de lete

p1 p4

c3c2c1

p3

p5 p8p7

p2

p6

TELOS -coreLKMS library LKMA LKMP

s1

s2

5 administrating production cascades

ob2ob1 ob3o1 o2

p2

a primary procedure

p1

rsps

persons

objectsoperations

supportresource support person

b abstract procedure model

o1i1 i2

is1

o2 i3

as2

a1 a2

composemodel

author Functioneditor

function operationsdirectoriesabstract actors

abstractinstruments

adapter

concretiseelements

Functionadaptor

resources repositories

person directories

knowledge reference system

o1

is1

o2

as2

a1 a2

ob x

rs x ps x c model with concretised elements

user

finds andexecutes

Functionexecutor

e1

is1

e2

as2

a1 a2

d secondary procedure based on function execution

ob x

rs x ps x

ob y ob z

executedoperation

px py

analyst

Functionanalyser

recordreact

e meta-procedure of functional cycle

Adapting orchestrations

From learning to explanation

learning topologies

participate consultdialog

CiCf

Ci,Cf

consult

i

f

ka kb kc kd ke

M

0%

100%

learning: activities as competence operators i-f

mastershipmeasured

competences

c1ic1f

explain

Ci?Cf?

c2ic2f

explain

c3ic3f

explain

effects of explanationon various learners

kk1

k2 k3

k1.1k1.2

knowledgerefining

competences

i

k1.3

k1.3.1 k1.3.2k3.1 k3.2

f

• Explicative capacities and pedagogical indexation. In order to observe the competence equilibrium around pedagogical operations, I have organised the competences space of a person P on "postures": (knowK, aimK, explainK(x,y), describeK(x,y), recommendK(x,y), evaluateK(x,y))- where the parenthesis show a predicate depending on the detained (x) or aimed (y) "mastering level" of the person to which P could explain directly (transmit by a document, evaluate, recommend etc) the knowledge k. The indexation of explicative documents poses similar problems to that of referencing support persons. They can be partially considered the author's representative towards the expected user (minus the interactivity limitations). That is why I have also characterised their explicative potential by (c1,c2) increases.

O

O

E

a state changesfor Toedatopology

O

D

E

A

d a

e

o

D

E

A

d a

e

O

D

E

A

e

O

D

E

A

a

e

O

D

E

A

d

e

O

D

E

A

d a

O

D

E

A

O

D

E

A

a

O

D

E

A

d

O

E

ed n

c1 c2

?

f2

R

b global allocationproblem

f1

8 Competence optimization

Service negotiation with TERMS

actor

work

syst

askservice

grou

categ

part lkmp

lkma

lkms

assist

deliv

suppdoc

filter

solvetransac

solvecompl

memor

solveconcur

manage

O

D

E

A

O

D

E

A

d a

O

D

E

A

d a

e

o

D

E

A

d a

e

O

D

E

A

e

TERMS

define

x

servicess1

y

propose

offerso1s1

z

negoti

accept

contractsc1o1s1c2d1s1

vu

answerrequ

demandsd1s1

negot

TERMS - Telelearning Extended Rights Management System

Technological background

• TERMS is built on a multi-tier J2EE architecture inspired by the MVC model that is designed to scale well on a cluster of front-end and back-end servers.

• The data layer uses the DAO pattern, providing a bridge between the data servers (HypersonicSQL, MySQL or other SQL-compliant data server) and the business layer (implemented in EJBs).

• The front-end is handled by servlets and JSPs, designed with action patterns in mind, extended with custom tag libraries, filters, listeners and additional web development frameworks (WebWork, Sitemesh).

• The Web Services access gate is implemented with the xFire framework, providing full WSDL and SOAP support.

• Designed to be portable across different servlet runners and EJB containers, TERMS currently uses Resin Caucho as its application server, using the Hessan binary protocol for fast access between front-end and back-end.

• Security is handled both explicitly and through the servlet runner's security roles and constraints, the application fully supporting Secure HTTP, through JNI and OpenSSL.

• The current payment mechanism uses Verisign's Java API, but can easily be swapped with alternatives.

• Other involved technologies include the ANT build platform, the JUnit testing package, the java activation framework, JAAS, SAAJ, MAIL, XML Parsers (Crimson, JAXP, JDOM...), log4j, Spring etc.