Object Model Requirements

By Pete Su

+Object Model Requirements

Prev	Chapter 15. Kernel Documentation	Next

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:

...	`scope`	`user_id`	`group_id`	...
...	`user`	`123`		...
...	`group`		`456`	...
...	`public`			...

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

...	`scope`	`user_id`	`group_id`	...
...	`user`	`123`		...
...	`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, 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 +this integrate with application level SQL queries?

Revision History

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

Prev	Home	Next
Overview	Up	Object Model Design

docs@openacs.org

View comments on this page at openacs.org +requirements on relation types.

09/06/2000

Pete Su

0.9

Edited for ACS 4 Beta release.

09/30/2000

Kai Wu

Prev	Home	Next
Overview	Up	Object Model Design

docs@openacs.org