<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sorry, I don't agree at all. <br>
<br>
The core Darwin-SW classes include only Darwin Core classes and the two
proposed DwC classes (Organism and CollectionObject a.k.a.
dsw:IndividualOrganism and dsw:Evidence) which underwent 30 day public
comment period [1] and were submitted to the Executive which
recommended further consideration by the RDF Task Group and the
community at large. The Documenting Darwin Core sessions at the TDWG
meeting will pick up these and other open issues for further discussion
and hopefully move them towards closure one way or the other. If the
two proposed classes are at some point accepted for inclusion in DwC,
Darwin-SW will use the new classes and deprecate dsw:IndividualOrganism
and dsw:Evidence, leaving only Darwin Core classes as the core classes
in Darwin-SW. <br>
<br>
It is NOT my view that Darwin-SW is unable to handle current needs for
linking resources effectively. If anyone wants to know why I say that,
come to our talk in the Friday 9AM session on Ontologies and Formal
Models at the meeting. We will show how real SPARQL queries on
Darwin-SW-based data can address important competency questions
involving diverse linked resources. Or see me any time during the
meeting earlier in the week and I'll be happy to give you a personal
demonstration not limited to 9 minutes. <br>
<br>
Steve<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://lists.tdwg.org/pipermail/tdwg-content/2011-September/002727.html">http://lists.tdwg.org/pipermail/tdwg-content/2011-September/002727.html</a>
see also open issue
<a class="moz-txt-link-freetext" href="https://code.google.com/p/darwincore/issues/detail?id=69">https://code.google.com/p/darwincore/issues/detail?id=69</a><br>
<br>
<br>
<br>
<br>
Robert Guralnick wrote:
<blockquote
cite="mid:CADAgxGUZSGt6yTNKLeWn-dASY3j2Xv7uPcVVRBasCGp=C+7E8A@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<div dir="ltr"><br>
<div> Rod --- There are a couple different conceptions of
interrelationships between Darwin Core "classes", including the Darwin
Core Semantic Web effort led by Steve Baskauf and Cam Web, and the
BiSciCol project. Darwin Core SW is here: <a moz-do-not-send="true"
href="https://code.google.com/p/darwin-sw/">https://code.google.com/p/darwin-sw/</a> and
the BiSciCol "take" is here: <a moz-do-not-send="true"
href="http://biscicol.blogspot.com/2013_03_01_archive.html">http://biscicol.blogspot.com/2013_03_01_archive.html</a>.
The Darwin Core SW version includes new classes not in Darwin Core,
while BiSciCol uses only existing class terms and a very simple set of
predicates. </div>
<div><br>
</div>
<div> I think in many people's view, including those of the authors
of the above (although I hate speaking for them), neither DW-SW or
DW-BiSciCol may be really able to handle the current needs for linking
resources together effectively. There has been a major effort to
refocus away from jury-rigging Darwin Core to try to serve in a more
semantic framework and pushing towards other solutions that align
biodiversity standards more with the OBO Foundry (<a
moz-do-not-send="true" href="http://www.obofoundry.org/">http://www.obofoundry.org/</a>).
The Biocollections Ontology (BCO; <a moz-do-not-send="true"
href="https://code.google.com/p/bco/">https://code.google.com/p/bco/</a>)
represents (what I hope) is a clear rethinking of the challenge that
does connect back to the Darwin Core.</div>
<div><br>
</div>
<div>Best, Rob</div>
<div> </div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sun, Oct 13, 2013 at 1:52 PM, Roderic
Page <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:r.page@bio.gla.ac.uk" target="_blank">r.page@bio.gla.ac.uk</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">
<div>I've always been somewhat puzzled by the disconnect between
the TDWG LSID ontology (e.g., <a moz-do-not-send="true"
href="http://rs.tdwg.org/ontology/voc/TaxonConcept"
style="color: blue; text-decoration: underline;" target="_blank">http://rs.tdwg.org/ontology/voc/TaxonConcept</a> )
which has a rich set of classes and links between those classes, and
Darwin Core (e.g., <a moz-do-not-send="true"
href="http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm"
style="color: blue; text-decoration: underline;" target="_blank">http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm</a> )
which overlaps with this vocabulary and, in my opinion, does a worse
job in some areas, notably taxon names and concepts. Maybe the LSID
vocabulary suffered from the limited uptake of LSIDs (apart from the
nomenclators and Catalogue of Life) or from the complexity of dealing
with RDF, but it seems that much of the essential work was done when
Roger Hyam created that ontology.</div>
<div><br>
</div>
<div>What might help is a way to visualise the TDWG LSID ontology
in terms of the interconnections between the different classes. I'm not
aware of such a visualisation (nor of an equivalent one for the Darwin
Core classes). </div>
<div><br>
</div>
<div>In any event, it seems odd to have two distinct ontologies
that are both in use, and which overlap so significantly.</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Rod</div>
<div>
<div>
<div class="h5">
<div>On 13 Oct 2013, at 16:12, Donald Hobern [GBIF] wrote:</div>
<br>
</div>
</div>
<blockquote type="cite"><span
style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; font-size: medium;">
<div link="blue" vlink="purple" lang="EN-GB">
<div>
<div class="h5">
<div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);">It’s been a couple of weeks but I
said I’d try to write something about a more general concern I have
around the way we use basisOfRecord and dcterms:type to hold values
like occurrence, event and materialSample. This is something that has
concerned me for years and that, I worry, is making everything we all
do much messier than it need be.</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);">I believe that the way we have come
to use Darwin Core basisOfRecord is confused and unhelpful. I really
wish we used Darwin Core like this:</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>1.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">basisOfRecord should be used ONLY to
indicate the type of evidence that lies behind a record – a key aspect
of whether the record is likely to be useful for different purposes</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>2.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">basisOfRecord values should be taken
from a hierarchical vocabulary with three main branches:</span></div>
<div
style="margin: 0in 0in 0.0001pt 1in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>a.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">“specimens” (i.e. biological material
that can be reviewed), with a hierarchy of subordinate values such as
“pinnedSpecimen”, “herbariumSheet”, etc.</span></div>
<div
style="margin: 0in 0in 0.0001pt 1in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>b.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">derived, non-biological evidence (not
sure what name), with a hierarchy of subordinate values such as
“dnaSequence”, “soundRecording”, “stillImage”, etc.</span></div>
<div
style="margin: 0in 0in 0.0001pt 1in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>c.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">asserted observations with no
revisitable evidence other than the authority of the observer</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>3.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">TDWG should deliver a basic ontology
in the form of a graph of key relationships between the most
significant conceptual entities in our world (TaxonName, TaxonConcept,
Identification, Collection, Specimen, Locality, Agent, …)</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>4.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">This ontology should not attempt to
map all the complexity of biodiversity-related data – just provide the
high-level map and key relationships (TaxonConcept hasName TaxonName,
Specimen heldIn Collection, etc.) – it should leave definition of other
properties as a separate, open-ended activity for the community</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>5.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">This ontology should be reviewed at
regular intervals and versioned as necessary to address critical gaps –
provided that backwards compatibility is maintained (splitting a class
into multiple consitituent classes probably won’t break anything, so
start simple)</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>6.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">The Darwin Core vocabulary should be
published as a flat, open-ended list of terms with clear definitions
that can be freely combined as columns in denormalised records</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>7.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">Every Darwin Core term should be
documented to be tightly associated with a single, fixed class in the
ontology (e.g. scientificName and specificEpithet are ALWAYS considered
to be properties of a TaxonName whether or not that TaxonName object is
clearly referenced or separated out)</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>8.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">Every data publisher should be
encouraged to share all relevant data elements in their source data in
the most convenient normalised or denormalised form, provided they use
the recognised Darwin Core properties for elements that match the
definition for those terms, and provided they give some metadata for
other elements. Possible forms include:</span></div>
<div
style="margin: 0in 0in 0.0001pt 1in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>a.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">A completely hierarchical, ABCD-like,
XML representation</span></div>
<div
style="margin: 0in 0in 0.0001pt 1in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>b.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">A completely flat denormalised,
simple-DwC-like, CVS representation, if the data includes no elements
with higher cardinality</span></div>
<div
style="margin: 0in 0in 0.0001pt 1in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>c.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">A set of flat, relational, CVS
representations, as with Darwin Core Archive star schemas, but with
freedom to have more complex graphed relationships as needed</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>9.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">Each table of CVS data in 8b and 8c
is a view that corresponds to a linear subgraph of the TDWG ontology,
identified by the classes of the DwC properties used – this allows us
to infer the “shape” of the data in terms of the ontology</span></div>
<div
style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"><span>10.<span
style="font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> <span> </span></span></span></span><span
style="color: rgb(31, 73, 125);">If we do this, we do not need to
worry about whether a record is a checklist record, an event, an
occurrence, a material sample or whatever else, although we could use
the dcterms: type property, or some new property, to hold this detail
as a further clue to intent and possible use for the record</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);">Here is an example. In today’s
terms, what sort of DwC record is this? Do I really have to replace
“recordId” with “eventId”, “occurrenceId” or similar? And which should
I choose?</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><b><span
style="color: rgb(31, 73, 125);">recordId, decimalLatitude,
decimalLongitude, coordinatePrecision, eventDate, scientificName,
individualCount</span></b></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);">I think it is clear that this record
tells us that there was a recording event at a particular time and
place where someone or some process recorded a given number of
individual organisms which were identified as representatives of a
taxon concept with a name corresponding to the supplied scientific
name. In other words this gives us some properties from a subgraph
that might include, say, instances of TDWG Event, Locality, Date,
Occurrence, Identification, TaxonConcept and TaxonName classes. None of
these is specifically referenced but we can unambiguously fold the flat
record onto the ontology. We can moreover then use the combination of
supplied elements to decide whether this record would be of interest to
GBIF, a national information facility, a tool cataloguing uses of
scientific names, etc. The same will also apply if multiple CVS tables
are provided as in 8c.</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);">I have thought about this for a long
time and cannot yet think of an area in which this would not work
efficiently – and unambiguously – for all concerned. There are some
cases where multiple instances of the same ontology class would be
referenced within a single record, which may mean more care is needed
by the publisher (e.g. if an insect specimen record includes a
reference to a host plant). There may be cases where automated review
of the data indicates that there are impossible combinations or
ambiguities that the publisher must resolve. However I believe we
could use this approach to generalise all mobilisation and consumption
of biodiversity data (including all the things we have addressed under
ABCD, SDD, TCS, Plinian Core, etc.) and to make it genuinely possible
for any data holder to share all the data they have in a form that
makes sense to them, while allowing others to consume these data
intelligently.</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);">Right now, I think our confused use
of basisOfRecord is almost the only thing that stops us from exploring
this. We have blurred the question of the evidence for a record, with
the question of the “shape” of the record as a subgraph. These are
different things. Separating them will allow us to get away from some
of our unresolvable debates and open up the doors to much simpler data
sharing and reuse.</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);">Thanks,</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);">Donald</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="color: rgb(31, 73, 125);"> </span></div>
<div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="font-size: 10.5pt; font-family: Consolas; color: rgb(31, 73, 125);"
lang="EN-US">----------------------------------------------------------------------</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="font-size: 10.5pt; font-family: Consolas; color: rgb(31, 73, 125);"
lang="EN-US">Donald Hobern - GBIF Director -<span> </span></span><a
moz-do-not-send="true" href="mailto:dhobern@gbif.org"
style="color: blue; text-decoration: underline;" target="_blank"><span
style="font-size: 10.5pt; font-family: Consolas; color: blue;"
lang="EN-US">dhobern@gbif.org</span></a><span
style="font-size: 10.5pt; font-family: Consolas; color: rgb(31, 73, 125);"><span
lang="EN-US"></span></span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="font-size: 10.5pt; font-family: Consolas; color: rgb(31, 73, 125);"
lang="EN-US">Global Biodiversity Information Facility<span> </span></span><a
moz-do-not-send="true" href="http://www.gbif.org/"
style="color: blue; text-decoration: underline;" target="_blank"><span
style="font-size: 10.5pt; font-family: Consolas; color: blue;"
lang="EN-US">http://www.gbif.org/</span></a><span
style="font-size: 10.5pt; font-family: Consolas; color: rgb(31, 73, 125);"><span
lang="EN-US"></span></span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="font-size: 10.5pt; font-family: Consolas; color: rgb(31, 73, 125);"
lang="DA">GBIF Secretariat, Universitetsparken 15, DK-2100 Copenhagen
Ø, Denmark</span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="font-size: 10.5pt; font-family: Consolas; color: rgb(31, 73, 125);"
lang="EN-US">Tel: <a moz-do-not-send="true"
href="tel:%2B45%203532%201471" value="+4535321471" target="_blank">+45
3532 1471</a> Mob: <a moz-do-not-send="true"
href="tel:%2B45%202875%201471" value="+4528751471" target="_blank">+45
2875 1471</a> Fax: <a moz-do-not-send="true"
href="tel:%2B45%202875%201480" value="+4528751480" target="_blank">+45
2875 1480</a></span></div>
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;"><span
style="font-size: 10.5pt; font-family: Consolas; color: rgb(31, 73, 125);"
lang="EN-US">----------------------------------------------------------------------</span></div>
</div>
</div>
</div>
</div>
<div class="im">_______________________________________________<br>
tdwg-content mailing list<br>
<a moz-do-not-send="true"
href="mailto:tdwg-content@lists.tdwg.org"
style="color: blue; text-decoration: underline;" target="_blank">tdwg-content@lists.tdwg.org</a><br>
<a moz-do-not-send="true"
href="http://lists.tdwg.org/mailman/listinfo/tdwg-content"
style="color: blue; text-decoration: underline;" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
</div>
</div>
</span></blockquote>
</div>
<br>
<div>
<span
style="text-indent: 0px; letter-spacing: normal; font-variant: normal; font-style: normal; font-weight: normal; line-height: normal; border-collapse: separate; text-transform: none; font-size: medium; white-space: normal; font-family: Helvetica; word-spacing: 0px;"><span
style="text-indent: 0px; letter-spacing: normal; font-variant: normal; font-style: normal; font-weight: normal; line-height: normal; border-collapse: separate; text-transform: none; font-size: medium; white-space: normal; font-family: Helvetica; word-spacing: 0px;">
<div style=""><span
style="text-indent: 0px; letter-spacing: normal; font-variant: normal; font-style: normal; font-weight: normal; line-height: normal; border-collapse: separate; text-transform: none; font-size: medium; white-space: normal; font-family: Helvetica; word-spacing: 0px;">
<div style=""><span
style="text-indent: 0px; letter-spacing: normal; font-variant: normal; font-style: normal; font-weight: normal; line-height: normal; border-collapse: separate; text-transform: none; font-size: medium; white-space: normal; font-family: Helvetica; word-spacing: 0px;">
<div style=""><span
style="text-indent: 0px; letter-spacing: normal; font-variant: normal; font-style: normal; font-weight: normal; line-height: normal; border-collapse: separate; text-transform: none; font-size: medium; white-space: normal; font-family: Helvetica; word-spacing: 0px;">
<div style=""><span
style="text-indent: 0px; letter-spacing: normal; font-variant: normal; font-style: normal; font-weight: normal; line-height: normal; border-collapse: separate; text-transform: none; font-size: medium; white-space: normal; font-family: Helvetica; word-spacing: 0px;">
<div style=""><span
style="text-indent: 0px; letter-spacing: normal; font-variant: normal; font-style: normal; font-weight: normal; line-height: normal; border-collapse: separate; text-transform: none; font-size: medium; white-space: normal; font-family: Helvetica; word-spacing: 0px;">
<div style="">---------------------------------------------------------<br>
Roderic Page<br>
Professor of Taxonomy<br>
Institute of Biodiversity, Animal Health and Comparative Medicine<br>
College of Medical, Veterinary and Life Sciences<br>
Graham Kerr Building<br>
University of Glasgow<br>
Glasgow G12 8QQ, UK<br>
<br>
Email: <span style=""> </span><a moz-do-not-send="true"
href="mailto:r.page@bio.gla.ac.uk" target="_blank">r.page@bio.gla.ac.uk</a><br>
Tel:<span> </span><span style=""> </span><a moz-do-not-send="true"
href="tel:%2B44%20141%20330%204778" value="+441413304778"
target="_blank">+44 141 330 4778</a><br>
Fax:<span> </span><span style=""> </span><a moz-do-not-send="true"
href="tel:%2B44%20141%20330%202792" value="+441413302792"
target="_blank">+44 141 330 2792</a></div>
<div style="">Skype:<span> </span><span style=""> </span>rdmpage<br>
Facebook: <span style=""> </span><a moz-do-not-send="true"
href="http://www.facebook.com/rdmpage" target="_blank">http://www.facebook.com/rdmpage</a></div>
<div style="">LinkedIn: <span style=""> </span><a
moz-do-not-send="true" href="http://uk.linkedin.com/in/rdmpage"
target="_blank">http://uk.linkedin.com/in/rdmpage</a><br>
Twitter: <span style=""> </span><a moz-do-not-send="true"
href="http://twitter.com/rdmpage" target="_blank">http://twitter.com/rdmpage</a><br>
Blog: <span style=""> </span><a moz-do-not-send="true"
href="http://iphylo.blogspot.com" target="_blank">http://iphylo.blogspot.com</a><br>
Home page: <span style=""> </span><a moz-do-not-send="true"
href="http://taxonomy.zoology.gla.ac.uk/rod/rod.html" target="_blank">http://taxonomy.zoology.gla.ac.uk/rod/rod.html</a></div>
<div style="">Wikipedia: <span style=""> </span><a
moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/Roderic_D._M._Page" target="_blank">http://en.wikipedia.org/wiki/Roderic_D._M._Page</a></div>
<div style="">Citations: <span style=""> </span><a
moz-do-not-send="true"
href="http://scholar.google.co.uk/citations?hl=en&user=4Z5WABAAAAAJ"
target="_blank">http://scholar.google.co.uk/citations?hl=en&user=4Z5WABAAAAAJ</a></div>
<div style="">ORCID:<span> </span><span style=""> </span><a
moz-do-not-send="true" href="http://orcid.org/0000-0002-7101-9767"
target="_blank">http://orcid.org/0000-0002-7101-9767</a></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></span></div>
<br>
</div>
<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><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Steven J. Baskauf, Ph.D., Senior Lecturer
Vanderbilt University Dept. of Biological Sciences
postal mail address:
PMB 351634
Nashville, TN 37235-1634, U.S.A.
delivery address:
2125 Stevenson Center
1161 21st Ave., S.
Nashville, TN 37235
office: 2128 Stevenson Center
phone: (615) 343-4582, fax: (615) 322-4942
If you fax, please phone or email so that I will know to look for it.
<a class="moz-txt-link-freetext" href="http://bioimages.vanderbilt.edu">http://bioimages.vanderbilt.edu</a>
</pre>
</body>
</html>