Associating Resources with Namespaces

The editors of the document "Associating Resources with Namespaces"
have released an updated editors' draft. This TAG finding addresses
the question of how ancillary information (schemas, stylesheets,
documentation, etc.) can be associated with a namespace. Section 4
"Namespace URIs and Namespace Documents" (earlier section title was:
"Identifying Individual Terms") has been expanded to include: 4.1
"Namespace URIs and Namespace Documents: The XML language case"; 4.2
"Namespace URIs and Namespace Documents: The Semantic Web case"; 4.3
"GRDDL and Namespace documents." From the Preface: The names in a
namespace form a collection: (1) Sometimes it is a collection of
element names -- DocBook and XHTML, for example; (2) sometimes it
is a collection of attribute names -- XLink, for example; (3)
sometimes it is a collection of functions -- XQuery 1.0 and XPath
2.0 Data Model; (4) sometimes it is a collection of properties --
FOAF; (5) sometimes it is a collection of concepts (WordNet), and
many other uses are likely to arise. Given the wide variety of things
that can be identified, it follows that an equally wide variety of
ancillary resources may be relevant to a namespace. A namespace may
have documentation (specifications, reference material, tutorials,
etc., perhaps in several formats and several languages), schemas
(in any of several forms), stylesheets, software libraries, applications,
or any other kind of related resource. The names in a namespace
likewise may have a range of information associated with them...
[In this document] we define a conceptual model for identifying related
resources that is simple enough to garner community consensus as a
reasonable abstraction for the problem; we show how RDDL 1.0 is one
possible concrete syntax for this model; and we show how other
concrete syntaxes could be defined and identified in a way that
would preserve the model.