[Medin_standards] MEDIN Stds Meeting, London 24th March Papers

Fri Mar 25 09:58:56 GMT 2011

All,
Thanks for a fruitful meeting yesterday. The minutes will follow but we agreed that I would write our conclusions to changes to the discovery metadata standard immediately and distribute to agree and then changes could be made to the tools asap. Details below: Please note the suggested change to the encoding of end date in temporal extent.
Any comments to all by next Tuesday pm please.
Mark

A number of issues raised by the NERC metadata group were circulated and raised at the meeting. There was general agreement that we should continue to lobby for these changes however until they had been introduced by ISO, INSPIRE and GEMINI then we should not make any amendments to the MEDIN standard. One clarification was made that the GEMINI2 schematron does not fail datasets whose bounding boxes cross the 180/-180 meridian; it simply tests that the east and west bounding coordinates are within the range -180 to 180. The ability to have multiple bounding boxes was appealing and MEDIN should lobby for changes in the GEMINI2 standard.

In addition the following changes were discussed:

Addition of a sub-element 'function' to resource locator - it was felt that until GEMINI2 allows terms other than 'download' to be included then we should omit this sub-element from the MEDIN Resource Locator element.

It was questioned which vocabularies we should use the Anchor element en-coding rather than the Character String for. It was decided all vocabs should be encoded with Anchor element this way and that for vocabs that do not have a ID Code and title then we should put those vocabs onto the NERC vocab server and allocate our own ID Code.

AP. BS to identify which vocabs this applies to; MC to draft spreadsheets; RKL to load to NERC vocab server.

How the end date of temporal extent is used for ongoing datasets was raised. It was clarified that for legacy data where the end date was not known then an approximate date should be given. In the event that the resource being described is ongoing then this sub element should be encoded as <gml:endPosition indeterminatePosition="after">2010-01-25</gml:endPosition>

With the date being the system date and time. It was discussed that the date of last revision could be used but as this conditional in the MEDIN metadata standard then it may not be available and therefore there would be no date to use for the encoding. It is suggested that the metadata tools will state that if the date set collection is ongoing then this Sub sub element End Date should be left null and the tools put in the necessary xml encoding into the xml record.

AP. MC to amend guidance; JP, BS to make necessary changes in tools.

Date of publication in the MEDIN standard will be changed from Mandatory to Conditional as it is not possible to complete accurately for a dataset that is not already published. (Check GEMINI standard first)

AP. MC to change Guidance document for date of publication; end date and refresh xml examples and then re-publish.

In summary
MEDIN will lobby for:

 *   Clarification on the encoding of the URI
 *   Allowing Spatial Resolution to be in dimensions other than meters
 *   Allowing multiple bounding boxes
 *   Allowing other terms than 'download' for the Resource Locator sub element 'function'
MEDIN will make changes to

 *   Obligation for Date of publication
 *   Encoding of vocabularies
 *   Encoding of end date for datasets that are ongoing

From: medin_standards-bounces at biwebs1.nerc-liv.ac.uk [mailto:medin_standards-bounces at biwebs1.nerc-liv.ac.uk] On Behalf Of Charlesworth, Mark E.
Sent: 23 March 2011 12:29
To: medin_standards at mailman.nerc-liv.ac.uk
Subject: Re: [Medin_standards] MEDIN Stds Meeting, London 24th March Papers

All,
3 final papers for the meeting tomorrow. Apologies for late delivery.

The 'Stats_work_prog.doc' is relevant to all and will be discussed. The MEDIN_Discovery_Metadata_etc_etc.doc is for information.

The pdf is for those who are discovery metadata fans. Under this agenda item we will also discuss suggestions including:
Addition of subelement 'function' to resource locator
Agree which vocabs the xml encoding using the anchor link should apply to
Clarify what should be put in the temporal reference 'end date' in the event of it being 'unknown' and 'ongoing'

Mark

From: Charlesworth, Mark E.
Sent: 21 March 2011 13:28
To: Charlesworth, Mark E.; medin_standards at mailman.nerc-liv.ac.uk
Subject: MEDIN Stds Meeting, London 24th March Papers

All,
Please find attached papers for the meeting on Thursday at 10.30.
Any further papers will be distributed at the meeting.
Best Wishes
Mark

From: Charlesworth, Mark E.
Sent: 22 February 2011 13:43
To: Charlesworth, Mark E.; medin_standards at mailman.nerc-liv.ac.uk
Subject: MEDIN Stds Meeting, London 24th March

All,
Please find attached a draft agenda for the next MEDIN Standards Meeting at MRC Head Office, Room L13 - 4, 13th Floor, One Kemble Street, London WC2B 4AN,
Directions are at: http://www.mrc.ac.uk/About/Findus/index.htm

Please confirm your attendance to me so I can make catering arrangements.

Best Wishes
Mark

From: Charlesworth, Mark E.
Sent: 18 November 2010 09:28
To: Charlesworth, Mark E.; medin_standards at mailman.nerc-liv.ac.uk
Subject: RE: Next Stds Meeting London

All,
The next MEDIN Standards meeting will be at the Medical Research Council in London on the 24th March from 10.30 to 4.
Please put this in your diaries and details will follow nearer the time.
Best Wishes
Mark

From: medin_standards-bounces at biwebs1.nerc-liv.ac.uk [mailto:medin_standards-bounces at biwebs1.nerc-liv.ac.uk] On Behalf Of Charlesworth, Mark E.
Sent: 09 November 2010 13:13
To: medin_standards at mailman.nerc-liv.ac.uk
Subject: [Medin_standards] Next Stds Meeting London

All,
The Medical Research Council in London has rooms available on the following dates for the next MEDIN Standards Meeting.
Please let  me know your availability within the next week.
March 15, 16, 17, 22, 23 or 24th
Best Wishes
Mark

--
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.nerc-liv.ac.uk/pipermail/medin_standards/attachments/20110325/a1aed463/attachment.html 