2.1 This folder
organizes definitions of all URI-based identifiers that are
introduced by nfoWorks.
2.2 Every URI-based identifier, including namespace identifiers,
assigned for nfoWorks has the form <http://nfoworks.org/ns/...>
(with the exact form and capitalizations).
2.3 All nfoWorks-established
URI-based identifiers are resolvable to a location in this
structure. The URI leads to the
definitive description of the identifier. Multiple
identifiers can be described on the same web page. Distinct identifiers
resolving to the same web page will differ in the use of
fragment IDs (suffixes following the first "#"
in the URI).
2.4 Although every
identifier is tied to a unique URI, not every URI resolvable
into this structure is an nfoWorks
(namespace) identifier. For example, <http://nfoWorks.org/ns/#a2.4>
and <http://nfoworks.org/ns#a2.4>
resolve to this section of this page. No identifier
significance is intended beyond providing a reference to a
distinct web location
(a permalink
that serves as a
purple number). The employment of these additional URIs
in RDF or any other resolvable reference is not
an nfoWorks identifier usage.
2.5 Note: To emphasize when the intended interpretation of
a URI
text
is as a namespace identifier, the notation {text}
is used. When it is useful to delimit URI
text
without signifying a namespace, the notation <text>
is used. (The {, }, <, and > characters are not allowed in
URIs. They are useful for unambiguously delimiting the
extent of a URI that is surrounded by such characters.)
2.6 Additional information about namespaces and URI-based
identifiers is provided at [d111001].
