<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, sans-serif" size="2">
<div>All,</div>
<div>The MEDIN discovery metadata guidance document (2.3.4) is available at <a href="http://www.oceannet.org/marine_data_standards/medin_approved_standards/documents/medin_schema_doc_2_3_4_30nov2010.pdf"><font color="#0000FF"><u>http://www.oceannet.org/marine_data_standards/medin_approved_standards/documents/medin_schema_doc_2_3_4_30nov2010.pdf</u></font></a>
</div>
<div>The changes will filter down to the tools in due course.</div>
<div> </div>
<div>We have also revamped the oceannet website (<a href="http://www.oceannet.org"><font color="#0000FF"><u>www.oceannet.org</u></font></a>) including the standards pages – any comments back to me please.</div>
<div> </div>
<div>Lastly, Becky has provided a draft definition of what a ‘service’ is - see below – any comments back to Becky at <a href="mailto:bese@MBA.ac.uk"><font color="#0000FF"><u>bese@MBA.ac.uk</u></font></a></div>
<div>Best Wishes</div>
<div>Mark</div>
<div> </div>
<div> </div>
<div> </div>
<div><font face="Arial, sans-serif"><b>Services</b></font></div>
<div> </div>
<div><font face="Arial, sans-serif">MEDIN considers a service to be a web service (specifically an implementation of a geo-portal software architecture), that provides access to geographic and thematic information in marine data; </font></div>
<div> </div>
<div style="margin-top: 3pt; margin-bottom: 3pt; "><font face="Arial, sans-serif" size="3">A <b>discovery</b> service – Allows the discovery of data set(s) via the searching of metadata records. </font></div>
<div><font face="Times New Roman, serif" size="3"> </font></div>
<div><font face="Arial, sans-serif">A <b>view</b> service – Allows the viewing of data set(s) or parts of data set(s) via a map interface.</font></div>
<div><font face="Arial, sans-serif"> </font></div>
<div><font face="Arial, sans-serif">A <b>download</b> service - gives access to data set(s) or a part of data set(s). The</font></div>
<div><font face="Arial, sans-serif">Download Service provides access to spatial objects whether representing discrete or continuous phenomena.</font></div>
<div> </div>
<div><font face="Arial, sans-serif">A <b>transformation</b> service – a service for carrying out data content transformations. This is an auxiliary service type normally connected with a download service. It is designed as a mechanism to enable spatial data
sets to be transformed with a view to achieving interoperability. An examples would be transforming between coordinate reference systems. A transformation service will usually not be made directly accessible for the general public but a metadata record of
it should exist.</font></div>
<div> </div>
<div><font face="Arial, sans-serif">An <b>invoke</b> spatial data service – A service invoking the use of other spatial data services that allows the definition of data inputs and data outputs expected by the spatial service and defines a workflow or service
chain combining multiple services. It also allows the definition of a web service interface managing and accessing (executing) workflows or service chains.</font></div>
<div> </div>
<div> </div>
</font>
<br />--
<br />This message (and any attachments) is for the recipient only. NERC
<br />is subject to the Freedom of Information Act 2000 and the contents
<br />of this email and any reply you make may be disclosed by NERC unless
<br />it is exempt from release under the Act. Any material supplied to
<br />NERC may be stored in an electronic records management system.</body>
</html>