On 10/05/2011 09:26, Pat Lockley wrote:
>> An enterprise service bus-based tool.
>>
>> An ESB is like a Swiss army knife for dealing with information through the
>> use of Web services, SOAPian, RESTian or OTHERian.
>>
>> The ESB has a set of Web services and a mediation layer for operating on Web
>> service requests and responses.
> So JSON, XML, Atom?
>
de rigeur
>> For example, one ESB service in the tool would be to automatically create a
>> manifold of document formats from one given format: html, odf, pdf, e-book,
>> plain text, ppt. A teacher can attach a preferred editing tool to the bus
>> which will then produce a document manifold.
> Multiple formats
>
More generally, information channel manifolds. As well as multiple
formats there can be different security options - oAuth, OpenID, and
even (whisper it) shibboleth, and different options for obtaining the
resources (Web app, Web service, push, pull).
The philosophy is to offer a broad range of services to maximise the
likelihood of connecting with a learner's PLE preferences. If all this
is done programmatically, it shouldn't create extra burdens on staff.
Write one, deliver many.
>> An ESB service would be responsible for mediation, assembly and dispatch of
>> information in the correct format for the requesting device.
> and content modification
>
mashing, splashing, XSLT, accessibilitification, security headers...
>> The ESB would have a presence module so that notifications can be sent out
>> to a student via email or sms or whatever suits his or her given presence
>> state.
> Updates / subscription
>
A student would set preferences for information channels according to
presence registered with presence server: I am on a train, I am in the
bath...
>> The ESB would have a workflow manager to keep track of long-running
>> educational processes.
> Such as?
Any of the learning designs that have been published in the realms of IMS LD and LAMS can be implemented using BPEL and JBI. JBI has bindings to connect Web services to email, sms, databases, LDAP, JMS... As JBI is allowed to pass away, I think Apache Camel can probably fill the breach.
For example, as a follow-up to the JISC AMSeT project I have implemented the "What is...?" learning design. The AMSeT team is no longer at Leeds and they pulled the servers. As soon as I can re-establish the site I will publish the workflow.
>> There would also be a service for detecting and destroying SCORM modules.
> Skynet?
Perfect! (I would have to apply to JISC to write a JBI Skynet binding.)
> Pat
>
>
Essentially, a move from static to dynamic OER.
|