The ACS 4x Glossary Package never made it beyond alpha
stage. Mainly because several acs-subsite and services issues
weren't resolved while I was still at aD (some still linger).
The design of the Glossary Package was meant to show how
one could make a simple ACS 3x module much more powerful
in the ACS 4 world via code reuse through acs-content-
repository, acs-workflow, and general comments. In fact, it was
originally to be the basis of ASJ article. These added
dependencies, all with their own issues, made the Glossary
impossible to finish in a clean manner at the time. In other
words, its a great example of what's good and bad about the
unfinished ACS 4x platform.
At this point, OpenACS 4 is a huge step forward in resolving
ACS 4 pitfalls. I think the Glossary can be a good stand alone
package, but one now has to look at what has changed in all its
dependencies as well.
