2011
DOI: 10.1016/j.compedu.2010.12.007
|View full text |Cite
|
Sign up to set email alerts
|

Generic service integration in adaptive learning experiences using IMS learning design

Abstract: IMS Learning Design is a specification to capture the orchestration taking place in a learning scenario. This paper presents an extension called Generic Service Integration. This paradigm allows a bidirectional communication between the course engine in charge of the orchestration and conventional Web 2.0 tools. This communication allows the engine to configure external services so as to adjust their behav-iour, and also retrieve information about their activity and use it to influence the orchestration proces… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
20
0
5

Year Published

2012
2012
2019
2019

Publication Types

Select...
5
2

Relationship

2
5

Authors

Journals

citations
Cited by 34 publications
(25 citation statements)
references
References 28 publications
0
20
0
5
Order By: Relevance
“…That is, the learning script must contain a description of the case specific tools (i.e. Google Spreadsheets), with the required vocabulary as defined by GSI [42].…”
Section: Formalization Of the Flow With Ims Ldmentioning
confidence: 99%
See 3 more Smart Citations
“…That is, the learning script must contain a description of the case specific tools (i.e. Google Spreadsheets), with the required vocabulary as defined by GSI [42].…”
Section: Formalization Of the Flow With Ims Ldmentioning
confidence: 99%
“…Apart from its sequencing capabilities, IMS LD also facilitates the reusability of learning courses. The GSI extension was proposed to improve IMS LD by allowing generic tools to be integrated in a conventional activity flow [27]. The work described in this document uses IMS LD reusability to comply with requirement Req2, and evaluates how GSI can overcome the IMS LD drawbacks when used in CSCBL scripts.…”
Section: Technological Support For the Orchestrationmentioning
confidence: 99%
See 2 more Smart Citations
“…These approaches may reduce the development e ort by fostering a high code reuse among integrations, but at the cost of supporting only generic functional commonalities, due to the existing heterogeneity in VLE and tools contracts. For example, the GSI architecture [Fue11] was designed to foster a many-to-many integration with IMS LD compliant platforms and third-party services. Ad hoc integration approaches, however, typically foster a one-to-one integration, and so, they can achieve a richer communication between VLEs and tools.…”
Section: Architectural Approachesmentioning
confidence: 99%