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.34 -r1.35 --- openacs-4/packages/acs-core-docs/www/object-system-requirements.html 27 Oct 2014 16:39:23 -0000 1.34 +++ openacs-4/packages/acs-core-docs/www/object-system-requirements.html 7 Aug 2017 23:47:51 -0000 1.35 @@ -1,5 +1,5 @@ -Object Model Requirements

Object Model Requirements

By Pete Su

+Object Model Requirements

Object Model Requirements

By Pete Su

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

I. Introduction

A major goal in OpenACS 4 is to unify and normalize many of the core services @@ -50,7 +50,7 @@ OpenACS application had to manage access control to its data separately. Later on, a notion of "scoping" was introduced into the core data model.

"Scope" is a term best explained by example. Consider some -hypothetical rows in the address_book table:

...scopeuser_idgroup_id...
...user123 ...
...group 456...
...public ...

The first row represents an entry in User 123's personal address book, +hypothetical rows in the address_book table:

...scopeuser_idgroup_id...
...user123 ...
...group 456...
...public ...

The first row represents an entry in User 123's personal address book, the second row represents an entry in User Group 456's shared address book, and the third row represents an entry in the site's public address book.

In this way, the scoping columns identify the security context in which a @@ -261,7 +261,7 @@ application's data model. In other words, it should be easy to "hook into" the object model, and that ability should not have a major impact on the application data model.

Note: Is the API the only way to obtain values? How does -this integrate with application level SQL queries?

Revision History

Document Revision #Action Taken, NotesWhen?By Whom?
0.1Creation08/10/2000Bryan Quinn
0.2Major re-write08/11/2000Pete Su
0.3Draft completed after initial reviews08/22/2000Pete Su
0.4Edited, updated to conform to requirements template, pending freeze08/23/2000Kai Wu
Final edits before freeze08/24/2000Pete Su
0.5Edited for consistency08/27/2000Kai Wu
0.6Put Object ID stuff first, because it makes more sense08/28/2000Pete Su
0.7Added requirement that knowledge-level objects must be moveable between +this integrate with application level SQL queries?

Revision History

Document Revision #Action Taken, NotesWhen?By Whom?
0.1Creation08/10/2000Bryan Quinn
0.2Major re-write08/11/2000Pete Su
0.3Draft completed after initial reviews08/22/2000Pete Su
0.4Edited, updated to conform to requirements template, pending freeze08/23/2000Kai Wu
Final edits before freeze08/24/2000Pete Su
0.5Edited for consistency08/27/2000Kai Wu
0.6Put Object ID stuff first, because it makes more sense08/28/2000Pete Su
0.7Added requirement that knowledge-level objects must be moveable between databases.08/29/2000Richard Li
0.8Rewrote 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/2000Pete Su
0.9Edited for ACS 4 Beta release.09/30/2000Kai Wu
View comments on this page at openacs.org
+requirements on relation types.
09/06/2000Pete Su
0.9Edited for ACS 4 Beta release.09/30/2000Kai Wu