<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Dear DAC Working Group members,</div>
<div> </div>
<div>Apologies if you are receiving information that you are already aware of, but I would like to highlight an issue that the MEIDN Standards Working Group discussed at our last meeting.</div>
<div> </div>
<div>In this meeting, I informed the Standards group of an issue I had found where MEDIN XML which was based on <a href="http://inspire.ec.europa.eu/documents/Metadata/INSPIRE_MD_IR_and_ISO_v1_2_20100616.pdf"><font color="blue"><u>http://inspire.ec.europa.eu/documents/Metadata/INSPIRE_MD_IR_and_ISO_v1_2_20100616.pdf</u></font></a>
has incorrect URLs for ISO codelists.</div>
<div> </div>
<div>In this issue, any URLs which link to ISO codelists following the structure in the example</div>
<div> </div>
<div><gmd:MD_ScopeCode</div>
<div>codeList="<a href=""></a>http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resou</div>
<div>rces/Codelist/gmxCodelists.xml#MD_ScopeCode" codeListValue="dataset"></div>
<div> </div>
<div>will not resolve. </div>
<div> </div>
<div>This is because the section of the snippet ‘…/resources/Codelist/…’ should actually have ‘codelist’ with a lower case ‘c’ e.g ‘…/resources/codelist/…’</div>
<div> </div>
<div>This was addressed by INSPIRE with an addendum in document <a href="http://inspire.ec.europa.eu/documents/Metadata/MD_IR_and_ISO_20131029.pdf"><font color="blue"><u>http://inspire.ec.europa.eu/documents/Metadata/MD_IR_and_ISO_20131029.pdf</u></font></a>
</div>
<div> </div>
<div>Can I please therefore ask all the DACs to check whether their MEDIN XML metadata are constructed using the guidance from the 2010 INSPIRE document or whether you are using the more up to date 2013 guidance? If you have created metadata using the online
tool, your metadata are correct. Unfortunately, up to now, if you have used Metadata Maestro, your metadata will have the incorrect structure URLs.</div>
<div> </div>
<div>The implication of this is subtle but important. Irrespective of the capitalisation, the XML will pass the validator as the URLs are structurally valid, and they will still be usable if manually read, but if stakeholders have systems to read the XML using
machine-to-machine technologies, they will not resolve the ISO lists, and therefore our metadata will not be fully useful to them. </div>
<div> </div>
<div>Many thanks,</div>
<div> </div>
<div>Sean</div>
<div> </div>
<div><img src="cid:28F2B12C22CE4F48A6D818D82FE8AF1C@eurprd06.prod.outlook.com"> </div>
<div> </div>
<div> <font color="#00B0F0"><b>Dr Sean Gaffney</b></font> </div>
<div> Manager, MEDIN Standards and Guidelines Work Stream</div>
<div> Joseph Proudman Building, 6 Brownlow Street Liverpool L3 5DA</div>
<div> w: <a href="http://www.oceannet.org/"><font color="blue"><u>www.oceannet.org</u></font></a>; e: <a href="mailto:sgaf@bodc.ac.uk"><font color="blue"><u>sgaf@bodc.ac.uk</u></font></a>; t: +44 (0) 151 795 4950 </div>
<div> </div>
<div> </div>
<div> </div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><u> ________________________________ </u></span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;">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. </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><u> ________________________________ </u></span></font></div>
</span></font>
</body>
</html>