Index: openacs-4/packages/acs-core-docs/www/objects.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/objects.html,v
diff -u -r1.43.2.2 -r1.43.2.3
--- openacs-4/packages/acs-core-docs/www/objects.html	20 Oct 2005 18:06:24 -0000	1.43.2.2
+++ openacs-4/packages/acs-core-docs/www/objects.html	30 Nov 2005 05:21:56 -0000	1.43.2.3
@@ -2,7 +2,7 @@
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
         </div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="objects-overview"></a>Overview</h3></div></div></div><p>
-Developing data models in OpenACS 5.2.0b5 is much like developing data models
+Developing data models in OpenACS 5.2.0b8 is much like developing data models
 for OpenACS 3, save for the implementation.  As usual, you need to examine
 how to model the information that the application must store and
 manipulate, and define a suitable set of SQL tables.  In our Notes
@@ -78,7 +78,7 @@
 Fire up your text editor and open the
 <code class="computeroutput">ROOT/packages/notes/sql/oracle/notes-create.sql</code> (<code class="computeroutput">ROOT/packages/notes/sql/postgresql/notes-create.sql</code> for the PG version) file created
 when we <a href="packages.html" title="OpenACS Packages">created the package</a>.  Then, do the following:
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2578137"></a>Describe the new type to the type system</h4></div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2560129"></a>Describe the new type to the type system</h4></div></div></div><p>
 First, add an entry to the <code class="computeroutput">acs_object_types</code> table with the following PL/SQL call:
 </p><pre class="programlisting">
 begin  
@@ -138,7 +138,7 @@
 because the new type <code class="computeroutput">note</code> is a subtype of
 <code class="computeroutput">acs_object</code>, it will inherit these attributes, so there is
 no need for us to define them.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2581334"></a>Define a table in which to store your objects</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2585294"></a>Define a table in which to store your objects</h4></div></div></div><p>
 The next thing we do is make a small modification to the data model to
 reflect the fact that each row in the <code class="computeroutput">notes</code> table
 represents something that is not only an object of type
@@ -163,7 +163,7 @@
 use the <code class="computeroutput">acs_objects</code> table to find objects will
 transparently find any objects that are instances of any subtype of
 <code class="computeroutput">acs_objects</code>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570831"></a>Define a package for type specific procedures</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2581393"></a>Define a package for type specific procedures</h4></div></div></div><p>
 The next step is to define a PL/SQL package for your new type, and
 write some basic procedures to create and delete objects. Here is a
 package definition for our new type:
@@ -211,7 +211,7 @@
 object OBJ was "read only", then any other object that used OBJ as its
 context would also be "read only" by default. We'll talk about this more
 later.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570919"></a>Define a package body for type specific procedures</h4></div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2563831"></a>Define a package body for type specific procedures</h4></div></div></div><p>
 The PL/SQL package body contains the implementations of the procedures
 defined above. The only subtle thing going on here is that we must use
 <code class="computeroutput">acs_object.new</code> to insert a row into
@@ -314,7 +314,7 @@
 models that are meant to be integrated with the OpenACS object
 system. 
 </p><p>
-There are two basic rules you should follow when designing OpenACS 5.2.0b5 data
+There are two basic rules you should follow when designing OpenACS 5.2.0b8 data
 models:
 
 
@@ -369,7 +369,7 @@
 requires a good amount of thought at design time even for simple
 applications.
 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="objects-summary"></a>Summary</h3></div></div></div><p>
-Hooking into the OpenACS 5.2.0b5 object system brings the application developer
+Hooking into the OpenACS 5.2.0b8 object system brings the application developer
 numerous benefits, and doing it involves only four easy steps: