Index: openacs-4/packages/glossary/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/glossary/www/doc/requirements.html,v diff -u -N -r1.3 -r1.4 --- openacs-4/packages/glossary/www/doc/requirements.html 11 Apr 2018 20:52:01 -0000 1.3 +++ openacs-4/packages/glossary/www/doc/requirements.html 12 Apr 2018 07:47:22 -0000 1.4 @@ -22,13 +22,13 @@

II. Vision Statement

The Glossary Package is based on the ACS 3.x glossary module which was simply - a repository for a site's terms and their definitions. + a repository for a site's terms and their definitions.

- In the process of migrating the glossary to an ACS 4.0 package, we will - expand it's feature set to support multiple contexts. A site, subsite, - group, user, or even document (a this point the document must exist in the database as an ACS object) may have one or more glossaries associated - with it. Terms may have illustrations (acs-content-repository). Each glossary can have its security set (acs-permissions), a workflow, and - optionally except user comments. A glossary's content will be stored in + In the process of migrating the glossary to an ACS 4.0 package, we will + expand its feature set to support multiple contexts. A site, subsite, + group, user, or even document (a this point the document must exist in the database as an ACS object) may have one or more glossaries associated + with it. Terms may have illustrations (acs-content-repository). Each glossary can have its security set (acs-permissions), a workflow, and + optionally except user comments. A glossary's content will be stored in the content repository and its presentation will use the ArsDigita Templating System (ATS). @@ -58,7 +58,7 @@

  • Mechanism for users to comment on terms. This feature is controlled by the administrator of the glossary via setting permissions.
    • - +