Stephen Downes

Knowledge, Learning, Community
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.

Today: 1054 Total: 1056 [Direct link]

Image from the website


Stephen Downes Stephen Downes, Casselman, Canada
stephen@downes.ca

Copyright 2024
Last Updated: Mar 28, 2024 09:28 a.m.

Canadian Flag Creative Commons License.

Force:yes