Note that associatedOccurrences is one of the several terms that are meant to allow lists of relationships between resources to be captured in a single field. Others include associatedMedia, associatedReferences, associatedSequnces, and associatedTaxa. The main purposes of these fields is to provide a mechanism to share relationship information in a flat application profile such as the Simple Darwin Core (<a href="http://rs.tdwg.org/dwc/terms/simple/index.htm">http://rs.tdwg.org/dwc/terms/simple/index.htm</a>). If an application profile isn't constrained by being flat, then there is a much more robust way to capture relationships, using the ResourceRelationship class and it's constituent terms (<a href="http://rs.tdwg.org/dwc/terms/index.htm#relindex">http://rs.tdwg.org/dwc/terms/index.htm#relindex</a>).<br>
<br><div class="gmail_quote">On Mon, Aug 23, 2010 at 6:39 PM, Bob Morris <span dir="ltr"><<a href="mailto:morris.bob@gmail.com">morris.bob@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Good idea, but it suffers from the same fate as might<br>
associatedOccurrences (not previously mentioned because I was after<br>
some clarification in principle, with the herbarium duplicate sheets<br>
only one current case of interest): I need to follow whatever the<br>
community practice is of regarding a sheet as part of a duplicate set<br>
distributed by the original collector. I'm told by the people at the<br>
Harvard University Herbaria that "duplicate" usually, but not always,<br>
means from the same organism and same collection event---occasionally<br>
people used to put several organisms on the same sheet, raising the<br>
possibility that they are not even the same taxon. Worse, the<br>
different parts of the same organism might be catalogued as separate<br>
specimens. In this case, an assertion that they are from the same<br>
individual might be true and understandable, but the utility of that<br>
assertion depends on your purpose. Consider a use case in which one<br>
set of traditional duplicates all have a determination that is out of<br>
date, but another specimen---say your acorn collected later from the<br>
same tree---has a current determination. For purposes of notifying<br>
duplicate holders that a new determination has been made to the<br>
original, the later acorn may not be interesting. This means that for<br>
this use, a distributed query of the form "find all records with the<br>
same dwc:individualID" is not as useful as "find all records with the<br>
same dwc:eventID".<br>
<br>
Also, as Mark writes, it doesn't address any other associatedOccurrences.<br>
<br>
More generally, we are working on annotations of data records.<br>
Probably what the real issue here is that associatedOccurrences is an<br>
assertion about organisms, and we are making assertions about<br>
occurrence data.<br>
<br>
On Mon, Aug 23, 2010 at 3:07 PM, Steve Baskauf<br>
<div class="im"><<a href="mailto:steve.baskauf@vanderbilt.edu">steve.baskauf@vanderbilt.edu</a>> wrote:<br>
</div><div><div></div><div class="h5">> Bob,<br>
> It seems to me that the most semantically clear way to indicate in a<br>
> machine-readable way that two herbarium sheets are duplicates would be to<br>
> assert that they have the same dwc:individualID. individualID is defined as<br>
> "An identifier for an individual or named group of individual organisms<br>
> represented in the Occurrence" so asserting that two occurrences represent<br>
> the same individual or named group of individual organisms pretty much<br>
> exactly describes what duplicate specimens are. I use this same approach to<br>
> indicate that<br>
> <a href="http://bioimages.vanderbilt.edu/baskauf/67307" target="_blank">http://bioimages.vanderbilt.edu/baskauf/67307</a><br>
> is an image of an acorn from the same tree:<br>
> <a href="http://bioimages.vanderbilt.edu/ind-baskauf/67304" target="_blank">http://bioimages.vanderbilt.edu/ind-baskauf/67304</a><br>
> as the bark image<br>
> <a href="http://bioimages.vanderbilt.edu/baskauf/67312" target="_blank">http://bioimages.vanderbilt.edu/baskauf/67312</a><br>
> I won't say more here as I have written more extensively on this approach in<br>
> Biodiversity Informatics 7:17-44<br>
> (<a href="https://journals.ku.edu/index.php/jbi/article/view/3664" target="_blank">https://journals.ku.edu/index.php/jbi/article/view/3664</a>). You can also<br>
> look at the RDF associated with those GUIDs to see what I mean. Solving<br>
> this problem is also one of the reasons I have proposed adding the class<br>
> Individual to DwC (i.e. so that the individuals that are the object of<br>
> dwc:individualID can be rdfs:type'd using a well-known vocabulary and<br>
> therefore be "understood" by linked data clients).<br>
><br>
> Steve<br>
><br>
> Bob Morris wrote:<br>
><br>
> <a href="http://rs.tdwg.org/dwc/terms/index.htm#associatedOccurrences" target="_blank">http://rs.tdwg.org/dwc/terms/index.htm#associatedOccurrences</a> carries<br>
> this description:<br>
><br>
> associatedOccurrences<br>
> Identifier: <a href="http://rs.tdwg.org/dwc/terms/associatedOccurrences" target="_blank">http://rs.tdwg.org/dwc/terms/associatedOccurrences</a><br>
> Class: <a href="http://rs.tdwg.org/dwc/terms/Occurrence" target="_blank">http://rs.tdwg.org/dwc/terms/Occurrence</a><br>
> Definition: A list (concatenated and separated) of identifiers of<br>
> other Occurrence records and their associations to this Occurrence.<br>
> Comment: Example: "sibling of FMNH:Mammal:1234; sibling of<br>
> FMNH:Mammal:1235". For discussion see<br>
> <a href="http://code.google.com/p/darwincore/wiki/Occurrence" target="_blank">http://code.google.com/p/darwincore/wiki/Occurrence</a><br>
> Details: associatedOccurrences<br>
><br>
> My questions:<br>
> a. Are the names of the associations, and/or the syntax of the value<br>
> meant to be community defined?<br>
> b. If no to a. , where are those definitions? If yes, Have any<br>
> communities defined any names and syntax? I am especially interested<br>
> in "duplicate of" in the case of herbarium sheets."<br>
> c. (May share an answer with b.) Is there any use being made by anyone<br>
> in which associatedOccurrences is designed to have machine-readable<br>
> values. If yes, where?<br>
><br>
> Thanks<br>
> Bob<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> Steven J. Baskauf, Ph.D., Senior Lecturer<br>
> Vanderbilt University Dept. of Biological Sciences<br>
><br>
> postal mail address:<br>
> VU Station B 351634<br>
> Nashville, TN 37235-1634, U.S.A.<br>
><br>
> delivery address:<br>
> 2125 Stevenson Center<br>
> 1161 21st Ave., S.<br>
> Nashville, TN 37235<br>
><br>
> office: 2128 Stevenson Center<br>
> phone: (615) 343-4582, fax: (615) 343-6707<br>
> <a href="http://bioimages.vanderbilt.edu" target="_blank">http://bioimages.vanderbilt.edu</a><br>
><br>
<br>
<br>
<br>
</div></div><div><div></div><div class="h5">--<br>
Robert A. Morris<br>
Emeritus Professor of Computer Science<br>
UMASS-Boston<br>
100 Morrissey Blvd<br>
Boston, MA 02125-3390<br>
Associate, Harvard University Herbaria<br>
email: <a href="mailto:morris.bob@gmail.com">morris.bob@gmail.com</a><br>
web: <a href="http://bdei.cs.umb.edu/" target="_blank">http://bdei.cs.umb.edu/</a><br>
web: <a href="http://etaxonomy.org/mw/FilteredPush" target="_blank">http://etaxonomy.org/mw/FilteredPush</a><br>
<a href="http://www.cs.umb.edu/~ram" target="_blank">http://www.cs.umb.edu/~ram</a><br>
phone (+1) 857 222 7992 (mobile)<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
<a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
</div></div></blockquote></div><br>