OpenACS 4 Object Model Requirements

-By Pete Su
+OpenACS 4 Object Model Requirements

Prev	Chapter�10.�Kernel Documentation	Next

OpenACS 4 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 +

I. Introduction

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 services were provided to applications in an ad-hoc and irregular fashion. Examples of such services include:

General Comments
User/groups
Attribute storage in user/groups
General Permissions
Site wide search
General Auditing

All of these services involve relating extra information and services to @@ -50,7 +49,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