171
edits
(Added a link to the unit test repository.) |
(Removed mention of file system backends) |
||
| Line 17: | Line 17: | ||
# A module identifier is a String of "terms" delimited by forward slashes. | # A module identifier is a String of "terms" delimited by forward slashes. | ||
# A term must be a camelCase identifier, ".", or "..". | # A term must be a camelCase identifier, ".", or "..". | ||
# | # Module identifiers may not have file-name extensions like ".js". | ||
# Module identifiers may be "relative" or "absolute". A module identifier is "relative" if the first term is "." or "..". | # Module identifiers may be "relative" or "absolute". A module identifier is "relative" if the first term is "." or "..". | ||
# Absolute identifiers are resolved off the conceptual name space root | # Absolute identifiers are resolved off the conceptual module name space root. | ||
# Relative identifiers are resolved relative to the | # Relative identifiers are resolved relative to the identifier of the module in which "require" is called. | ||
=== Unspecified === | === Unspecified === | ||
| Line 26: | Line 26: | ||
This specification leaves the following important points of interoperability unspecified: | This specification leaves the following important points of interoperability unspecified: | ||
# Whether | # Whether modules are stored with a database, file system, or factory functions, or are interchangeable with link libraries. | ||
# Whether a PATH is supported by the module loader for resolving module identifiers. | # Whether a PATH is supported by the module loader for resolving module identifiers. | ||
edits