<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bob,<br>
It seems to me that the most semantically clear way to indicate in a
machine-readable way that two herbarium sheets are duplicates would be
to assert that they have the same dwc:individualID. individualID is
defined as "An identifier for an individual or named group of
individual organisms represented in the Occurrence" so asserting that
two occurrences represent the same individual or named group of
individual organisms pretty much exactly describes what duplicate
specimens are. I use this same approach to indicate that <br>
<a class="moz-txt-link-freetext" href="http://bioimages.vanderbilt.edu/baskauf/67307">http://bioimages.vanderbilt.edu/baskauf/67307</a><br>
is an image of an acorn from the same tree: <br>
<a class="moz-txt-link-freetext" href="http://bioimages.vanderbilt.edu/ind-baskauf/67304">http://bioimages.vanderbilt.edu/ind-baskauf/67304</a><br>
as the bark image<br>
<a class="moz-txt-link-freetext" href="http://bioimages.vanderbilt.edu/baskauf/67312">http://bioimages.vanderbilt.edu/baskauf/67312</a><br>
I won't say more here as I have written more extensively on this
approach in <i>Biodiversity Informatics</i> 7:17-44
(<a class="moz-txt-link-freetext" href="https://journals.ku.edu/index.php/jbi/article/view/3664">https://journals.ku.edu/index.php/jbi/article/view/3664</a>). You can
also look at the RDF associated with those GUIDs to see what I mean.
Solving this problem is also one of the reasons I have proposed adding
the class Individual to DwC (i.e. so that the individuals that are the
object of dwc:individualID can be rdfs:type'd using a well-known
vocabulary and therefore be "understood" by linked data clients).<br>
<br>
Steve<br>
<br>
Bob Morris wrote:
<blockquote
cite="mid:AANLkTi=i5EGixn8h1E=ohN_KLAoFs4ApbxPvA9icTowp@mail.gmail.com"
type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="http://rs.tdwg.org/dwc/terms/index.htm#associatedOccurrences">http://rs.tdwg.org/dwc/terms/index.htm#associatedOccurrences</a> carries
this description:
associatedOccurrences
Identifier: <a class="moz-txt-link-freetext" href="http://rs.tdwg.org/dwc/terms/associatedOccurrences">http://rs.tdwg.org/dwc/terms/associatedOccurrences</a>
Class: <a class="moz-txt-link-freetext" href="http://rs.tdwg.org/dwc/terms/Occurrence">http://rs.tdwg.org/dwc/terms/Occurrence</a>
Definition: A list (concatenated and separated) of identifiers of
other Occurrence records and their associations to this Occurrence.
Comment: Example: "sibling of FMNH:Mammal:1234; sibling of
FMNH:Mammal:1235". For discussion see
<a class="moz-txt-link-freetext" href="http://code.google.com/p/darwincore/wiki/Occurrence">http://code.google.com/p/darwincore/wiki/Occurrence</a>
Details: associatedOccurrences
My questions:
a. Are the names of the associations, and/or the syntax of the value
meant to be community defined?
b. If no to a. , where are those definitions? If yes, Have any
communities defined any names and syntax? I am especially interested
in "duplicate of" in the case of herbarium sheets."
c. (May share an answer with b.) Is there any use being made by anyone
in which associatedOccurrences is designed to have machine-readable
values. If yes, where?
Thanks
Bob
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Steven J. Baskauf, Ph.D., Senior Lecturer
Vanderbilt University Dept. of Biological Sciences
postal mail address:
VU Station B 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) 343-6707
<a class="moz-txt-link-freetext" href="http://bioimages.vanderbilt.edu">http://bioimages.vanderbilt.edu</a>
</pre>
</body>
</html>