<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class="Section1">
<p class="MsoNormal">Here's my 2-cents worth…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">An example of important taxon concept content missing from DwC and its extensions (unless I missed it - which is very possible) …<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The identification history of a specimen is a vital audit trail of information. It is the history of taxon concepts within the context of a single specimen. A harvested knowledge of that history across specimens allows you to make important
inferences about taxonomic stability. For example if the taxon concept has wandered over a spread of names which are heterotypic in origin then its' telling you that you are dealing with a taxonomically fuzzy entity. If you are a biosecurity officer deciding
whether a new organisms should be released into the environemnt or allowed across the border then that is a vital piece of information. It's a 'kind of' taxon concept within organism occurrence.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It's in ABCD of course.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So let's add a other extension to DwC. But then what difference between DwC + extensions and ABCD within the context of specimens? One important difference I see is that ABCD is scary to end users because it humungous.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">IMHO DwC should be a bunch of simple core metadata concepts for simple observations/occurrences (not appropriate for surveys!) that facilitates resource discovery. If you wish to 'get data' within this context then one approach is to wrap
the package into ' metadata + data extensions' . And one way of ensuring the data wrapped by the 'data extensions' are integrable across domains is build them from concepts defined within an overarching agreed standard ontology. Likewise I see the observation/occurrence
metadata concepts as the potential entry points to the semantic RDF triple-trails also defined by the same ontology.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">That's the way I look at it, which is probably too simplistic.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And like Paul I'd be intrigued to see DwC deal with some of the tortuous nomenclatural data complexities we recently had to untangle in IndexFungorum to port it into Rich Pyle's 'all codes of life' Global Name Usage Bank (GNUB) data structure.
It was distantly removed from anything currently in DwC.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jerry<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div>
<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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> David Remsen [mailto:dremsen@mbl.edu]
<br>
<b>Sent:</b> Tuesday, 28 April 2009 1:47 a.m.<br>
<b>To:</b> Kevin Richards<br>
<b>Cc:</b> David Remsen; Blum, Stan; Technical Architecture Group mailing list; exec@tdwg.org<br>
<b>Subject:</b> Re: [tdwg-tag] darwin core terms inside tdwg ontology<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Kevin, Can you tell me what the limitations are on being able to exchange taxonomic information with the DwC terms? As far as I can tell, you can exchange fairly complex taxonomic information short of concept-to-concept relations and
I find the DwC-with-extensions approach we are using to exchanging information tied to taxa (not instances of taxa) to be a nice and practical compromise between complexity and practicality. My understanding is that the IPT can output TCS/RDF for those who
want it. I am personally very happy to see the DwC taxon terms added. Finally I can provide format specifications that biologists can understand.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">David Remsen<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Apr 25, 2009, at 9:52 AM, Kevin Richards wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black">I see the ontology as a model of ALL (hopefully, eventually all) the data in our domain of biodiversity informatics. </span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black">I would love to see it as a standard (at the least it might give it a bit more clout).</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black">I agree that the ontology is useful to tie other TDWG schemas together, using it as a core/master model. I would be happy to see it used for ALL tasks within
TDWG, but I understand the usefulnes of the more specific schemas/standards - horses for courses.</span><span style="font-size:
9.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black">If I understand Stan here, I agree with him about the dubious use of DwC for representing Taxon Concepts/Names. As far as I know, it was really intended as
a transfer standard for observation records?? It contains very limited taxon information! It really is not a overly difficult job to use a more suitable schema/ontology. I think the popularity of Darwin Core is due to its simplicity - and I wonder if what
Roger is proposing will help with this - ie an XML implementation of the ontology as well as an RDF version. This will allow people to create very simple XML documents with reasonably simple/flat data, eg an xml document of TaxonName entities, with perhaps
6 or 7 or so key fields - even simpler than DwC. :-)</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black">Kevin</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div id="divRpF910076">
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:black">From:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black"> </span></span><span style="font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:black"><a href="mailto:tdwg-tag-bounces@lists.tdwg.org">tdwg-tag-bounces@lists.tdwg.org</a><span class="apple-converted-space"> </span>[<a href="mailto:tdwg-tag-bounces@lists.tdwg.org">tdwg-tag-bounces@lists.tdwg.org</a>]
On Behalf Of Blum, Stan [<a href="mailto:sblum@calacademy.org">sblum@calacademy.org</a>]<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Saturday, 25 April 2009 6:12 a.m.<br>
<b>To:</b><span class="apple-converted-space"> </span>Technical Architecture Group mailing list;<span class="apple-converted-space"> </span><a href="mailto:exec@tdwg.org">exec@tdwg.org</a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [tdwg-tag] darwin core terms inside tdwg ontology</span><span style="font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<div id="idOWAReplyText927">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><strong><span style="font-size:
10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></strong><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black"> </span></span><span style="font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:black"><a href="mailto:tdwg-tag-bounces@lists.tdwg.org">tdwg-tag-bounces@lists.tdwg.org</a><span class="apple-converted-space"> </span>on
behalf of John R. WIECZOREK<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Fri 2009-04-24 8:58 AM<br>
<b>To:</b><span class="apple-converted-space"> </span>Roger Hyam<br>
<b>Cc:</b><span class="apple-converted-space"> </span>Technical Architecture Group mailing list<br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [tdwg-tag] darwin core terms inside tdwg ontology</span><span style="font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">Anything I should do on the DwC side in anticipation of harmony?<br>
<br>
<a href="http://rs.tdwg.org/dwc/terms/index.htm#theterms" target="_blank">http://rs.tdwg.org/dwc/terms/index.htm#theterms</a><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">===========================================================</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">John,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">At some point, all or (most) of the DarwinCore terms need to be added to the TDWG ontology.</span><span style="font-size:9.0pt;font-family:
"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">But having said that, I also need to say that I'm uncomfortable with:</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">1) The current state of the TDWG ontology (primarily the naming conventions; lets just use terms names), and our understanding of the role it plays in TDWG and
how it will be managed (entry of terms, integration of terms into the conceptual [is-a / has-a] relationships to other terms); and</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">2) the fact that the new DarwinCore straddles or overlaps the roles of an ontology and an application schema.</span><span style="font-size:
9.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">I understood the past TAG roadmaps to indicate that we were adopting an approach in which the TDWG Ontology would be a repository for data concepts that are present
in (or implied by) TDWG standards; and that real data transmission would be accomplished with application schemas. The ontology itself would not be a standard, but would be a tool that helps integrate standards. I thought our standards would be created to
function as application schemas or components of application schemas (as in the DwC and its extensions). I am now pretty confused. <span class="apple-converted-space"> </span>I'd like to hear the rationale for combining taxonomic name/concept with organism
occurrence. I haven't gone over all the existing docs, so apologies if I've missed that, but I think it's confusing that a (new) DarwinCore record could be either a taxonomic name or an organism occurrence, or maybe something else. Maybe I'm too attached
to object orientation and just don't GET the semantic web, but it feels to me like we are stepping into squishy ground.</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">Also, I the the DCMI maintenance procedures are also more appropriately applied to the ontology than a TDWG standard. The existing process for ratifying TDWG
standards and the procedure in the DwC seem to be pretty explicitly in conflict; one can change the other cannot (without becoming another thing).</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">Is anyone else having these same trepidations? I don't think I've been as much of a Rip Van Winkle as Jim Croft, but I clearly missed some important shifts. </span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";
color:black">-Stan</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black"><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial","sans-serif";
color:green">Please consider the environment before printing this email<br>
Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails.<br>
The views expressed in this email may not be those of Landcare Research New Zealand Limited.<span class="apple-converted-space"> </span><a href="http://www.landcareresearch.co.nz">http://www.landcareresearch.co.nz</a><br>
</span><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black">_______________________________________________<br>
tdwg-tag mailing list<br>
<a href="mailto:tdwg-tag@lists.tdwg.org">tdwg-tag@lists.tdwg.org</a><br>
<a href="http://lists.tdwg.org/mailman/listinfo/tdwg-tag">http://lists.tdwg.org/mailman/listinfo/tdwg-tag</a><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Green" size="1">Please consider the environment before printing this email<br>
Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails.<br>
The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz<br>
</font>
</body>
</html>