<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello<br>
I would just like to comment on *event core*.<br>
I've been doing a lot of work translating published data into Darwin
Core. During that process I've wished several times that I could use
Event as core. I am happy to hear about that proposed change. It
will make it easier to model the data I am working with.<br>
Anne<br>
<br>
<div class="moz-cite-prefix">On 8/20/2014 7:04 AM, Éamonn Ó Tuama
[GBIF] wrote:<br>
</div>
<blockquote cite="mid:00c201cfbc66$88f90160$9aeb0420$@org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
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;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Hi
Rob,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Thank
you for the feedback. I have tried to address the two main
issues you raise below. At the outset, I would like to
emphasise that much of this work is taking place in the
context of the EU BON project which includes a task on
developing/enhancing tools and standards for data sharing
with a particular focus on the IPT for publishing
sample-based data. So, we were constrained by the need to
publish sample-based data sets in the Darwin Core Archive
format and to demonstrate practical application using a
working prototype. When the discussion on the TDWG list
faded out, we took it to our EU BON partners whose
requirements were essential input to further development. We
recognise that these discussions took place away from TDWG
(although the TDWG/EU BON contributors overlapped) and this
is the reason we are presenting the outcomes here for
further consideration. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">*<b>Event
core</b>*<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">As
the SIGS report indicated, sample data can be modelled in
Darwin Core Archives using either Occurrence or Event as
core. This was the starting point for our evaluation but as
things progressed the data wrangling pushed the model back
towards the </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Event
core. </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">We
actually went through the exercise of mapping multiple test
datasets in an iterative process spanning several months'
work. </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">In
the end, we found that using an Event core better matched
the typical sample data we were dealing with</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">,
allowing use of a measurement-or-fact extension to be
included for the efficient expression of environmental
information associated with the event. The choice comes down
to an Occurrence core or an Event core + Occurrence
extension. In both cases, the true observation records are
Occurrences. The big difference is what type the core has
and therefore to which kind of records you can attach
further facts and extra information with DwC-A extensions.
Many sampling datasets have very rich information about the
site and event, so it is very natural to hang facts from an
Event core. When picking the Occurrence core those facts
would have to be repeated for </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">each
and every occurrence record. Moreover, </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">our
approach doesn’t stop anyone from using the Occurrence core
if they so wish. This just provides a different option for
datasets that better fit an Event core model.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I
want to stress that we are not building a “specific IPT
version” to support an Event core but, rather, we adapted
the IPT so that it can be configured to support any generic
“core + extension” format to enable its use for exploration
of more data formats. This is part of the core codebase and
there were no custom forks of the IPT for this work. Our
view at GBIF is that if there are significant numbers of
data publishers who are keen to adopt, promote and use a
(any) format, and the tools can be configured to do so, then
we should support it, and, if necessary, use a custom
namespace.<span style="color:#1F497D"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">*<b>New
terms around abundance</b>*<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Yes,
the discussion on TDWG did fade out but it was clear that
the term “abundance” as recommended by the SIGS report
(along with abundanceAsPercent) was confusing many when we
were looking for term(s) that reported quantitative measures
of organisms in a sample. It also became clear we would need
to be able to state the type of quantity being measured. An
alternative suggestion for using the MeasurementsOrFact
class was immediately shot down.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">As
some of our main use cases were coming from the EU BON
project, discussion shifted to that forum and consensus
formed about the currently proposed terms. It was within
this group that the additional terms (samplingGeometry,
samplingUnit, eventSeriesID) were proposed and where we
began testing with sample data sets.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Best
regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Éamonn<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:robgur@gmail.com">robgur@gmail.com</a> [<a class="moz-txt-link-freetext" href="mailto:robgur@gmail.com">mailto:robgur@gmail.com</a>] <b>On
Behalf Of </b>Robert Guralnick<br>
<b>Sent:</b> 19 August 2014 16:56<br>
<b>To:</b> Éamonn Ó Tuama [GBIF]<br>
<b>Cc:</b> TDWG Content Mailing List<br>
<b>Subject:</b> Re: [tdwg-content] Darwin Core: proposed
news terms for expressing sample data<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"> Hi Éamonn --- I am curious about the
outcomes presented in the SIGS paper, in particular, this
portion of the paper: <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">"Solutions without introducing an event
core in Darwin Core Archives: During the review of the
solutions for the uses cases, it became apparent that
either model could be applied to every use case. The core
and extensions bore a complementary relationship and
between them could express all the required information.
The core simply provided the central anchor in the star
schema from which to join the additional information.
Therefore, using the Occurrence core, well established in
the GBIF network through uptake of the IPT, seemed more
appropriate than inventing CollectingEvent as an
additional core type."<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> That SIGS paper has John Wieczorek
and you both as authors, including many luminaries across
the biodiversity standards spectrum. Given the above, its
curious to see the EventCore come back again, along with a
specific IPT version to support it. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> So I see two issues, conflated, in
this post you just made. One is the need for an EventCore
at all, and the nature of relating Event and
Occurrence/Material Sample. The second is the
introduction of new terms, which seemingly have arrived
after debate on similar terms - but framed around
abundance - stalled a year ago. To my mind, these both
require some further discussion, because I don't
(necessarily) see TDWG community coherence around either
issue?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best, Rob<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Aug 19, 2014 at 6:11 AM, Éamonn
Ó Tuama [GBIF] <<a moz-do-not-send="true"
href="mailto:eotuama@gbif.org" target="_blank">eotuama@gbif.org</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Dear
All,<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">GBIF
is committed to exploring ways in which the IPT and
Darwin Core Archive format can be extended for
publishing sample-based data sets. In association with
the EU BON project [1], a customised version of the
IPT [2] has been deployed to test this using a special
type of Darwin Core Archive in which the core is an
“Event” with associated taxon occurrences in an
“Occurrence” extension.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The
Darwin Core vocabulary already provides a rich set of
terms with many relevant for describing sample-based
data. Synthesising several sources of input (GBIF
organised workshop on sample data, May 2013 [3],
discussions on the TDWG mailing list in late 2013;
internal discussion among EU BON project partners),
five new terms relating to sample data were identified
as essential. The complete model including these new
terms are fully described with examples in the online
document “Publishing sample data using the GBIF IPT”
[4].<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">As
a first step towards ratification, we would like to
register the new terms in the DwC Google Code tracker
[5] if there are no major objections on this list. The
five terms are:<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p style="margin-bottom:0cm;margin-bottom:.0001pt">1.<span
style="font-size:7.0pt"> </span><b>quantity</b>:
the number or enumeration value of the quantityType
(e.g., individuals, biomass, biovolume,
BraunBlanquetScale) per samplingUnit or a percentage
measure recorded for the sample.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p style="margin-bottom:0cm;margin-bottom:.0001pt">2.<span
style="font-size:7.0pt"> </span><b>quantityType</b>:
: the entity being referred to by quantity, e.g.,
individuals, biomass, %species, scale type.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p style="margin-bottom:0cm;margin-bottom:.0001pt">3.<span
style="font-size:7.0pt"> </span><b>samplingGeometry</b>:
an indication of what kind of space was sampled;
select from point, line, area or volume.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p style="margin-bottom:0cm;margin-bottom:.0001pt">4.<span
style="font-size:7.0pt"> </span><b>samplingUnit</b>:
the unit of measurement used for reporting the
quantity in the sample, e.g., minute, hour, day,
metre, metre^2, metre^3. It is combined with quantity
and quantityType to provide the complete measurement,
e.g., 9 individuals per day, 4 biomass-gm per
metre^2.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p style="margin-bottom:0cm;margin-bottom:.0001pt">5.<span
style="font-size:7.0pt"> </span><b>eventSeriesID</b>:
an identifier for a set of events that are associated
in some way, e.g., a monitoring series; may be a
global unique identifier or an identifier specific to
the series.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Best
regards,<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Éamonn<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">[1]
<a moz-do-not-send="true" href="http://eubon.eu"
target="_blank">http://eubon.eu</a> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">[2]
<a moz-do-not-send="true"
href="http://eubon-ipt.gbif.org" target="_blank">http://eubon-ipt.gbif.org</a>
<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">[3]
<a moz-do-not-send="true"
href="http://www.standardsingenomics.org/index.php/sigen/article/view/sigs.4898640"
target="_blank">http://www.standardsingenomics.org/index.php/sigen/article/view/sigs.4898640</a><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">[4] <span
style="color:#1F497D"><a moz-do-not-send="true"
href="http://links.gbif.org/sample_data_model"
target="_blank"><span style="color:purple">http://links.gbif.org/sample_data_model</span></a></span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">[5] <a moz-do-not-send="true"
href="https://code.google.com/p/darwincore/issues/list" target="_blank">https://code.google.com/p/darwincore/issues/list</a>
</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">____________________________________________________<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span
style="font-size:9.0pt">Éamonn Ó Tuama, M.Sc.,
Ph.D. (<a moz-do-not-send="true"
href="mailto:eotuama@gbif.org" target="_blank">eotuama@gbif.org</a>),
</span></i><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span
style="font-size:9.0pt">Senior Programme Officer
for Interoperability, </span></i><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span
style="font-size:9.0pt">Global Biodiversity
Information Facility Secretariat, </span></i><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span
style="font-size:9.0pt">Universitetsparken 15,
DK-2100, Copenhagen Ø, DENMARK</span></i><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span
style="font-size:9.0pt">Phone: <a
moz-do-not-send="true"
href="tel:%2B45%203532%201494" target="_blank">+45
3532 1494</a>; Fax: <a moz-do-not-send="true"
href="tel:%2B45%203532%201480" target="_blank">+45
3532 1480</a></span></i><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a moz-do-not-send="true"
href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
<a moz-do-not-send="true"
href="http://lists.tdwg.org/mailman/listinfo/tdwg-content"
target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tdwg-content mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a>
<a class="moz-txt-link-freetext" href="http://lists.tdwg.org/mailman/listinfo/tdwg-content">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Anne E. Thessen, Ph.D.
The Data Detektiv, Owner and Founder
Ronin Institute, Research Scholar
443.225.9185</pre>
</body>
</html>