Index: openacs-4/packages/acs-content-repository/www/doc/requirements.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/requirements.adp,v
diff -u -r1.4 -r1.5
--- openacs-4/packages/acs-content-repository/www/doc/requirements.adp	30 Apr 2018 08:15:07 -0000	1.4
+++ openacs-4/packages/acs-content-repository/www/doc/requirements.adp	3 Sep 2024 15:37:31 -0000	1.5
@@ -1,7 +1,11 @@
 
-<property name="context">{/doc/acs-content-repository {ACS Content Repository}} {Content Repository Requirements}</property>
+<property name="context">{/doc/acs-content-repository/ {ACS Content Repository}} {Content Repository Requirements}</property>
 <property name="doc(title)">Content Repository Requirements</property>
 <master>
+<style>
+div.sect2 > div.itemizedlist > ul.itemizedlist > li.listitem {margin-top: 16px;}
+div.sect3 > div.itemizedlist > ul.itemizedlist > li.listitem {margin-top: 6px;}
+</style>              
 <h2>Content Repository Requirements</h2>
 
 Karl Goldstein (<a href="mailto:karlg\@arsdigita.com">karlg\@arsdigita.com</a>
@@ -133,17 +137,17 @@
 <p>
 <strong>40.10</strong>. The data model must support the
 hierarchical organization of content items in a manner similar to a
-file system.</p><p>
+filesystem.</p><p>
 <strong>40.20</strong>. The URL of a content item should reflect
 its location in the hierarchy. For example, a press release with
 the URL <kbd>/press-releases/products/new-widget</kbd> is located
 at the third level down from the root of the hierarchy.</p><p>
 <a name="folder" id="folder"><strong>40.20.5 Content
 Folder</strong></a>.</p><p>A <em>folder</em> is analogous to a folder or directory in a
-file system. It represents a level in the content item hierarchy.
-In the previous example, <kbd>press-releases</kbd> is a folder
-under the repository root, and <kbd>products</kbd> is folder within
-that. The description of a folder may include the following
+filesystem. It represents a level in the content item hierarchy. In
+the previous example, <kbd>press-releases</kbd> is a folder under
+the repository root, and <kbd>products</kbd> is folder within that.
+The description of a folder may include the following
 information:</p><blockquote>
 <p>
 <strong>40.20.5.10</strong>. A URL-encoded name for building the
@@ -160,7 +164,7 @@
 <p><a name="folder" id="folder">
 <strong>40.30.5 Content Symbolic
 Link</strong>.</a></p><p><a name="folder" id="folder">A <em>symbolic link</em> is
-analogous to a symlink, alias or shortcut in a file system. The
+analogous to a symlink, alias or shortcut in a filesystem. The
 description of a symbolic link must include the following
 information:</a></p><p><a name="folder" id="folder">
 <strong>40.30.5.10</strong>. A
@@ -315,7 +319,7 @@
 </blockquote>
 <p><strong>100.50 Content Folders</strong></p>
 <p>The repository should allow for hierarchical arrangement of
-content items in a manner similar to a file system. The API to meet
+content items in a manner similar to a filesystem. The API to meet
 this general requirement focuses primarily on <a href="#folder">content folders</a>:</p>
 <blockquote>
 <p>
@@ -398,5 +402,5 @@
 <a href="mailto:karlg\@arsdigita.com">karlg\@arsdigita.com</a>
 <br>
 
-Last Modified: $&zwnj;Id: requirements.html,v 1.3 2017/08/07 23:47:47
+Last Modified: $&zwnj;Id: requirements.html,v 1.3.2.1 2021/04/05 19:49:48
 gustafn Exp $