Index: openacs-4/packages/acs-events/www/doc/design.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-events/www/doc/design.html,v
diff -u -r1.1.1.1 -r1.1.1.1.28.1
--- openacs-4/packages/acs-events/www/doc/design.html	12 Jun 2001 03:56:20 -0000	1.1.1.1
+++ openacs-4/packages/acs-events/www/doc/design.html	22 Jun 2016 08:19:32 -0000	1.1.1.1.28.1
@@ -15,7 +15,7 @@
 <ul>
     <li> Tcl script directory (link to the API browser page for the package)  </li>
     <li> PL/SQL file (link to the API browser page for the package)  </li>
-    <li> Data model: <a href="/doc/sql/display-sql?url=acs-events-create.sql&package_key=acs-events">acs-events-create.sql</a> </li>
+    <li> Data model: <a href="/doc/sql/display-sql?url=acs-events-create.sql&amp;package_key=acs-events">acs-events-create.sql</a> </li>
     <p>
     <li> <a href="requirements.html">Requirements document</a> </li>
     <li> ER diagram </li>
@@ -29,10 +29,10 @@
 The ACS events service is primarily intended for use by writers of
 application packages and other service packages. The service allows
 developers to specify and manipulate relationships (possibly
-recurring) between a <i>set of intervals in time</i>, an
-<i>activity</i>, and an arbitrary number of <i>parties</i>. An
+recurring) between a <em>set of intervals in time</em>, an
+<em>activity</em>, and an arbitrary number of <em>parties</em>. An
 activity can be associated with an arbitrary number of ACS
-<i>objects</i>.  
+<em>objects</em>.  
 </p>
 <p>
 The package doesn't provide for any interpretation of events, leaving
@@ -52,24 +52,24 @@
 requirements for each of these areas in the following ways:
 </p>
 <p>
-<b>Events:</b> The service creates a new subtype of acs_object:
+<strong>Events:</strong> The service creates a new subtype of acs_object:
 acs_event.  It creates an auxiliary table for mapping events to
 parties.  It provides an API for manipulating and querying events and their
 associated time interval sets, activities, recurrences, and parties.
 </p>
 <p>
-<b>Time Intervals:</b> The service creates tables for storing time
+<strong>Time Intervals:</strong> The service creates tables for storing time
 intervals and sets of time intervals.  It provides an API for
 manipulating and querying time intervals and time interval sets.
 </p>
 <p>
-<b>Activities:</b> The service creates a new subtype of acs_object:
+<strong>Activities:</strong> The service creates a new subtype of acs_object:
 acs_activity.  It creates an auxiliary table for mapping activities to
 objects.  It provides an API for manipulating activities, their
 properties, and their associated objects.
 </p>
 <p>
-<b>Recurrences:</b> The service creates a table for storing
+<strong>Recurrences:</strong> The service creates a table for storing
 information on how an event recurs, including how the event recurs and
 when it stops recurring. It provides an API for manipulating
 recurrence information and recurring events.  This includes a function
@@ -157,15 +157,15 @@
 <p>
 The 4.0 ACS Events service doesn't enforce a particular policy to
 prevent problems, but it does provide mechanisms that a well-designed
-application can use.  The keys are the <b>event_recurrence.insert_events</b>
-procedure and the <b>partially_populated_events</b> view.
+application can use.  The keys are the <strong>event_recurrence.insert_events</strong>
+procedure and the <strong>partially_populated_events</strong> view.
 </p>
 <p>
-<b>insert_events</b> takes either an event_id or a recurrence_id and a
+<strong>insert_events</strong> takes either an event_id or a recurrence_id and a
 cutoff date.  It either uses the recurrence_id, or gets it from the
 event_id, to retrieve the information needed to generate the dates of
 the recurrences.  When inserting a recurring event for the first time,
-the application will need to call <b>insert_events</b> with a
+the application will need to call <strong>insert_events</strong> with a
 reasonable populate_until date.  For calendar, for example, this could
 be sysdate + the lookahead limit.
 </p>
@@ -200,7 +200,7 @@
 For the days_of_week column, the representation chosen, a
 space-delimited list of integers, has a number of advantages.  First,
 it is easy and reasonably efficient to generate the set of dates
-corresponding to the recurrences.  <b>insert_events</b> takes each
+corresponding to the recurrences.  <strong>insert_events</strong> takes each
 number in the list in turn and adds it to the date of the beginning of
 the week.  Second, the Tcl and Oracle representations are equivalent
 and the translations to and from UI are straightforward.  In
@@ -275,33 +275,33 @@
 <h4>Events</h4>
 
 <p>
-This is the main abstraction in the package.  <tt>acs_event</tt> is a
-subtype of <tt>acs_object</tt>.  In addition to the
-<tt>acs_events</tt> table, there is an <tt>acs_event_party_map</tt>
-table which maps between parties and events.  The <tt>acs_event</tt>
-package defines <tt>new</tt>, <tt>delete</tt>, various procedures to
-set attributes and <tt>recurs_p</tt> indicating whether or not a
+This is the main abstraction in the package.  <kbd>acs_event</kbd> is a
+subtype of <kbd>acs_object</kbd>.  In addition to the
+<kbd>acs_events</kbd> table, there is an <kbd>acs_event_party_map</kbd>
+table which maps between parties and events.  The <kbd>acs_event</kbd>
+package defines <kbd>new</kbd>, <kbd>delete</kbd>, various procedures to
+set attributes and <kbd>recurs_p</kbd> indicating whether or not a
 particular event recurs.
 </p>
 
 <h4>Time Interval Sets</h4>
 
 <p>
 Because time interval sets are so simple, there is no need to make
-them a subtype of <tt>acs_object</tt>.  Interval sets are represented
+them a subtype of <kbd>acs_object</kbd>.  Interval sets are represented
 with one table to represent time intervals, and a second table which
 groups intervals into sets, with corresponding PL/SQL packages
-defining <tt>new</tt>, <tt>delete</tt>, and additional manipulation functions.
+defining <kbd>new</kbd>, <kbd>delete</kbd>, and additional manipulation functions.
 </p>
 
 <h4>Activities</h4>
 
 <p>
-This is the secondary abstraction in the package.  <tt>acs_activity</tt> is a
-subtype of <tt>acs_object</tt>.  In addition to the
-<tt>acs_activities</tt> table, there is an <tt>acs_activity_object_map</tt>
-table which maps between objects and activities.  The <tt>acs_activity</tt>
-package defines <tt>new</tt>, <tt>delete</tt>, and various procedures to
+This is the secondary abstraction in the package.  <kbd>acs_activity</kbd> is a
+subtype of <kbd>acs_object</kbd>.  In addition to the
+<kbd>acs_activities</kbd> table, there is an <kbd>acs_activity_object_map</kbd>
+table which maps between objects and activities.  The <kbd>acs_activity</kbd>
+package defines <kbd>new</kbd>, <kbd>delete</kbd>, and various procedures to
 set attributes and mappings.
 </p>
 
@@ -310,15 +310,15 @@
 <p>
 Since recurrences are always associated with events, there seemed to
 be no need to make them objects.  The information that determines how
-an event recurs is stored in the <tt>event_recurrences</tt> table.
+an event recurs is stored in the <kbd>event_recurrences</kbd> table.
 </p>
 <p>
-The <tt>event_recurrence</tt> package defines <tt>new</tt>,
-<tt>delete</tt>, and other procedures related to recurrences.  The key
-procedure is <tt>insert_events</tt>.
+The <kbd>event_recurrence</kbd> package defines <kbd>new</kbd>,
+<kbd>delete</kbd>, and other procedures related to recurrences.  The key
+procedure is <kbd>insert_events</kbd>.
 </p>
 <p>
-A view, <tt>partially_populated_events</tt>, is created which hides
+A view, <kbd>partially_populated_events</kbd>, is created which hides
 some of the details of retrieving recurrences that need to populated further.
 </p>
 
@@ -412,10 +412,10 @@
 
 <h3>XII.  Revision History</h3>
 
-<table cellpadding=2 cellspacing=2 width=90% bgcolor=#efefef>
-<tr bgcolor=#e0e0e0>
-    <th width=10%>Document Revision #</th>
-    <th width=50%>Action Taken, Notes</th>
+<table cellpadding="2" cellspacing="2" width="90%" bgcolor="#efefef">
+<tr bgcolor="#e0e0e0">
+    <th width="10%">Document Revision #</th>
+    <th width="50%">Action Taken, Notes</th>
     <th>When?</th>
     <th>By Whom?</th>
 </tr>