Hi Nico, <div><br></div><div>Wouldn't the individual be asserted to be an instance of a species "concept"<div><br></div><div>For instance:</div><div><br></div><div>The species concept <a href="http://lod.taxonconcept.org/ses/ICmLC#Species">http://lod.taxonconcept.org/ses/ICmLC#Species</a></div>
<div><br></div><div><a href="http://lod.taxonconcept.org/ses/ICmLC#Species"></a>An individual of that species concept <a href="http://lod.taxonconcept.org/ses/ICmLC#Individual">http://lod.taxonconcept.org/ses/ICmLC#Individual</a></div>
<div><br></div><div><a href="http://lod.taxonconcept.org/ses/ICmLC#Individual"></a>An occurrence that has been asserted to be an occurrence of that species <a href="http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9#Occurrence">http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9#Occurrence</a></div>
<div><br></div><div><a href="http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9#Occurrence"></a>Which is documented by this page <a href="http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9.html">http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9.html</a></div>
<div><br></div><div><a href="http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9.html"></a>Relationships between these entities can be browsed via the Knowledge Base view.</div><div><br></div><div>< <a href="http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9%23Occurrence">http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9%23Occurrence</a> ></div>
<div><br></div><div><a href="http://bit.ly">bit.ly</a> <a href="http://bit.ly/jgRUxv">http://bit.ly/jgRUxv</a></div><div><br></div><div><a href="http://bit.ly/jgRUxv"></a>* Note that links on the HTML page will also take you to the views of the different entities in the Knowledge Base.</div>
<div><br></div><div>Also note that someone else could assert that the individual butterfly is actually an instance of a different species concept. One could simply replace these assertions with their own in a separate mapping file, or</div>
<div>with a different predicate. Note the hypothetical links below don't work.</div><div><br></div><div>The individual <a href="http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9#Individual">http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9#Individual</a><br>
</div><div><br></div><div><<a href="http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9#Individual">http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9#Individual</a>> <bioimages:individualHasStevesSpeciesConcept> <<a href="http://lod.bioimages.org/ses/123123#Species">http://lod.bioimages.org/ses/123123#Species</a>></div>
<div><br></div><div>* We might miss some species occurrence records when we do this, so it would be best to avoid creating a number of basically duplicate concepts especially if they not the same "kind" of concept.</div>
<div> For instance those that are linked to a specific name or classification hierarchy.</div><div><br></div><div>Respectfully,</div><meta charset="utf-8"><div><br></div><div>- Pete<br><br><div class="gmail_quote">On Tue, May 31, 2011 at 6:10 AM, Nico Cellinese <span dir="ltr"><<a href="mailto:ncellinese@flmnh.ufl.edu">ncellinese@flmnh.ufl.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word">I personally like this nicely refined suggestion but to be honest, I can also live with the others previously made. What I don't seem to be able to digest is the notion that same individual will later be equaled by some to a species. That assertion is hard to swallow.<div>
<br></div><div>Nico<br><div><br></div><div><br><div><div><div></div><div class="h5"><div>On May 31, 2011, at 3:44 AM, Paul Murray wrote:</div><br></div></div><blockquote type="cite"><div><div></div><div class="h5"><div style="word-wrap:break-word">
<div><span style="font-family:Times"><pre>><i> An Occurrence is a combination of an Individual and an Event.
</i>><i> An Occurrence is a coupling of an Individual and an Event.
</i>><i> An Occurrence is a pairing of an Individual and an Event.
</i></pre><div><font face="Helvetica"><font face="Times"><i><br></i></font></font></div><div><span style="font-family:Helvetica">How about:</span></div><div><span style="font-family:Helvetica">An Occurrence is the <i>reification</i> of an individual's involvement in (entaglement with? presence at? relationship to?) an event. It reifies an "Event involvesIndividual Individual" fact.</span></div>
<div><font face="Helvetica"><br></font></div></span></div><div>The need for this construct is that we often need to say a number of additional things about an individual's involvement with (presence at) an event beyond simply assertin that there is some relationship. We need to say what tokens that individual left, what role that individual had (Predator? Prey? Parasite?), perhaps temporal or other limits of that particular individual at the event. Occurrence is the object to which these facts may be attached. An individual might meaningfully have more than one occurrence at an event - particularly in cases where events are part-of larger events, or where an individual somehow has multiple roles (hyenas chased away from their kill by a lion - or is it the other way around?).</div>
<div><br></div><div>To put it another way: "reification" = "tuple" = "association table" = "pulling a property out into an object". More or less.</div><div><br></div><div>To put it another another way, an Occurence object stands in relation to an event and an individual much as a TaxonRelationship object stands in relation to the two taxa it mentions. You <i>could</i> simply model taxonomy with a "hasSubtaxon" predicate, but we usually need to say a great deal more about taxonomic relationships than that.</div>
<div><br></div><div><br></div><p>If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments.
Please consider the environment before printing this email.</p>
</div></div></div>_______________________________________________<br>tdwg-content mailing list<br><a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">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>
</blockquote></div><br></div></div></div><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>
<br></blockquote></div><br><br clear="all"><br>-- <br>
------------------------------------------------------------------------------------<br>Pete DeVries<br>Department of Entomology<br>University of Wisconsin - Madison<br>445 Russell Laboratories<br>1630 Linden Drive<br>Madison, WI 53706<br>
Email: <a href="mailto:pdevries@wisc.edu" target="_blank">pdevries@wisc.edu</a><br><a href="http://www.taxonconcept.org/" target="_blank">TaxonConcept</a> & <a href="http://about.geospecies.org/" target="_blank">GeoSpecies</a> Knowledge Bases<br>
A Semantic Web, <a href="http://linkeddata.org/" target="_blank">Linked Open Data</a> Project<br>--------------------------------------------------------------------------------------<br>
</div></div>