Registry Viewpoints

From Metadata-Registry
Jump to: navigation, search
Logo lg.gif
DCMI Registry Community
Dublin Core Metadata Initiative
The DCMI Copyright Statement applies to these pages.

Back to Registry Community main page

Definitions and viewpoints

Purpose of this page

Every registry development is situated in a unique set of circumstances and thinking. This page is to be used to collect a few perspectives. These might include anything from statement of fact or position to formal use cases (see the Use Cases section on this page).


Anything from attributed quotes to structured description is fine on this page.

Definitions and viewpoints

"Vocabularies are sets of terms used to tag documents. Their use increases both precision and recall of searching. At the simplest level, all Flickr terms form a vocabulary. Richer vocabularies have semantics and structure. Thesauri, taxonomies, ontologies, authority lists and control lists are all more or less the same thing as vocabularies (purists will hate me for saying that). -- Mike Taylor on the Becta VMS

"Creating vocabularies is a pain. Tools are expensive." -- Mike Taylor on the Becta VMS

  • "namespace schemas declare (name and define) data elements;
  • application profiles describe the use of (previously declared) data elements to meet the requirements of a particular context or application.

A metadata application profile may

  • select elements from multiple namespaces (but must not use elements that are not previously declared in a namespace schema);
  • refine the definitions of elements by making them narrower or more specific;
  • specify constraints on the permitted values of elements by mandating the use of particular controlled vocabularies or formats" Pete Johnston

"What is an application profile? Application profiles consist of data elements drawn from one or more namespace schemas combined together by implementors and optimised for a particular local application."

Stakeholders/User groups

"The registry is intended to serve as a discovery mechanism and resolution service, with the goal of promoting the reuse of existing terminologies represented in multiple languages. ... Each of the communities these registries serve is comprised of:

  • Read-only users. These include both the humans and applications that are the primary consumers of the registry content. Additionally, the read-only users provide feedback to the registration authority regarding change requests to the registry content.
  • A registration authority, responsible for approving registry content. For example, the DCMI Usage Board is the registration authority for the registry available at the Dublin Core Web site. The Usage Board evaluates proposed new terms that are suggested by the larger Dublin Core community. Approved terms are then passed to the registry steward for inclusion in the metadata registry.
  • Stewards are responsible for application support and maintenance. Their role is limited to the development, support and ongoing maintenance of the registry software. They rely on the registration authority for decisions regarding the actual registry content." -- Wagner & Weibel, The Dublin Core Metadata Registry: Requirements, Implementation, and Experience. Journal of Digital Information, Volume 6 Issue 2, 2005

Sandbox for for (as yet uncategorised/dissected) resources [...] A Registry has the connotation of more than just a shared dumping ground. Registries have the additional capability to create workflow processes to check that new metadata is not a duplicate (for a given namespace). A Repository is similar to a front-porch of a house. No locks prevent new things from landing there. But a Registry is a protected back room where human-centric workflow processes are used ensure that metadata items are non-duplicates, precise, consistent, concise, distinct, approved and unencumbered with business rules that prevent reuse across an enterprise.[...] Registries have the implicit connotation of trust behind them. They now serve a a central process for the creation of shared meaning across the enterprise. Definitions in a registry have been vetted by an enterprise-level organization that has the responsibility of enterprise data stewardship. They have a high probability of being consistent with industry best-practices and vertical industry standards. Registries are the go-to source for creating canonical XML schemas, enterprise ontologies or conformed dimensions in a OLAP cube. Repositories are personal or small departmental definitions of an isolated view of the world."

Principles of Metadata Registries: A White Paper of the DELOS Working Group on Registries

METADATA STANDARDS AND METADATA REGISTRIES: AN OVERVIEW Bruce E. Bargmeyer, Environmental Protection Agency, and Daniel W. Gillman, Bureau of Labor Statistics Daniel W. Gillman, Bureau of Labor Statistics, Washington, DC 20212

Christophe Blanchi, Jason Petrone. Distributed Interoperable Metadata Registry. D-Lib Magazine December 2001, Volume 7 Number 12, ISSN 1082-9873

Heery, Rachael. "Naming Names: Metadata Registries." Ariadne, no. 11 (1997).

Rachel Heery, Harry Wagner. A Metadata Registry for the Semantic Web. D-Lib Magazine, May 2002, Volume 8 Number 5. ISSN 1082-9873

Nagamori, Mitsuharu, and Shigeo Sugimoto. "Metadata Schema Registry as a Tool to Enhance Metadata Interoperability." TCDL Bulletin 3, no. 1 (2006).

Survey of Metadata Registries. DART Project, Suzanne Little.

Rachel Heery. Review of other registries.

Data Semantics: ISO/IEC 11179 (Metadata Registries)

Terminology: ISO 704 (Principles of Terminology)

ISO 1087-1 (Vocabulary for terminology work)

ISO/TC 37/SC 4 (Language Resources Management)

Interoperability: ISO/IEC 19763 (Framework for Metamodel Interoperability)

ISO/IEC 20944 (Interoperability and bindings)

Registries in use

Whittenburg, LuAnn; Saba, Virginia K. Using Metadata Registries with Nursing Terminology. Medinfo 2007: Proceedings of the 12th World Congress on Health (Medical) Informatics; Building Sustainable Health Systems. Abstract: Health data and information sharing using a metadata registry promotes cross-system and cross-organization descriptions of common units of health data and allows nurses, health administrators, and hospital systems to make significant strides towards sustaining health system information systems. Metadata registries contribute to patient safety, efficient and successful electronic health record system implementation, and lower of healthcare costs in electronic health record system implementations by avoiding multiple data translations and mapping, data duplication and messaging errors.

Knowledge Representation, Concepts, and Terminology: Toward a Metadata Registry for the Bureau of Labor Statistics. Final Report to the Bureau of Labor Statistics. Stephanie W. Haas. 1999.