Hi Alison,
Welcome back!
Right, what I want to do is to generate an ontology containing the mapping between the BODC Parameter Discovery Vocabulary, the CF Standard Names and the GCMD Science Keywords (that used to be called Parameter Valids). This is going to be 'for real' and therefore needs to be maintainable, which implies that it is built from versioned vocabularies and that the differences between the versions mapped and any subsequent versions need to be accurately documented in detail so that I can successfully manage ontology maintenance.
The way I would like to do this in practice would be to add current synchronised copies of CF Standard Names and the GCMD Science Keywords to the BODC-maintained NERC DataGrid Vocabulary Server. This is an automatically managed back end vocabulary storage system maintaining creation/modified timestamps for all terms, versioning for all term lists and an audit trail of all changes made. The back end is interfaced by a Web Service API (
http://www.bodc.ac.uk/products/web_services/vocab/). A demonstration client (
http://vocab.ndg.nerc.ac.uk/client/vocabServer.jsp) using the Web Service API is temporarily available until the appropriate part of the BODC web site has been redeveloped to use the API.
If this is done, I will get Michael Hughes in BODC to extend Luis Bermudez's voc2OWL software to output OWL files from our vocabulary back end (an Oracle database). This will be used to output the lists to be mapped and I will then use the VINE tool to actually do the mapping.
For this to happen, I need the following.
>From CF:
The blessing of the CF community to serve Standard Names from the NDG server (would NOT replace existing sources as canonical units not served and existing synonym management not carried through)
A spreadsheet containing two columns - standard name and its accompanying description (standard name version zero, which increments by 1 for each subsequent maintenance session)
Update spreadsheets for new standard names
Information on any changes/corrections to existing standard names or their descriptions
>From GCMD:
The blessing of GCMD to serve Science Keywords operationally (a demonstration snapshot is there at the moment)
Agreement on start point and maintenance mechanism (MEDI meeting next week gives us an opportunity)
Assistance upgrading our demonstration snapshot to any agreed start point
Here's hoping we can make this happen.
Cheers, Roy.
>>> "Pamment, JA (Alison)" <J.A.Pamment at rl.ac.uk> 8/25/2006 4:18 pm >>>
Hi Roy,
I am just checking my email quickly as I will be on leave next week and
also I am currently working fewer hours because my daughter is off
school. I will be back to my term time working arrangements (Mon-Fri
0830-1330) on Thursday 7th September and I will contact you as soon as
possible after then.
Cheers,
Alison
------
Alison Pamment Tel: +44 1235 778065
NCAS/British Atmospheric Data Centre Fax: +44 1235 445858
Rutherford Appleton Laboratory Email: J.A.Pamment at rl.ac.uk
Chilton, Didcot, OX11 0QX, U.K.
> -----Original Message-----
> From: Roy Lowry [mailto:rkl at bodc.ac.uk]
> Sent: 25 August 2006 12:42
> To: Pamment, JA (Alison)
> Subject: CF Standard Names
>
> Hi Alison,
>
> Once you are back after the summer break, could you let me know when
you
> will be around so I can co-ordinate with you about establishing
serving a
> synchronised copy of the CF Standard Names through the NDG Vocabulary
> Server.
>
> Cheers, Roy.
>
>
>
> --
> This message (and any attachments) is for the recipient only. NERC
> is subject to the Freedom of Information Act 2000 and the contents
> of this email and any reply you make may be disclosed by NERC unless
> it is exempt from release under the Act. Any material supplied to
> NERC may be stored in an electronic records management system.
--
This message (and any attachments) is for the recipient only. NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.
Received on Thu Sep 07 2006 - 02:59:09 BST
