Index: openacs-4/packages/acs-core-docs/www/object-system-design.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/object-system-design.adp,v diff -u -N -r1.4 -r1.4.2.1 --- openacs-4/packages/acs-core-docs/www/object-system-design.adp 25 Apr 2018 08:38:28 -0000 1.4 +++ openacs-4/packages/acs-core-docs/www/object-system-design.adp 2 Mar 2019 19:30:05 -0000 1.4.2.1 @@ -1,5 +1,5 @@ -{/doc/acs-core-docs {ACS Core Documentation}} {Object Model Design} +{/doc/acs-core-docs/ {ACS Core Documentation}} {Object Model Design} Object Model Design

Object Model -Design

<authorblurb>

By Pete Su, Michael Yoon, Richard Li, -Rafael Schloming

</authorblurb>
+Design
+

By Pete Su, Michael Yoon, Richard Li, Rafael Schloming

+OpenACS docs are written by the named authors, and may be edited by +OpenACS documentation staff.

Essentials

@@ -361,7 +363,7 @@ easily gain access to generic features. However, while the API itself doesn't enforce the idea that applications only use the object model for metadata, it is also the case that the data model -is not designed to scale to large type hierarchies. In the more +is not designed to scale too large type hierarchies. In the more limited domain of the metadata model, this is acceptable since the type hierarchy is fairly small. But the object system data model is not designed to support, for example, a huge type tree like the