Index: openacs-4/packages/acs-content-repository/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/requirements.html,v diff -u -r1.3 -r1.4 --- openacs-4/packages/acs-content-repository/www/doc/requirements.html 7 Aug 2017 23:47:47 -0000 1.3 +++ openacs-4/packages/acs-content-repository/www/doc/requirements.html 3 Sep 2024 15:37:31 -0000 1.4 @@ -166,8 +166,7 @@

40.10. The data model must support the hierarchical -organization of content items in a manner similar to a file -system.

+organization of content items in a manner similar to a filesystem.

40.20. The URL of a content item should reflect its location in the hierarchy. For example, a press release with the URL @@ -176,8 +175,7 @@

40.20.5 Content Folder.

-

A folder is analogous to a folder or directory in a file -system. It represents a level in the content item hierarchy. In the +

A folder is analogous to a folder or directory in a filesystem. It represents a level in the content item hierarchy. In the previous example, press-releases is a folder under the repository root, and products is folder within that. The description of a folder may include the following information:

@@ -204,7 +202,7 @@

40.30.5 Content Symbolic Link.

A symbolic link is analogous to a symlink, alias or -shortcut in a file system. The description of a symbolic link must include +shortcut in a filesystem. The description of a symbolic link must include the following information:

40.30.5.10. A URL-encoded name for the symbolic link. As @@ -394,7 +392,7 @@

100.50 Content Folders

The repository should allow for hierarchical arrangement of content -items in a manner similar to a file system. The API to meet this +items in a manner similar to a filesystem. The API to meet this general requirement focuses primarily on content folders: