<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:794062422;
mso-list-type:hybrid;
mso-list-template-ids:1493856486 -997399412 201916419 201916421 201916417 201916419 201916421 201916417 201916419 201916421;}
@list l0:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">G’day again TDWGers:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Matt passed on links to this thread to me and suggested I comment, as I was the author of the O&M standard (published as ISO 19156:2011 and OGC Abstract Spec Topic 20).
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">For those who are not aware of this work, there is a short Wikipedia page
<a href="http://en.wikipedia.org/wiki/Observations_and_Measurements">http://en.wikipedia.org/wiki/Observations_and_Measurements</a> whose main value is it has links to a number of more detailed resources.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Probably the richest of these is another Wiki page at CSIRO
<a href="https://www.seegrid.csiro.au/wiki/AppSchemas/ObservationsAndSampling">https://www.seegrid.csiro.au/wiki/AppSchemas/ObservationsAndSampling</a> which hasn’t been updated much recently, but at least has some diagrams embedded.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">As Matt and others have hinted, as a result of a workshop at NCEAS a few years ago, there were some tweaks to allow it to meet some of the requirements identified in OBOE, just
in time to beat the ISO deadline!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">O&M includes a generic model for ‘Sampling Features’ – being those artefacts that are created to assist the observation process, but would not exist and have very much interest
otherwise. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Things like specimens, transects, sections, quadrats, scenes and swaths, drillholes, flightlines, trajectories, ships tracks, etc.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Because it is a generic standard, you won’t find things with names familiar to any particular discipline, and there are a lot of stub classes for supporting information which
need filling out for specific applications. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">But the intention is that it provides a framework for a discipline or community to specialize for their purposes, while retaining some topology and perhaps terminology (maybe
just as super-classes) that help with information sharing across discipline boundaries.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">The main properties of a sampling feature are
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Calibri","sans-serif";color:#1F497D">The sampledFeature – being the domain object which it is being used to characterize<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Calibri","sans-serif";color:#1F497D">Related sampling features – other features related to the observational strategy<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Calibri","sans-serif";color:#1F497D">Related observations – observation events that use this sampling feature (for which another generic model is provided)
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">We’ve generally found it helpful in teasing apart observational records and protocols in a variety of environmental science applications, and other have applied it in oceans,
meteorology, even air-traffic control! <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">The primary classification of sampling features in O&M is by topological dimension (point, curve, surface, solid), because these are commonly used and afford common processing
methods. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">‘Specimen’ is the other concrete sampling-feature type.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">There is no ‘sample’ class, because it is such an overloaded word (noun, verb, statistical sample vs ex-situ sample, etc).
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">O&M and its Sampling Feature model was designed in UML.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">As Matt notes that the original implementation in the OGC context was in XML, using GML
<a href="http://schemas.opengis.net/samplingSpecimen/2.0/specimen.xsd">http://schemas.opengis.net/samplingSpecimen/2.0/specimen.xsd</a> and
<a href="http://schemas.opengis.net/samplingSpatial/2.0/spatialSamplingFeature.xsd">
http://schemas.opengis.net/samplingSpatial/2.0/spatialSamplingFeature.xsd</a> . <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">However, it has been implemented other ways: there is an OWL2/RDFS representation at
<a href="http://def.seegrid.csiro.au/isotc211/iso19156/2011/sampling">http://def.seegrid.csiro.au/isotc211/iso19156/2011/sampling</a> which is linked in with OWL versions of a bunch of the other ISO standards, and therefore probably makes too many commitments
for the faint hearted – see paper from ISWC 2013 here <a href="http://ceur-ws.org/Vol-1063/paper1.pdf">
http://ceur-ws.org/Vol-1063/paper1.pdf</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">O&M was also one of the core inputs to the W3C Semantic Sensor Network ontology, reported here:
<a href="http://www.w3.org/2005/Incubator/ssn/wiki/Incubator_Report">http://www.w3.org/2005/Incubator/ssn/wiki/Incubator_Report</a> though that focussed on the sensors and observations side of the equation, and hardly deals with sampling.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Hope this helps.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">>> Date: Thu, 21 Aug 2014 18:52:06 -0800<br>
>> From: Matt Jones <<a href="mailto:jones@nceas.ucsb.edu" target="_blank">jones@nceas.ucsb.edu</a>><br>
>> Subject: Re: [tdwg-content] Darwin Core: proposed news terms for<br>
>> expressing sample data<br>
>> To: ?amonn ? Tuama [GBIF] <<a href="mailto:eotuama@gbif.org" target="_blank">eotuama@gbif.org</a>><br>
>> Cc: TDWG Content Mailing List <<a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>><br>
>> Message-ID:<br>
>><br>
<CAFSW8xkx7uRP9PC2g3=<a href="mailto:JT_VJanqujH8nPXoz8GXwh%2BJwKw5Ccw@mail.gmail.com" target="_blank">JT_VJanqujH8nPXoz8GXwh+JwKw5Ccw@mail.gmail.com</a>><br>
>> Content-Type: text/plain; charset="utf-8"<br>
>><br>
>> This proposal is treading on ground that is quite similar to other<br>
>> observations and measurements standards for data exchange that are<br>
already<br>
>> mature, in particular:<br>
>><br>
>> * OGC Observations and Measurements (<br>
>> <a href="http://www.opengeospatial.org/standards/om" target="_blank">http://www.opengeospatial.org/standards/om</a>)<br>
>> * Extensible Observation Ontology (OBOE;<br>
>> <a href="https://semtools.ecoinformatics.org/oboe" target="_blank">https://semtools.ecoinformatics.org/oboe</a>)<br>
>><br>
>> The former is a standard and broadly deployed, whereas the latter is part<br>
>> of a research program in the use of ontologies for measurements. Through<br>
>> collaboration between the two projects, they've been modified to be<br>
>> reasonably isomorphic, but O&M uses an XML serialization while OBOE uses<br>
an<br>
>> OWL-DL serialization. They largely express the same measurements and<br>
>> sampling model once one gets beyond the terminology differences.<br>
>><br>
>> So, I'm wondering if it make much sense to extend Darwin Core, which is<br>
at<br>
>> heart an Occurrence exchange syntax, into this measurements area that is<br>
>> well represented by these other existing specifications? I'm curious to<br>
>> hear why people would even want to do this. And if we do go down this<br>
>> path, won't we just end up with a new syntax that does essentially what<br>
O&M<br>
>> and OBOE do now?<br>
>><br>
>> Matt<br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>