Ticket #585 (closed task: fixed)

Opened 14 years ago

Last modified 13 years ago

[M] Controlled vocab for formats

Reported by: selatham Owned by: rkl
Priority: critical Milestone: ReFactored_Discovery_WebServices
Component: discovery Version:
Keywords: MDIP WS-Discovery2 Cc:

Description (last modified by selatham) (diff)

e.g. "Original", "DIF", "ISO19139" (should this be ISO19115 more people understand that?), "MOLES", "DC"

Get this into Vocab server and identify the namespace etc as appearing in MOLES.

Change History

comment:1 Changed 14 years ago by ko23

1) Vocab title: NDG-recognised formats. 2) Purpose of vocab: 3) Values: these should be as stated in the IDIssues document

Namespace to be provided by vocab server.

comment:2 Changed 14 years ago by ko23

  • Owner changed from ko23 to selatham

To be extended and harmonised in lines with OAI list

comment:3 Changed 14 years ago by selatham

  • Status changed from new to assigned

Actually the only reserved metadataPrefix in the OAI-PMH is 'oai_dc'.

2) Purpose:to distinguish between different metadata formats utilised within NDG. These formats may or may not have been devised by NDG. They could be other recognised standard formats.

comment:4 Changed 14 years ago by ko23

Yeah, that was the idea in IDIssues.

Note that the DC that I create from MOLES is actually OAI DC. So far as I'm aware, this is the only one NDG is interested in at the moment. However, it does potentially mean that I'm misusing the "DC" term, and there should be another one ("OAI-DC" or "DC-OAI"?) to cover the specific DC variant.


comment:5 Changed 14 years ago by selatham

  • Status changed from assigned to new
  • Owner changed from selatham to ko23

Can we call it 'oai_dc'? Then it's exactly the same as that specified in the oai standard. I can envisage some other extensions of Dublin Core appearing. Particularly for citations of datasets (ala CLADDIER), but don't know how/if any different to oai_dc they'll be. ..or maybe we should just say DC?

comment:6 Changed 14 years ago by rkl

My recommendation would be to call it oai_dc then we aren't backed into a corner should we decide to support other DC profiles in the future.

Might it be a good idea to include a URL to a web-accessible schema as part of the definition?

comment:7 Changed 14 years ago by selatham

  • Description modified (diff)

comment:8 Changed 13 years ago by ko23

A quick spreadsheet has been put together at  http://proj.badc.rl.ac.uk/ndg/browser/TI07-MOLES/trunk/Vocabs/Proposals/NDG_Format_Vocab.xls

Roy, is this enough?

comment:9 Changed 13 years ago by selatham

Noticed that it's got OAI_DC rather than lower case oai_dc as suggested in my earlier comment. Any particular reason that we need to stick to upper case for this?

comment:10 Changed 13 years ago by ko23

Nope, but good to get comments ;-)

Seriously, from my perspective, one term's as good as another: it's more important that they are meaningful to everyone else and that they are used consistently.

If someone has either a technical or aesthetic reason for wanting to change them, then I'd like to hear it and it can be taken into account.

comment:11 Changed 13 years ago by rkl


I've looked at Kev's spreadsheet. First comment is that I don't like the keys. Keys should be semantically neutral and these are not. Also, I have an 8-byte size limit on keys in the Vocan server back end that whilst not set in concrete is non-trivial to change.

The column I'm most comfortable with are the abbreviations. I've no concerns about mixed case so could Sue/Kev? agree what is to go in here?

The full terms should not include abbreviations, so things like CSML should be spelled out. No descriptions are present and they need to be.

Finally, can a URI 'point' to something? If the URI is a URN is labels something but doesn't tell you where it is.

Suggest that Kev has another go at the spreadsheet and reaches consensus at RAL. I'll then do the final tidying up and load it up into the server.

comment:12 Changed 13 years ago by ko23

No problem.

This is basically a "first draft to provoke comment" and get suggestions for what should be in there and get it off my laptop (I'm expecting a disk problem ;((( , and I'll let you know more formally when I reckon it's ready to be passed over.

comment:13 Changed 13 years ago by ko23

  • Owner changed from ko23 to rkl

Some acronyms left in "term", but these are extended in the description, or the term would be far too ponderous.

comment:14 Changed 13 years ago by rkl

  • Status changed from new to closed
  • Resolution set to fixed

Vocabulary implemented (N021)

Note: See TracTickets for help on using tickets.