Note: This report was originally published in D-Lib Magazine, February 1998, by Stuart Weibel (OCLC Office of Research) and Juha Hakala (Helsinki University Library).
Original publication: https://www.dlib.org/dlib/february98/02weibel.html

DC-5: The Helsinki Metadata Workshop

Stuart Weibel, OCLC Office of Research; Juha Hakala, Helsinki University Library

Introduction

Some 70 attendees came from sixteen countries on four continents to the fifth Dublin Core Metadata Workshop, held in Helsinki, Finland, in October 1997. The workshop was co-sponsored by the National Library of Finland, OCLC, and the Coalition for Networked Information (CNI). Travel support was provided by the National Science Foundation, OCLC, CNI, and attendee home institutions.

The participants represented many stakeholders in various resource description communities, including librarians, digital library researchers, computer networking specialists, content experts, and museum information specialists.

Primary Business

The primary business of DC-5 was to finalize the definitions of the 15 unqualified Dublin Core elements. Several previously contested element definitions were resolved.

Contested Elements

Date

The Date element was defined as "a date associated with the creation or availability of the resource." The workshop acknowledged the inherent ambiguity but agreed on a series of date refinements for qualified applications. The Date Sub-elements Working Group produced a draft proposal available for review.

Coverage

The Coverage element reached consensus for "spatially-referenced resources" with geographic and temporal applications. For unqualified Dublin Core, a simple text string would suffice, while more elaborate schemes were anticipated for qualified Dublin Core.

Relation and the 1:1 Principle

The workshop established the foundational 1:1 principle: each resource should have a discrete metadata description, and each metadata description should include elements relating to a single resource.

This principle addressed a long-standing question about how to handle related resources — versions, translations, parts of a whole, and other relationships. Rather than attempting to describe multiple resources in a single record, the Relation element enables linking separate descriptions coherently.

The Relation Working Group identified a draft set of relation types for common resource relationships.

Working Groups

Three working groups produced draft reports:

Date Sub-elements Working Group. Developed a proposal for refining the Date element with sub-types such as "created," "modified," "valid," and "available."

Relation Working Group. Identified relation types that describe common relationships between resources, building on the 1:1 principle.

Sub-element Working Group. Defined common sub-elements expected in practical applications of the Dublin Core, addressing the need for more specific metadata within the framework of the 15 core elements.

Significance

DC-5 marked the transition from element definition to element deployment. With the 15 unqualified elements finalized, the Dublin Core community could focus on implementation, qualification mechanisms, and domain-specific applications. The 1:1 principle provided the architectural foundation for a coherent metadata ecosystem.

Acknowledgments

Misha Wolf, David Bearman, Simon Cox, and John Kunze were acknowledged for exceptional diligence in their contributions to the workshop's success.

References

• Dublin Core Homepage: http://purl.org/metadata/dublin_core
• DC-5 Workshop: http://linnea.helsinki.fi/meta/DC5.html
• Date Sub-elements Report: http://purl.oclc.org/metadata/reports/date
• Relation Working Group Report: http://purl.oclc.org/metadata/reports/relation
• Sub-element Working Group Report: http://purl.oclc.org/metadata/reports/subelement
• Reference Description of Elements: http://purl.org/metadata/dublin_core/elements
• Projects Using Dublin Core: http://purl.oclc.org/metadata/dublin_core/projects.html