Metadata guidelines for the UK RDTF

Table of Contents
Resource Discovery Taskforce
There are 198 comments in this document

Introduction (24)
Guiding principles (11)
RDTF metadata guidelines (21)
The community formats approach (66)
The RDF data approach (28)
The Linked Data approach (19)
Designing ‘http’ URIs (5)
Data model guidelines (22)
References (2)

About

NOTE: THE COMMENT PERIOD HAS CLOSED – YOU CAN STILL LEAVE COMMENTS HERE IF YOU LIKE BUT WE MAY NOT BE ABLE TO TAKE ACCOUNT OF THEM IN THE FINAL GUIDELINES DOCUMENT.

This DRAFT document provides a set of guidelines for how metadata associated with library, museum and archival collections should be made available for the purposes of supporting resource discovery in line with the JISC/RLUK Resource Discovery Taskforce (RDTF) Vision.

This draft has been prepared by Andy Powell and Pete Johnston of Eduserv, with funding from the JISC.

It is being made available for comment prior to submission as a final deliverable to the JISC in early March 2011. The comment period runs from Thursday 3rd February until Friday 18th February.

Comments on all aspects of the guidelines are welcome. Comments can be made directly on JISCPress or by emailing the authors at [email protected] Note that we have added a number of ‘questions from the authors’ to the JISCPress system to encourage debate.

The guidelines themselves suggest that RDTF metadata should be made openly available using one (or more) of three approaches, referred to as 1) the community formats approach, 2) the RDF data approach and 3) the Linked Data approach. The guidelines do not consider issues of compliance. In line with the vision, these guidelines primarily concern scenarios in which metadata is aggregated as the basis of resource discovery initiatives, though no assumptions are made about the scope or scale of such activities.

For a printable version of this draft, a single document version is available from Google Docs.

A summary of the whole consultation (showing all comments made during the comment period) is also available.

This document provides a set of guidelines about how metadata associated with library, museum and archival collections should be made available for the purposes of supporting resource discovery in line with the Resource Discovery Taskforce (RTDF) Vision [1]. Such a vision presents a number of significant metadata challenges because it spans the library, museum and archives sectors, each of which has multiple different metadata standards in current use. The RDTF Vision is about making the met […]
24 Comments

These guidelines have been developed such that they: support the RDTF Vision [1]; are compatible with the outcomes of the JISC IE Technical Review meeting in London, Aug 2010 [2]; are in line with Linked Data principles as far as possible [3]; are compatible with the W3C Linked Open Data Star Scheme [4][5]; are in line with Designing URI Sets for the UK Public Sector [6]; take into account the Europeana Data Model [7] and ESE [8]; are informed by mainstream web practice an […]
11 Comments

RDTF metadata should be made openly available using one or more of three approaches, referred to below as the community formats approach, the RDF data approach and the Linked Data approach. All three approaches suggest that all RDTF metadata be made available using non-proprietary formats and under an open licence. For the purposes of these guidelines, a non-proprietary format is considered to be a format for which there is a published specification, usually maintained by a standards organiz […]
21 Comments

Guidance RDTF metadata that is exposed using the community formats approach must be made available under an open licence, using a non-proprietary file format (such as one of those listed in the examples section below). The metadata must be made available using simple HTTP GET requests or the OAI-PMH [11]. Where HTTP is used, one or more sitemaps (conforming to the Sitemap protocol [12]) should also be made available, listing the available files. The sitemaps should be listed in a robots […]
66 Comments

Guidance RDTF metadata that is exposed using the RDF data approach must be made available under an open licence as RDF datasets [26]. The RDF datasets must be made available using simple HTTP GET requests as one or more RDF dumps (e.g. files containing RDF/XML [27], N-Triples [28], N-Quads [29] or RDF/JSON [30]). GZip compression may be used to reduce the file size of the RDF dumps. The location of all RDF dumps must be disclosed in accordance with the Semantic Web Crawling Sitem […]
28 Comments

Guidance RDTF metadata that is exposed using the Linked Data approach must be made available under an open licence as RDF datasets. The RDF datasets must be made available using simple HTTP GET requests as one of more RDF dumps (e.g. files containing RDF/XML, N-Triples, N-Quads or RDF/JSON). GZip compression may be used to reduce the file size of the RDF dumps. The location of all RDF dumps must be disclosed in accordance with the Semantic Web Crawling Sitemap Extension. Metadat […]
19 Comments

For metadata that is exposed using the RDF data or Linked Data approaches, all significant resources associated with the collection of interest must be assigned a unique URI. Where the Linked Data approach is used, such URIs must be ‘http’ URIs. When assigned, all ‘http’ URIs should conform to the Designing URI Sets for the UK Public Sector guidelines.
5 Comments

Metadata that is exposed using the RDF data or Linked Data approaches should be modeled according to FRBR, the CIDOC CRM or the principles that underpin EAD. Where structural “containment” relationships are required, ORE should be used.
22 Comments

RDTF Vision – http://ie-repository.jisc.ac.uk/475/1/JISC%26RLUK_VISION_FINAL.pdf eFoundations: Resource discovery revisited – http://efoundations.typepad.com/efoundations/2010/08/resource-discovery-revisited.html Linked Data principles – http://linkeddata.org/ Linked Data Design Issues – http://www.w3.org/DesignIssues/LinkedData.html Linked Open Data Star Scheme by example – http://lab.linkeddata.deri.ie/2010/star-scheme-by-example/ Designing URI Sets for the UK Public Sector – […]