Dear Al and all others,
for me is .LRN something like a package of OpenACS, but not
a simple package like "Wimpy Point", more a package of OACS
packages including some specialities to support Learning.
By the way we need much more than just a flavour "groupware
for universities/schools".
This discussion reminds me on complex systems (e.g.
mainframe operating systems) where we would have named
.LRN to be a "subsystem" with the attributes
- use as much of the underlying system (OACS) as possible -
one portal system for all e.g. or easy integration of
existing OACS packages into .LRN etc.
- special interfaces to OACS where necessary, external
authentication e.g.
- special integration to OACS where necessary, for example
internationalization needs different coding rules to
enable an OACS package to be included into .LRN
The recent .LRN development - internationalization and
external authentication - was initiated through and by
the .LRN community, but has greatly affected OACS.
So finally naming
.LRN a (or better THE) subsystem of OACS
would in my limited knowledge of the english language
describe at best the situation and intentions.
Michael
