e-Framework Technical Approach

Various authors, e-Framework, Jul 10, 2009
Commentary by Stephen Downes

eFramework, which was discussed here yesterday, has released its technical model. It contains three parts: the rationale, the technical model itself, and considerations for implementation in an enterprise architecture. The rationale is very similar to that of learning objects: "In the service-oriented view of software design, only one spell check service is needed. This service exists somewhere on the internet, and provides a standard interface by which other applications can make use of it." Sounds good in principle. Collapses under the weight of service architecture, access federations, and localization requirements. That doesn't mean a return to the world of silos. But the model of "one spell-checker to rule them all" simply has too many downsides.
Views: 0 today, 130 total (since January 1, 2017).[Direct Link]
Creative Commons License. gRSShopper

Copyright 2015 Stephen Downes ~ Contact: stephen@downes.ca
This page generated by gRSShopper.
Last Updated: Oct 20, 2017 02:49 a.m.