[scheme-catalog updates atsmyles@earthlink.net**20100813210636] hunk ./docs/scheme-catalog.html 64 + <feature identifier> identifier hunk ./docs/scheme-catalog.html 66 - <url> --> See RFC 3986 + <url> --> See RFC 3986 hunk ./docs/scheme-catalog.html 72 - <name> --> Symbol + <name> --> symbol hunk ./docs/scheme-catalog.html 74 - <value> --> Datum + <value> --> datum hunk ./docs/scheme-catalog.html 76 -

Let's start with this example

- -
-	(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"))))
-
- -All scheme catalogs start with the following form: + +
+

Symantics

+

All scheme catalogs start with the following form:

hunk ./docs/scheme-catalog.html 83 -

+
+

Libraries

+

hunk ./docs/scheme-catalog.html 87 - +

hunk ./docs/scheme-catalog.html 95 -
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.
+
A list of arbitrary metadata in the form of an a-list. The name of each key-value pair must be a symbol and the value may be any datum. This specification and all future specifications for this format will not define the meanings of any metadata.
hunk ./docs/scheme-catalog.html 98 -
-The versions of the library are in the following form: -(versions ( requirements uri (@ (name value) ...)) ...) +
+

Versions

+

The versions of the library are in the following form:

+ +(versions (<version-number> <requires> url (@ (name value) ...)) ...) hunk ./docs/scheme-catalog.html 106 -
features
-
the set of requirements which must be met for this library to be valid see spec
-
uri
-
A valid uri.
+
requires
+
the set of requirements which must be met for this library to be valid see spec
+
url
+
A valid url. This url must point to a valid resource where the library is stored. see spec
hunk ./docs/scheme-catalog.html 111 -
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.
+
A list of arbitrary metadata in the form of an a-list. The name of each key-value pair must be a symbik and the value may be any type. This specification and all future specifications for this format will not define the meanings of any metadata.
hunk ./docs/scheme-catalog.html 115 +

Requires

+A requirements clause for a particular version follows the form: + (requires <requirement-clause>+) +

Requirment clauses are an additional discriminator for deciding which version to use. Besides the standard R6RS descriminators of library name and version number, these additional requirements can be used for determining which source code file to use for the same version based on what features are available to the implementation. +

hunk ./docs/scheme-catalog.html 122 - +
+
+

URLs

+