Index: openacs-4/packages/acs-core-docs/www/object-system-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/object-system-requirements.html,v diff -u -r1.6.2.6 -r1.6.2.7 --- openacs-4/packages/acs-core-docs/www/object-system-requirements.html 19 Apr 2003 20:39:32 -0000 1.6.2.6 +++ openacs-4/packages/acs-core-docs/www/object-system-requirements.html 29 Apr 2003 05:58:33 -0000 1.6.2.7 @@ -1,7 +1,7 @@
A major goal in OpenACS 4 is to unify and normalize many of the core services of the system into a coherent common data model and API. In the past, these @@ -127,7 +127,7 @@ that store metadata on application objects. The object type system supports subtyping with inheritance, so new object types can be defined in terms of existing object types.
The OM data model forms the main part of the OpenACS 4 Kernel data model. The -other parts of the Kernel data model include:
Parties and Groups
Permissions
Each of these is documented elsewhere at length.
The data model for the object system provides support for the following +other parts of the Kernel data model include:
Parties and Groups
Permissions
Each of these is documented elsewhere at length.
The data model for the object system provides support for the following kinds of schema patterns that are used by many existing OpenACS modules:
Object identification is a central mechanism in the new metadata system. The fact that every object has a known unique identifier means that the core can deal with all objects in a generic way. Thus the only action required of @@ -265,4 +265,4 @@ this integrate with application level SQL queries?
Document Revision # | Action Taken, Notes | When? | By Whom? |
0.1 | Creation | 08/10/2000 | Bryan Quinn |
0.2 | Major re-write | 08/11/2000 | Pete Su |
0.3 | Draft completed after initial reviews | 08/22/2000 | Pete Su |
0.4 | Edited, updated to conform to requirements template, pending freeze | 08/23/2000 | Kai Wu |
� | Final edits before freeze | 08/24/2000 | Pete Su |
0.5 | Edited for consistency | 08/27/2000 | Kai Wu |
0.6 | Put Object ID stuff first, because it makes more sense | 08/28/2000 | Pete Su |
0.7 | Added requirement that knowledge-level objects must be moveable between databases. | 08/29/2000 | Richard Li |
0.8 | Rewrote intro to match language and concepts in the design document. Also cleaned up usage a bit in the requirements section. Added short vague -requirements on relation types. | 09/06/2000 | Pete Su |
0.9 | Edited for ACS 4 Beta release. | 09/30/2000 | Kai Wu |