Jon Phipps's Library tagged metadata →  View Popular

It is increasingly common for Web-based protocols to require the
discovery of policy or metadata before making a request. For
example, the Robots Exclusion Protocol specifies a way for automated
processes to obtain permission to access resources; likewise, the
Platform for Privacy Preferences [W3C.REC-P3P-20020416] tells user-
agents how to discover privacy policy beforehand.

While there are several ways to access per-resource metadata (e.g.,
HTTP headers, WebDAV's PROPFIND [RFC4918]), the overhead associated
with them often precludes their use in these scenarios.

When this happens, it is common to designate a "well-known location"
for such metadata, so that it can be easily located. However, this
approach has the drawback of risking collisions, both with other such
designated "well-known locations" and with pre-existing resources.

To address this, this memo proposes a single (and hopefully last)
"well-known location", /host-meta, which acts as a directory to the
interesting metadata about a particular authority. Future mechanisms
that require authority-wide metadata can easily include an entry in
the host-meta resource, thereby making their metadata cheaply
available (indeed, because it can be cached, the more mechanisms that
use it, the more efficient it becomes) without impinging on others'
URI space.

Note that the metadata provided by a host-meta resource is explicitly
scoped to apply to the entire authority (in the URI [RFC3986] sense)
associated with it (using the process described in Section 4); it
does not apply to a subset, nor does it apply to other authorities
(e.g., using another port, or a different hostname in the same
domain). However, individual mechanisms (e.g., a relation type in
the Link field) MAY reduce or expand this scope. This should only be
done after careful consideration of the consequences upon security,
administration, interoperability and network load.

Structural Metadata and the Social Limitation of Interoperability: A Sociotechnical View of XML and Digital Library Standards
Development

HIVE is an automatic metadata generation approach that dynamically integrates discipline specific controlled vocabularies encoded with the Simple Knowledge Organisation Systems (SKOS), a World Wide Web Consortium (W3C) standard. HIVE will assist content creators and information professionals with subject cataloging and will provide a solution to the traditional controlled vocabulary problems of cost, interoperability, and usability.

OpenCollection is a full-featured collections management and online access application for museums, archives and digital collections.

APML allows users to share their own personal Attention Profile in
much the same way that OPML allows the exchange of reading lists
between News Readers. The idea is to compress all forms of Attention
Data into a portable file format containing a description of ranked
user interests.

Survey of Metadata Registries

The choice to use folksonomy for organizing information on the Internet is not a simple, straightforward decision, but one with important underlying philosophical issues. Although folksonomy advocates are beginning to correct some linguistic and cultural variations when applying tags, inconsistencies within the folksonomic classification scheme will always persist. There are no right or wrong classification terms in a folksonomic world, and the system can break down when applied to databases of journal articles or dissertations. Folksonomists are confusing cataloging structure with personal opinions and subsequent social bookmarking. These are not the same thing, and they need to be separated.

the entities within the IESR are collections, services and agents. Each of these has associated administrative metadata. The metadata is defined by the IESR Application Profile, along with its associated controlled lists.