On 10/05/2011 11:17, Pat Lockley wrote:
>> mashing, splashing, XSLT, accessibilitification, security headers...
> Would XSLT be ran by the consumer - not the provider?
XSLT would be a major player on the provider side in a whole range of
circumstances: converting DocBook to pdf, creating and customising SVG
graphics, Web service payload editing, handling Atom files, creating
Jasper reports....
If an information channel returns XML to a consumer then he or she is
welcome to do anything with it, including an XSLT transformation.
However, to expect or require a consumer to use XSLT explicitly is not
such a good idea. The PLE will consist of a set of tools that will
accept information in different formats. Provide information through a
range of channels that is most likely to hit the PLE toolset and let the
students get on with it.
>>>> 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.
> I can't make sense of Apache Camel - but could it be simplified into
> support for new templates to be added in?
>
>
I don't think that this is the right question to ask of Camel. The
template stuff would come in at the process level - BPMN/BPEL although a
tutor would need to know nothing of this. The processes carry out
sequences of operations on documents - copying, moving, creating,
aggregating. Reusability is achieved by processing different sets of
documents at different stages in the process. For example, to initiate
a learning design you might provide a set of documents to the students.
One way of doing this is to copy all files in a tutor's initial
information folder to all students. Different learning designs,
different sets of initial documents, and similarly at different points
during the workflow.
Regards,
Brian
|