Search   |   Back Issues   |   Author Index   |   Title Index   |   Contents



D-Lib Magazine
July/August 2003

Volume 9 Number 7/8

ISSN 1082-9873

Using the OAI-PMH ... Differently


Herbert Van de Sompel
Digital Library Research and Prototyping
Los Alamos National Laboratory

Jeffrey A. Young
OCLC Office of Research

Thomas B. Hickey
OCLC Office of Research

Red Line



The Open Archives Initiative's Protocol for Metadata Harvesting (OAI-PMH) was created to facilitate discovery of distributed resources. The OAI-PMH achieves this by providing a simple, yet powerful framework for metadata harvesting. Harvesters can incrementally gather records contained in OAI-PMH repositories and use them to create services covering the content of several repositories. The OAI-PMH has been widely accepted, and until recently, it has mainly been applied to make Dublin Core metadata about scholarly objects contained in distributed repositories searchable through a single user interface. This article describes innovative applications of the OAI-PMH that we have introduced in recent projects. In these projects, OAI-PMH concepts such as resource and metadata format have been interpreted in novel ways. The result of doing so illustrates the usefulness of the OAI-PMH beyond the typical resource discovery using Dublin Core metadata. Also, through the inclusion of XSL1 stylesheets in protocol responses, OAI-PMH repositories have been directly overlaid with an interface that allows users to navigate the contained metadata by means of a Web browser. In addition, through the introduction of PURL2 partial redirects, complex OAI-PMH protocol requests have been turned into simple URIs that can more easily be published and used in downstream applications.


It comes as no surprise that most current implementations of OAI-PMH [1] repositories mainly make descriptive metadata about resources harvestable. This emphasis on descriptive metadata has its origin in the early motivations of the OAI3 (Open Archives Initiative) effort that focused on making distributed resources discoverable. The OAI-PMH facilitates this by providing a simple, yet powerful framework for metadata harvesting that allows harvesters to gather metadata held by different repositories into a central location and to make it searchable there. Initially, the descriptive metadata provided by OAI-PMH repositories was to a large extent limited to the mandatory unqualified Dublin Core, but an evolution towards the provision of more extensive descriptive metadata, such as MARC21, is becoming apparent. Providing extensive descriptive metadata is possible in the OAI-PMH thanks to the notion of parallel metadata formats that enables repositories to expose metadata about the same resource in multiple metadata formats.

Creative interpretation of what actually constitutes a resource about which an OAI-PMH repository holds metadata, and of the nature of metadata formats used in the OAI-PMH, has led to suggestions that the protocol could be quite useful beyond the traditional domain of resource discovery using Dublin Core metadata and could reach into the realm of state maintenance in distributed systems [2 , 3 , 4 ]. As a matter of fact, metadata records in the OAI-PMH are any data that can be validated against a W3C4 XML5 Schema6. Therefore, the OAI-PMH can be a medium for incremental, date-sensitive exchange of any form of semi-structured data. In the Section below entitled "Unconventional OAI-PMH resources and metadata formats", three creative uses of the OAI-PMH notions of resource and metadata format are described in the context of the application in which they are used.

The metadata contained in OAI-PMH repositories is typically gathered by harvesters that process it and make it searchable through a user interface. In these uses of the OAI-PMH, repositories are never directly accessed by end-users; the "customers" of the repositories are robots. The Section entitled "A user interface for OAI-PMH repositories", describes an approach to overlay OAI-PMH repositories with an interface allowing users to directly navigate the repository content. We also show how this approach has been used to make the GSAFD Thesaurus, the OpenURL Registry and the XTCat Thesis Catalog user-accessible. The Section entitled "PURLs for simple access to OAI-PMH records" describes an approach to use PURL (Persistant URL7) partial redirects to create simple URIs that lead to records in OAI-PMH repositories. These URIs are easier to publish and use in downstream applications than their corresponding OAI-PMH protocol requests.

Unconventional OAI-PMH resources and metadata formats

In this Section, three examples are given of less conventional OAI-PMH repositories that make creative use of the OAI-PMH notions of resource and metadata format. The repositories are described in the following order: the GSAFD8 Thesaurus, the Digital Library Usage Logs, and the OpenURL9 Registry.

The GSAFD Thesaurus

Libraries put a great deal of effort into creating, maintaining, and using thesauri to improve the recall and precision of database searches. In the GSAFD Thesaurus project, the OCLC Office of Research attempts to determine the value of cross-thesaurus linking and improved thesaurus-access. The desired enhanced thesaurus services are intended for both machine and human use. As the basis of this effort, the GSAFD Thesaurus is stored as an OAI-PMH repository.

The GSAFD Thesaurus records, which are available in MARC 2110 format, were downloaded from the American Library Association site [5]. The records were enriched with 7XX fields where a GSAFD term mapped to a term in the Library of Congress Subject Heading (LCSH) file. The exact nature of this mapping process as well as an evaluation of its added-value is beyond the scope of this article. The records were then converted to the MARC XML format [6] and subsequently stored in an OAI-PMH repository. The resources about which the OAI-PMH repository exposes metadata are the concepts represented by thesaurus terms. In the repository, an OAI-PMH item exists per thesaurus term, and its OAI-PMH identifier is the actual thesaurus term. Three OAI-PMH metadata formats are available per OAI-PMH item:

  • oai_dc: Used to dynamically disseminate unqualified Dublin Core metadata describing the enriched thesaurus record.
  • marc21: Used to contain the enriched MARC 21 thesaurus records in the MARC XML format.
  • z39_19: Used to dynamically disseminate a user-friendly Z39.19 format [7] representation of the enriched thesaurus records.

This approach allows the GSAFD Thesaurus to be simultaneously accessed in three modes, all based on the OAI-PMH protocol:

  • Interaction by users via a Web browser. At the time of writing, this mode of interaction can be experienced at OAI-PMH baseURL Table 1 shows a Z39.19 record in its XML form. Details on how direct user-interaction with an OAI-PMH repository can be implemented are provided in the Section entitled "A User interface for OAI-PMH Repositories".
  • Interaction by machines through OAI-PMH-based Web Services mechanisms.
  • Interaction by OAI-PMH harvesters aiming at recurrently gathering thesaurus records, and updates thereof, for use elsewhere.
  <Term>Adventure fiction</Term>
  <SN>Use for works characterized by an emphasis on physical and often
      violent action, exotic locales, and danger, generally
      with little character development.</SN>
  <UF>Adventure stories</UF>
  <UF>Swashbucklers </UF>
  <NT>Picaresque literature</NT>
  <RT>Sea stories</RT>
  <NT>Western stories</NT>
  <MT scheme="lcshac" controlNumber="(DLC)sj 96004703 ">Adventure and
  <MT scheme="lcsh" controlNumber="(DLC)sh 85001072 ">Adventure stories</MT>

Table 1: A Z39.19 thesaurus record from the GSAFD Repository. This record shows the relationships between terms using standard Z39.19 labels. The "MT" label is an extension to the Z39.19 standard to indicate terms that are mapped to a different thesaurus. The scheme attribute indicates that the first maps to a term in the LCSH (juvenile) thesaurus and the second maps to a term in the standard LCSH thesaurus. The controlNumber attribute indicates the unique ID within the external thesaurus.

As a result, by storing the GSAFD Thesaurus as an OAI-PMH repository, its content becomes an integral part of the Web infrastructure where it can be seamlessly used by both human and machine using standard Web tools.

Digital Library Usage Logs

In a recent collaboration between Old Dominion University and the Los Alamos National Laboratory (LANL) aimed at the deployment of recommender systems, logs that describe the usage of the LANL Digital Library are exposed through the OAI-PMH. The Digital Library Usage Log repositories currently cannot be publicly harvested. Because of the specific aim of the project, only actions by which users express a preference for a specific document are selected and ingested into a relational database. In the current set-up, preference is measured implicitly [8], and a log-entry is typically created when a user clicks an OpenURL [9] provided for a document available via the LANL Digital Library services. The content of the database populated by events that express user preferences is exposed as two interlinked OAI-PMH repositories:

  • The User Repository: The resources about which this repository exposes metadata are the users of the LANL Digital Library. In this repository, an OAI-PMH identifier exists per user accessing the Digital Library. In principle, two parallel metadata formats are available for each OAI-PMH identifier: a Dublin Core record describing the user and a User-log record that lists all relevant actions by the user. An individual entry in a User-log record will, amongst other things, list the unique identifier of the document about which the user expressed a preference, as well as the datetime on which this happened. For reasons of privacy, the OAI-PMH identifiers used in this repository do not reveal the real identity of the user, and the Dublin Core record describing the user is actually not exposed. This raises questions of compliance of the User Repository with the OAI-PMH that mandates support of Unqualified Dublin Core. It also illustrates why the OAI Technical Committee failed to reach a consensus quickly on the question of whether or not to keep Dublin Core mandatory in version 2.0 of the protocol.
  • The Document Repository: The resources about which this repository exposes metadata are the documents for which users have expressed a preference. In this repository, an OAI-PMH identifier exists per document for which a preference has been expressed. Two parallel metadata formats are available for each OAI-PMH identifier: a Dublin Core record describing the document itself and a Document-log record that lists all expressions of preference for the actual document by users. An individual entry in a Document-log record will, amongst others, list the unique identifier of the user that expressed a preference for the document, as well as the datetime on which this occurred. Table 2 shows a brief Document-log record from this repository. To support a better readability, XML Namespace information is omitted, and information is not encoded.
<day date="2002-02-22">
<agent time="2002-02-22T17:28:51Z"
<day date="2002-02-23">
<agent time="2002-02-23T19:14:08Z"

Table 2: A Document-log record from the Document Repository. This record shows that two users have expressed a preference for the document with unique identifier ori:doi:10.1006/geno.1999.5925. The user with unique identifier has done so on 2002-02-22, while the user with unique identifier has done so on 2002-02-23. The XLinks, which are OAI-PMH requests against the User Repository, lead to the User-log record for the respective user.

The User Repository and the Document Repository are interlinked by means of XLinks11 in the following manner:

  • In the User Repository, an XLink leads from each individual entry in a User-log record — recording that the user has expressed preference for document x — to the Document-log record in the Document Repository that describes expressions of preference for document x by the whole user community.
  • In the Document Repository, an XLink leads from each individual entry in a Document-log record — recording that the document was preferred by user y — to the User-log record in the User Repository that describes all expressions of preference by user y. These XLinks can be seen in Table 1.

It is expected that the usage of the OAI-PMH in the context of this project will provide a scalable and sustainable infrastructure to share continuously updated usage information with a fully autonomous downstream application. That application will mine harvested usage logs and provide recommendations based on patterns derived from the mining activity. Recommendations will be accessible by querying the application using an XML ContextObject as specified the Draft NISO OpenURL Standard.

The OpenURL Registry

The upcoming NISO OpenURL Standard is a so-called "framework standard". Its nature is inspired by the Bison-Futé model [10] and extends the usability of OpenURL's context-sensitive services concept [10, 11, 12, 13] beyond the scholarly domain in which OpenURL originated. It does so by specifying a framework that enables communities to define and implement their own OpenURL-based service environment. The approach builds on a Registry that is introduced to contain the explicit definitions for core components of the OpenURL Framework as registered by communities. Such core components include, amongst others, Namespaces of Identifiers that can be used to identify resources, Metadata Formats that can be used to describe resources, ContextObject Formats that can be used to express the payload of an OpenURL using a well-defined syntax, and Community Profiles that list the actual choices a Community makes from Registry entries when it actually deploys its own OpenURL environment.

To bootstrap deployment of the new specification in the original OpenURL community, many initial Registry entries provided by the NISO AX Committee12 are relevant for the purpose of open linking in the scholarly information environment. For example:

  • The registered Namespaces of Identifiers include the DOI13 Namespace, the Namespace of PubMed identifiers, and the Namespace of OCLC WorldCat numbers.
  • Several registered Metadata Formats have tags that closely resemble those used in OpenURL 0.1 [9], but MARCXML [6] and Unqualified Dublin Core [14] have also been registered. These Metadata Formats are either defined by means of an XHTML14 document derived from a well-defined Template [15], or by means of a W3C XML Schema.

Two ContextObject Formats that can be used by several Communities to express the payload of an OpenURL have been defined. The first is a Key/Encoded-Value Format [16] that — like OpenURL 0.1 — expresses the OpenURL payload as a list of ampersand-delimited key/value pairs. Its definition is based on the aforementioned XHTML Template. The second is the XML Format [17] in which the OpenURL payload is expressed as an XML instance document, the format of which is defined by means of a W3C XML Schema.

Early in the NISO AX Standardization effort, it had been suggested that making the OpenURL Registry OAI-PMH conformant could lead to an environment in which OpenURL Resolvers could easily remain synchronized with the definitions contained in the Registry by regularly polling for updates and harvesting them whenever required [3]. Although the nature of the content of the Registry has significantly evolved since then, the idea of creating an OAI-PMH compliant Registry has been used for the Registry for Trial Use of the Draft NISO OpenURL Standard. The nature of the OAI-PMH Repository that holds the Registry entries is described below. In order to avoid confusion between OAI-PMH and OpenURL terminology the following convention is used in this description: an OAI-PMH term is followed by [OAI], and an OpenURL term is followed by [OURL].

The resources [OAI] about which the repository [OAI] contains metadata [OAI] are the concrete entries for core components of the OpenURL Framework that are registered by Communities in order to be able to deploy their OpenURL environment. For example, a resource [OAI] can be the DOI Namespace [OURL], an XML Metadata Format [OURL] to describe book-like objects, or the Key/Encoded-Value ContextObject Format [OURL] used to express the payload of an OpenURL. Each such registered item receives an Identifier [OURL] at registration, and this becomes an identifier [OAI] for the item in the OAI-PMH repository. Currently, the OAI-PMH repository supports three metadata formats [OAI] with the following metadataPrefixes [OAI] and characteristics:

  • oai_dc: Dublin Core is used to describe registered items. A Dublin Core record exists per registered item.
  • mtx: This metadata format [OAI] is defined by the W3C XML Schema that defines XHTML. The metadata format [OAI] is actually further restricted by the XHTML Template that is used for defining Key/Encoded-Value Metadata Formats [OURL] for the OpenURL Framework. An MTX record [OAI] exists for all registered Key/Encoded-Value Metadata Formats [OURL], and the record [OAI] content is the actual XHTML-based definition of the Metadata Format [OURL].
  • xsd: This metadata format [OAI] is defined by the W3C XML Schema that defines W3C XML Schema. An xsd record [OAI] exists for all registered XML Metadata Formats [OURL], and the record [OAI] content is the actual W3C XML Schema that defines the Metadata Format [OURL].

If required for the purpose of registration, the repository can support additional metadata formats [OAI], as long as they can be defined by means of W3C XML Schema. For example, it is anticipated that Community Profiles listing Registry choices will be registered and will be unambiguously expressed as well-formed XML instance documents that validate against a special-purpose W3C XML Schema. If this happens, the repository can support a fourth metadata format [OAI] to accommodate such Community Profile documents.

In addition to the described interpretations of the OAI-PMH notions of resource and metadata formats, the repository also builds on the OAI-PMH notion of sets. In the OAI-PMH, repositories can optionally implement sets, which group contained items into hierarchical subdivisions of the repository. The repository used for the OpenURL Registry implements a set structure in which every set refers to a core component of the OpenURL Framework. As such, there are, for example, sets to contain registered Namespaces of Identifiers, a set to contain registered Character Encodings, etc.

The described approach to the deployment of the OpenURL Registry does effectively facilitate a straightforward synchronization of information that is essential to the functioning of the OpenURL Framework between the Registry and OpenURL Resolvers. But, as will be shown in the next Section, it also enables the creation of a straightforward interface that allow users to navigate the Registry content in a meaningful manner, by the sole use of OAI-PMH requests.

The OpenURL Registry repository can be harvested at OAI-PMH baseURL

A user interface for OAI-PMH repositories

The OAI-PMH was designed to facilitate incremental harvesting of metadata contained in a repository by robots; so far, its uses have largely been restricted to that application area. However, it is also possible to explore the content of repositories from a user interface that only uses OAI-PMH requests as its navigation mechanism. As will be shown, this approach can be highly attractive for certain repositories.

In order to implement direct and meaningful access from a Web browser to the content of an OAI-PMH repository, a reference to an XSLT stylesheet is introduced in OAI-PMH protocol requests. Doing so, a protocol response looks as shown in Table 3.

<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet  type="text/xsl" href="gui.xsl" ?>
<OAI-PMH xmlns="" 	      

Table 3: An OAI-PMH protocol response with embedded reference to an XSLT stylesheet.

When such a response is sent to an automated process such as an OAI-PMH harvester, the stylesheet reference will be ignored and the XML will be processed directly. However, a Web browser receiving the response will use the stylesheet reference to render the response into HTML in the manner specified by the stylesheet. As such, it is possible to create a browser-based user interface to interact directly with an OAI-PMH repository by merely clicking OAI-PMH requests provided in the interface, and by receiving OAI-PMH responses rendered by means of a specified stylesheet. Similarly (perhaps even more generally useful), an OAI service provider can directly issue a GetRecord request to a record's home repository on behalf of the user so that the home repository has control of the transformation/display/branding of the records that users see.

The capabilities of the user interface using this method are rather limited because of the limitations of using only OAI-PMH verbs. However, for simple applications or for the navigation of small repositories, the approach can be quite useful as is illustrated in the following examples.

Figure 1 shows the result of issuing the OAI-PMH GetRecord request to obtain a Dublin Core record from the XTCAT Experimental Thesis Catalog. The response, which includes a stylesheet reference, is rendered by the browser. No further external mediation is required for displaying the metadata contained in the response to users. In addition, several navigational links are provided in the interface that are OAI-PMH requests.

Image showing an OAI-PMN response to a GetRecord request

Figure 1: An OAI-PMH response to the GetRecord request

Figure 2 shows how the OAI-PMH ListIdentifiers verb is used to render terms from the small GSAFD Thesaurus in a user interface. In the GSAFD Thesaurus, terms are treated as OAI-PMH identifiers. As can be seen, the interface allows for further exploration of each thesaurus term. This is achieved by hyperlinking each term with an OAI-PMH GetRecord request for the Z39.19 [7] metadata that describes the term. This approach would not lead to an interesting user interface if the OAI-PMH identifiers were not meaningful in themselves — for example, they could be numbers sequentially assigned to thesaurus terms instead of the terms themselves. In such cases, a ListRecords request could be substituted for ListIdentifiers and the meaningful thesaurus terms could be extracted from the appropriate metadata tag.

image showing an OAI-PMH response

Figure 2: An OAI-PMH response to the ListIdentifiers request

Figure 3 shows how the OAI-PMH ListSets request is used in the OpenURL Registry to display a list of the core components of the OpenURL Framework. Again, the interface allows for further exploration of the Registry by means of OAI-PMH requests. For example, the hyperlink provided with each set name is an OAI-PMH ListRecords request for all items in the set that have Dublin Core metadata. Because all entries in the OpenURL Registry have Dublin Core metadata, the result will be a list describing each item of the specified set, i.e., of the specified core component of the OpenURL Framework.

Image showing response to an OAI-PMH request

Figure 3: An OAI-PMH response to the ListIdentifiers request

Finally, Figure 4 shows the usage of the OAI-PMH ListMetadataFormats request to allow users of the OpenURL Registry to navigate to either of the two currently existing types of definitions for OpenURL ContextObject Formats or Metadata Formats — namely, the Key/Encoded-Value Formats defined by means of the XHTML Template, or the XML Format defined by means of XML Schema. For each definition type, a metadata format [OAI] is available in the repository. The hyperlink provided with each of the listed types is an OAI-PMH ListRecord request for Dublin Core metadata of all Format definitions of the specified type, i.e., with the metadata format [OAI].

Image showing an OAI-PMH response

Figure 4: An OAI-PMH response to the ListIdentifiers request

PURLs for simple access to OAI-PMH records

OAI-PMH identifiers uniquely identify items in OAI-PMH repositories. They are resolved through the use of the identifier itself, along with an identifier of a metadata format available for that item. The resolution occurs through the submission of rather lengthy OAI-PMH GetRecord requests (e.g.,
). In the above, it has been shown that the OAI-PMH can be useful for direct human interaction with repositories. Hence it seems sensible to construct "cool URLs" [18] to resolve OAI-PMH identifiers, because they are easier for humans to use.

PURLs [19] are a method for creating and maintaining URLs for digital collections. PURLs do this by offering a level of indirection to URLs that enables a collection owner to change the URL for objects in the collection while maintaining a Persistent URL for publication and access. The PURL system also includes the ability to do "partial redirects" in which only part of the PURL is used for the indirection to an actual URL. This turns out to be an effective technique for creating a name gateway to turn complex OAI-PMH GetRecord requests into cool URLs15.

The proposed scheme [20] for creating OAI-PMH GetRecord PURLs is:

  "" repository-identifier "/" metadataPrefix "/" local-identifier

For OAI-PMH repositories where the identifiers conform to the oai-identifier schema [21], the repository-identifier in the PURL should match the repository-identifier embedded in the oai-identifier.

For example, the XTCat [22] Repository has oai-identifiers of the form The repository-identifier is therefore and the local-identifier for this particular item is OCLCNo/ocm00006585. Following the proposed PURL scheme, the corresponding cool URL is, which resolves to the oai_dc GetRecord response shown earlier.

Such resolution is achieved by creating a PURL partial redirect of the form:

  "" repository-identifier "/" metadataPrefix "/"

which will be mapped to the destination:

  baseURL "?verb=GetRecord
           &metadataPrefix=" metadataPrefix
           "&identifier=oai:" repository-identifier ":"


  /oai/ ->
  /oai/ ->

Note, however, that the OpenURL Registry used in the latter example doesn't use identifiers that conform to the oai-identifier scheme, so the entire identifier must be appended to the PURL rather than a parsed local-identifier.

Appending a local-identifier to a PURL partial redirect has the effect of appending it to the PURL partial redirect's destination, thus completing the identifier parameter in the OAI-PMH GetRecord request. The described technique makes publishing of OAI-PMH GetRecord requests in downstream applications easier and makes handling the requests by humans more straightforward.


This article has introduced some novel ways to use the OAI-PMH. It has been shown that, through the creative interpretation of the OAI-PMH notions of resource and metadata format, repositories with rather unconventional content, such as Digital Library usage logs, can be deployed. These applications further strengthen the suggestion that the OAI-PMH can effectively be used as a mechanism to maintain state in distributed systems. It has also been shown that simple user interfaces can be implemented by the mere use of OAI-PMH requests and responses that include stylesheet references. For certain applications, such as the OpenURL Registry, the interfaces that can be created in this manner seem to be quite adequate, and hence the proposed approach is attractive if only because of the simplicity of its implementation. The availability of an increasing amount of records in OAI-PMH repositories generates the need to be able to reference such records in downstream applications, through URIs16 that are simpler to publish and use than the OAI-PMH HTTP GET requests used to harvest them from repositories. This article has shown that PURL partial redirects can be used to that end.


The authors would like to acknowledge the work Patrick Hochstenbach (Los Alamos National Laboratory), and Johan Bollen (Old Dominion University) on the Digital Library Usage Log repository, as well as the work of Phil Norman (OCLC) on the OpenURL Registry.

Many thanks also to Patrick Hochstenbach, Carl Lagoze, and Michael Nelson for their feedback on the draft of this article.


1. XSL - Extensible Stylesheet Language, <>.

2. PURL - Persistent URL, <>.

3. OAI - Open Archives Initiative, <>.

4. W3C - World Wide Web Consortium, <>.

5. XML - Extensible Markup Language, <>.

6. XML schema, <>.

7. URL - Uniform Resource Locator, <>.

8. GSAFD - Guidelines on Subject Access to Individual Works of Fiction, Drama, Etc., <
Committees3/Subject_Analysis/MARC_21_Authority_Records_for_GSAFD_ Genre_Terms.htm

9. OpenURL - NISO AX Committee. 2003. The OpenURL Framework for Context-Sensitive Services, Draft Standard. <>.

10. MARC 21 - MAchine-Readable Cataloging (21 refers to the 21st century), <>.

11. XLink. <>.

12. NISO AX - National Information Standards Organization, <>.

13. DOI - Digital Object Identifier, <>.

14. XHTML - Extensible HyperText Markup Language, <>.

15. Cool URLs, "Cool URIs don't change," <>.

16. URI - Uniform Resource Identifier, <>.


[1] Lagoze, Carl, Herbert Van de Sompel, Michael Nelson, and Simeon Warner. 2002. The Open Archives Initiative Protocol for Metadata Harvesting - Version 2.0. <>

[2] Van de Sompel, Herbert. 2000. Closing Keynote Address for the Task Force Meeting of the Coalition for Networked Information, San Antonio TX, Fall 2000. <>.

[3] Van de Sompel, Herbert and Donna Bergmark. 2002. A distributed registry for OpenURL metadata schemas with an OAI-PMH conformant central repository. IEEE Proceedings of the 2002 International Conference on Parallel Processing Workshops, 18-21 August 2002, Vancouver CA, pp. 469-472.

[4] Nelson, Michael. 2002. Service Providers: Future Perspectives. Presentation at the 2nd Workshop on the Open Archives Initiative. Geneva, Switzerland, October 2002. <>

[5] Association for Library Collections & Technical Services. 2003. ALA | MARC 21 Authority Records for GSAFD Genre Terms. <

[6] MARCXML. <>.

[7] National Information Standards Organization. 1993. Guidelines for the Construction, Format, and Management of Monolingual Thesauri. <>.

[8] Claypool, Mark, Phong Le, Makoto Wased, and David Brown. 2001. Implicit Interest Indicators. Proceedings of the International Conference on Intelligent User Interfaces, January 14-17 2001, Santa Fe, NM, pp. 33-40.

[9] Van de Sompel, Herbert, Patrick Hochstenbach and Oren Beit-Arie. 2000. OpenURL Syntax Description.

[10] Van de Sompel, Herbert and Oren Beit-Arie. 2001. Generalizing the OpenURL Framework beyond References to Scholarly Works: The Bison-Futé Model. D-Lib Magazine. 7(7/8). <doi:10.1045/july2001-vandesompel>.

[11] Van de Sompel, Herbert and Patrick Hochstenbach. 1999. Reference Linking in a Hybrid Library Environment. Part 1: Frameworks for
Linking. D-Lib Magazine. 5(4). <doi:10.1045/april99-van_de_sompel-pt1>.

[12] Van de Sompel, Herbert and Patrick Hochstenbach. 1999. Reference Linking in a Hybrid Library Environment. Part 2: SFX, a Generic Linking
Solution. D-Lib Magazine. 5(4). <doi:10.1045/april99-van_de_sompel-pt2>.

[13] Van de Sompel, Herbert and Patrick Hochstenbach. 1999. Reference Linking in a Hybrid Library Environment. Part 3: Generalizing the SFX
Solution in the "SFX@Ghent & SFX@LANL" experiment. D-Lib Magazine. 5(10).

[14] Johnston, Pete. 2002. Unqualified Dublin Core XML Schema for OAI-PMH. <>.

[15] NISO Committee AX. 2003. The Z39.88-2003 Matrix Constraint Language. <>.

[16] NISO Committee AX. 2003. The Key/Encoded-Value Physical Representation. <>.

[17] NISO Committee AX. 2003. The XML Physical Representation. <>.

[18] Berners-Lee, Tim. 1998. Hypertext Style: Cool URIs don't change. <>

[19] OCLC. 2003. Persistent URL Home Page. <>.

[20] Powell, Andy, Jeffrey A. Young, Thomas B. Hickey. In press.

[21] Lagoze, Carl, Herbert Van de Sompel, Michael Nelson, and Simeon Warner. 2002. Implementation Guidelines for the Open Archives Initiative for Metadata Harvesting: Specification and XML Schema for the OAI Identifier Format. <>.

[22] OCLC. 2003. XTCat - Experimental Thesis Catalog. <>.


Copyright © Herbert Van de Sompel, Jeffrey A. Young, and Thomas B. Hickey

Top | Contents
Search | Author Index | Title Index | Back Issues
Previous Article | Next Article
Home | E-mail the Editor


D-Lib Magazine Access Terms and Conditions

DOI: 10.1045/july2003-young