Index: openacs-4/packages/acs-core-docs/www/objects.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/objects.adp,v
diff -u -r1.1.2.12 -r1.1.2.13
--- openacs-4/packages/acs-core-docs/www/objects.adp	23 Jun 2016 08:32:45 -0000	1.1.2.12
+++ openacs-4/packages/acs-core-docs/www/objects.adp	19 Nov 2016 09:21:54 -0000	1.1.2.13
@@ -1,5 +1,5 @@
 
-<property name="context">{/doc/acs-core-docs {Documentation}} {OpenACS Data Models and the Object System}</property>
+<property name="context">{/doc/acs-core-docs {ACS Core Documentation}} {OpenACS Data Models and the Object System}</property>
 <property name="doc(title)">OpenACS Data Models and the Object System</property>
 <master>
 <include src="/packages/acs-core-docs/lib/navheader"
@@ -86,7 +86,7 @@
 for the PG version) file created when we <a class="link" href="packages" title="OpenACS Packages">created the package</a>.
 Then, do the following:</p><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140641346975088" id="idp140641346975088"></a>Describe the new type to the type
+<a name="idp140198988154544" id="idp140198988154544"></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  
@@ -142,7 +142,7 @@
 attributes, so there is no need for us to define them.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140641346988144" id="idp140641346988144"></a>Define a table in which to store your
+<a name="idp140198988135696" id="idp140198988135696"></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 <code class="computeroutput">note</code>, but also an <code class="computeroutput">acs_object</code>. The new table definition looks
@@ -166,7 +166,7 @@
 <code class="computeroutput">acs_objects</code>.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140641346969888" id="idp140641346969888"></a>Define a package for type specific
+<a name="idp140198988120400" id="idp140198988120400"></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:</p><pre class="programlisting">
@@ -213,7 +213,7 @@
 only" by default. We&#39;ll talk about this more later.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140641353326144" id="idp140641353326144"></a>Define a package body for type specific
+<a name="idp140198988107984" id="idp140198988107984"></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>
@@ -365,8 +365,8 @@
 <code class="computeroutput">acs_objects</code>. This means you
 should never use the fields in <code class="computeroutput">acs_objects</code> for application-specific
 purposes. This is especially true for the <code class="computeroutput">context_id</code> field.</p></li>
-</ul></div><div class="cvstag">($&zwnj;Id: objects.html,v 1.52.2.10 2016/06/21
-07:44:36 gustafn Exp $)</div>
+</ul></div><div class="cvstag">($&zwnj;Id: objects.xml,v 1.9.14.1 2016/06/23
+08:32:46 gustafn Exp $)</div>
 </div>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"