Index: openacs-4/packages/acs-content-repository/www/doc/object-model.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/object-model.html,v diff -u -N -r1.1.1.1 -r1.1.1.1.30.1 --- openacs-4/packages/acs-content-repository/www/doc/object-model.html 13 Mar 2001 22:59:26 -0000 1.1.1.1 +++ openacs-4/packages/acs-content-repository/www/doc/object-model.html 22 Jun 2016 07:40:41 -0000 1.1.1.1.30.1 @@ -1,46 +1,46 @@ - -
-The content repository is an extension of the ACS Object Model. -The following diagram illustrates the relationship among the -standard object types defined by the content repository (click on -a box to view a description and API summary for a particular object -type):
- - - - -Note that content revisions and content items inherit separately -from the root of the object model. Each item may be related to one or -more revisions, but they are fundamentally different types of -objects.
- -Also important to note is the relationship between custom content types -and the rest of the object model. You define new content types as -subtypes of Content Revision, not of Content Item. This is because -new content types are characterized by their attributes, -which are stored at the revision level to make changes easy to -audit. Custom content types typically do not require additional -unaudited attributes or methods beyond those already provided by -the Content Item type. It is thereful almost never necessary to -create a custom subtype of Content Item itself.
- -The content repository is an extension of the ACS Object Model. +The following diagram illustrates the relationship among the +standard object types defined by the content repository (click on +a box to view a description and API summary for a particular object +type):
+ + + + +Note that content revisions and content items inherit separately +from the root of the object model. Each item may be related to one or +more revisions, but they are fundamentally different types of +objects.
+ +Also important to note is the relationship between custom content types +and the rest of the object model. You define new content types as +subtypes of Content Revision, not of Content Item. This is because +new content types are characterized by their attributes, +which are stored at the revision level to make changes easy to +audit. Custom content types typically do not require additional +unaudited attributes or methods beyond those already provided by +the Content Item type. It is thereful almost never necessary to +create a custom subtype of Content Item itself.
+ +