innovation in metadata design, implementation & best practices

DCMI Citations Working Group

Bath Citation Meeting Comments

Dublin Core Metadata Initiative - Citation Working Group

16 May 2001

Editor: Ann Apps < ann.apps@man.ac.uk>

Status of this document:*Working Draft_

This document includes comments, for clarification, on the minutes of the meeting held at The University of Bath, UK, on 15 March 2001 to discuss a proposal for capturing journal article citation information in Dublin Core and a way forward for this proposal. This document also includes a proposed structure for a proposal paper, and the expected process required to progress this proposal to become a DCMI recommendation.

Comments and feedback should be sent to the working group mailing list, < dc-citation@jiscmail.ac.uk>, the archives for which may be browsed at < http://jiscmail.ac.uk/lists/dc-citation.html> (NOTE, you must be a member of the WG to post messages to the WG) or, alternatively, send your feedback to the Editor of this Working Draft.


Citation Meeting, University of Bath, 15 March 2001

A meeting of a small group of interested people was held at The University of Bath, UK (hosted by UKOLN) on 15 March 2001 to discuss a proposal for capturing journal article citation information in Dublin Core and a way forward for this proposal. The minutes of this meeting may be read at http://www.ukoln.ac.uk/metadata/resources/dc/dc-citation-wg/meetings/2001-03-15.html.

Comments on Minutes

Following are some comments on the meeting minutes for clarification, resulting from some email discussion following the meeting. Note that the minutes record the general, and fairly informal, discussion at the meeting. Not all the suggestions made during the meeting are expected to be taken forwarded into a proposal for a DC recommendation. The suggested proposal from the meeting is in the following section.

Briefly the recommendation from the meeting was:

Given this recommendation, we would then suggest 3 possible syntaxes to capture them: DCSV, OpenURL, RDF. With examples.

The difference between this and the previous Citation WG's charter is:

Proposal Structure

This is an outline draft structure for the proposal. To a large extent the document can utilise the structure and content of the meeting minutes report.

DCMI Process

Following the Bath meeting, Rachel Heery sent the following email to Stu Weibel and Makx Dekkers asking for advice on how to submit and progress a proposal from the group.

We hosted a meeting here at UKOLN yesterday of the group looking at progressing DCMI recommendation on handling metadata for journal articles. We had a productive meeting, unfortunately Cliff had to cancel at the last moment but fortunately we had sufficient background and collective memory to proceed! An account of the meeeting will be available next week, in the meantime I have been actioned to contact you now and ask for advice on how to proceed. In the meeeting we agreed the outline of a recommendation on best practice for describing journal articles using data elements based on the DC element set . The recommendation closely follows the previous DC Citation WG proposal with some small variance. We would also like to include in the recommendation an explanation of three encoding mechanisms (OpenURL, DC structured value, RDF). The questions we would like you to answer are - what form should we write up our recommendation (what 'template' do we follow?) - what will be the process for getting the recommendation we produce approved? - who do we send it to? We need re-assurance (before spending time writing up) that the process is in place to ensure our recommendation has a good chance of succesfully becoming an 'official DC recommendation'! Note that we have limited the scope somewhat from that of the original DC Citation WG which also considered issues related to version.

Following is the draft recommended process taken from Stu's reply with some additional information from Makx.

Form for the proposal

We do not currently have a template for such proposals, other than basic header material, and Beth Marsh can assist you in pouring your proposal into such a template.

As for the content, what is most important is that the document include:

The more clearly this can be done, of course, the greater the likelihood that objections to the proposal can be resolved quickly. The proposal needs to be concise, but needs to guide an informed reader through the options.

It is my belief that the success of the proposal will depend as much as anything on the clarity of the solution and *why* it is an effective solution. I trust there is confidence that the objections raised in Ottawa are taken into account?

Who to send it to and how will it be approved

The following is a summary of the process for approving such proposals. Makx and I are working on a formal policy document for this issue, and there are details still being worked out, but it will look a bit like this: