Eclipse process framework: Difference between revisions

Content deleted Content added
Line 16:
Static page generation is useful, as a reference site, but additional effort has to occur 1) to move towards process orchestration (based upon [[SPEM]] models) and 2) provision of training resources (potentially by including SCORM/IMS modes for export). Process training, within organizations, is of paramount concern and the amount of rework to push EPF output into [[SCORM]]/[[IMS]] ready structures for presentation in an eLearning environments (on top of the initial process authoring effort) is prohibitive. Model transformation technology may help here.
 
The usability concerns wont be addressed until there is large scale adoption of the approach and interoperability issues around plug-ins drive the design to its optimum. The proposal is that process orchestration support ([[Wilos]] etc) and interoperability with elearning standards (to support migration of process data into training ___domain) would/might accelerate adoption.
 
==See also==