[updated scheme-catalogs doc
atsmyles@earthlink.net**20100702204809] hunk ./docs/scheme-catalog.html 22
-<ul>
-  <li>Dealing with features. Should be like srfi-0?</li>
+<ul>  
hunk ./docs/scheme-catalog.html 28
-<p>R6RS provides a facility to define libraries. However it leaves unspecified where to find the library to load when a top level program references it. SRFI 103 attempts to codify how to find a library file on a filesystem. However, it sufferes from the following limitations:
+<p>R6RS provides a facility to define libraries. However it leaves unspecified where to find the library to load when a top level program references it. SRFI 103 attempts to codify how to find a library file on a filesystem. However, it suffers from the following limitations:
hunk ./docs/scheme-catalog.html 40
+<p>Let's start with this example</p>
+
+<pre>
+	(catalog
+	 (library (rnrs io ports)
+	  (versions
+	   ((6)
+	    (requires gambit-binary)
+	    "file:/Users/asmyles8440/.gambit/lib/rnrs-io-ports-v-6.o1"
+	    (@ (dynlib #t)))
+	   ((6)
+	    "file:///Users/asmyles8440/Documents/projects/r6gambit/libs/rnrs/io.scm#0")))
+	 (library (rnrs io simple)
+	  (versions
+	   ((6)
+	    (requires gambit-binary)
+	    "file:/Users/asmyles8440/.gambit/lib/rnrs-io-simple-v-6.o1"
+	    (@ (dynlib #t)))
+	   ((6)
+	    "file:///Users/asmyles8440/Documents/projects/r6gambit/libs/rnrs/io.scm#1"))))
+</pre>
+
+All scheme catalogs start with the following form:
+
+<code>(catalog library ...)</code>
+
+<div>
+Each library is in the form:
hunk ./docs/scheme-catalog.html 69
-??? detailed specification
+<code>(library <library-name> (versions <version-info>) (@ (name value) ...))</code>
+<dl>
+   <dt>library-name</dt>
+   <dd>A R6RS library name without any version info</dd>
+   <dt>versions</dt>
+   <dd>A list of versions available</dd>
+   <dt>metadata (@)</dt>
+   <dd>A list of arbitrary metadata in the form of an a-list. The name of each key-value pair must be a name and the value may be any type. This specification and all future specifications for this format will not define the meanings of any metadata.</dd>
+</dl>
+</div>
+<div>
+The versions of the library are in the following form:
+<code>(versions (<version-number> requirements uri (@ (name value) ...)) ...)</code>
+<dl>
+   <dt>version-number</dt>
+   <dd>A list of numbers or the empty list ()</dd>
+   <dt>features</dt>
+   <dd>the set of requirments which must be met for this library to be valid see <a href="#requirements-spec">spec</a></dd>
+   <dt>uri</dt>
+   <dd>A valid uri.</dd>
+   <dt>metadata (@)</dt>
+   <dd>A list of arbitrary metadata in the form of an a-list. The name of each key-value pair must be a name and the value may be any type. This specification and all future specifications for this format will not define the meanings of any metadata.</dd>
+</dl>
+</div>
+<div id="requirements">
+</div>