<!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 text="#000000" bgcolor="#ffffff">
    Dear all:<br>
    <br>
    &nbsp;&nbsp; Our joint paper
    (<a class="moz-txt-link-freetext" href="https://journals.ku.edu/index.php/jbi/article/view/3927/3790">https://journals.ku.edu/index.php/jbi/article/view/3927/3790</a>; you
    may just look at "Summary and Outlook at the end)) and also Dave
    Thau's other publications (<a class="moz-txt-link-freetext" href="http://wwwcsif.cs.ucdavis.edu/~thau/">http://wwwcsif.cs.ucdavis.edu/~thau/</a>;
    perhaps start with the 2007 Ecol. Inform. publication) provide *a*
    vision for usage. There are others since ontology development is
    purpose dependent.<br>
    <br>
    1. Dahdul et al. 2010
    (<a class="moz-txt-link-freetext" href="http://sysbio.oxfordjournals.org/content/59/4/369.full.pdf+html">http://sysbio.oxfordjournals.org/content/59/4/369.full.pdf+html</a>)
    provide a rationale from the viewpoint of large-scale,
    phylogeny-informed, ontology-driven analyses of evolutionary traits.
    Quote:<br>
    <br>
    "A more complex investigation of morphology, such as a comparison of
    structures across a monophyletic group of species, requires
    processing such a large amount of data that it is rarely undertaken
    except by the most determined domain experts. Yet larger-scale
    analyses of the patterns of morphological evolution across multiple
    clades are simply not tractable." [Inference: they would be if we
    had suitable ontologies].<br>
    <br>
    2. Schulz et al. 2008
    (<a class="moz-txt-link-freetext" href="http://bioinformatics.oxfordjournals.org/content/24/13/i313.full">http://bioinformatics.oxfordjournals.org/content/24/13/i313.full</a>)
    address the potential benefits of organizing data from the model
    organism and biomedical community (roughly) according to an
    ontology-driven taxonomic &uuml;bersystem (thanks for that one, Spanish
    accents!):<br>
    <br>
    "To sum up, biological taxa constitute an overarching and systematic
    ordering principle that is relevant in practically all biological
    subject areas. In this article, we will show how the realm of
    biological<br>
    systematics can be embedded into an ontological framework. It is
    structured as follows: We start with a summary introduction of
    domain ontologies in general, as well as in the context of the
    biology, addressing the OBO ontologies and the BioTop biomedical
    topdomain ontology. Then we provide a formal account of different
    aspects of the conceptualization of biological taxa and demonstrate
    how this is implemented in BioTop. Finally, we briefly describe our
    tentative implementation supporting our claim that an overarching
    ontological framework for biology must have a conclusive and
    practical account of biological taxa."<br>
    <br>
    3. Our own (Dave Thau's and mine) view of areas of usage is as
    follows; this is all from the perspective of representing the
    interests of taxonomy past, present and future, which - as some may
    cheerfully argue - has roughly the same relationship to TDWG as
    university administrations have to their faculty. <br>
    <br>
    A. An ontology of strictly nomenclatural relationships. Potentially
    very useful for connecting literature, names, types, and ancillary
    data in ways that name and synonymy relationships cannot. To my
    knowledge this has neither been fleshed out nor implemented, but is
    imo very worthwhile exploring.<br>
    <br>
    B. A full-blown ontology of (parts of) the tree of life (cf. Schulz
    et al. 2010 =&gt; representing phylogeny, classification, names,
    characters, specimens). Will probably only make sense for taxa whose
    classification is largely stable. Not clear whether there is much
    benefit for taxonomy proper.<br>
    <br>
    C. Ontology-based reasoning facilitates semantic integration of
    multiple alternative taxonomies in taxonomic concept world. Once two
    taxonomies are represented in an ontological framework and some
    basic mappings of equivalence among their concepts are done
    (typically by a specialist), then reasoning can infer millions of
    additional relationships. This would presumably make the whole
    taxonomic concept approach and mapping more palatable and scalable.
    Dave Thau has shown how this can work.<br>
    <br>
    (D.) An emerging and growing set of anatomical ontologies (spiders,
    wasps, plants, fishes, etc. =&gt; OBO Foundry) would benefit from
    all or any of A-C, I suppose.<br>
    <br>
    &nbsp;&nbsp; I think it's also worth pondering whether, in addition trying to
    represent today's data and practices in something like OWL-DL -
    which will probably be both challenging and somewhat deflating -
    TDWG can develop and formulate recommendations and examples of more
    "ontology-compatible practices" in taxonomy and taxonomic
    databasing/integretation. That is, practices that don't necessarily
    use OWL just yet but adopt a semantic perspective that's more
    aligned with logics than was/is often the case. A lot of that has to
    do with unstated metadata-type information, I think. <br>
    <br>
    &nbsp;&nbsp; Bottom line of this view: reasoning in (and for!) taxonomy
    can/should help with data integration, based on names (A) and
    concepts (C).<br>
    <br>
    Regards,<br>
    <br>
    Nico<br>
    <br>
    <br>
    On 11/15/2010 9:55 AM, Arlin Stoltzfus wrote:
    <blockquote cite="mid:493D46F9-1ADD-4676-91A2-109EE6BD20DD@umd.edu"
      type="cite">
      <div>
        <div>
          <div>On Nov 13, 2010, at 5:17 AM, Roger Hyam wrote:</div>
          <br class="Apple-interchange-newline">
          <blockquote type="cite"><span class="Apple-style-span"
              style="border-collapse: separate; color: rgb(0, 0, 0);
              font-family: Helvetica; font-style: normal; font-variant:
              normal; font-weight: normal; letter-spacing: normal;
              line-height: normal; orphans: 2; text-indent: 0px;
              text-transform: none; white-space: normal; widows: 2;
              word-spacing: 0px; font-size: medium;">
              <div bgcolor="#FFFFFF">
                <div>I think we need a mother of all points at the
                  beginning</div>
                <div><br>
                </div>
                <div>0) Clearly defined use-cases/scenarios/competency
                  questions that have enough detail to act as tests of
                  any proposed solutions. Without these we will continue
                  to bob around in the sea of good ideas and never
                  arrive at any destination.</div>
              </div>
            </span></blockquote>
          <div><br>
          </div>
          I often have thought the same thing. &nbsp;Folks working on
          ontologies tend to focus on philosophical issues of
          conceptualization, i.e., painting a detailed picture of the
          "things" involved. &nbsp;This quickly leads to problems because, to
          the extent that the world actually can be understood via
          "classes" and "properties", domain experts simply do not agree
          on what these classes and properties are. &nbsp;Yet one of the
          (frequently implicit) assumptions of ontology-building is that
          the domain experts have an agreed-upon description of the
          world, or they can talk themselves to the point of having one.
          &nbsp;</div>
        <div><br>
        </div>
        <div>The alternative is to focus on the process of reasoning
          from inputs to correct outputs, i.e., test-driven ontology
          development. &nbsp;Perhaps domain experts would agree much more
          thoroughly on what inferences are valid, and what ones are
          invalid, from a given set of inputs. &nbsp;In an ideal world, the
          domain experts would provide a rich set of hypothetical
          information inputs, and then they would provide a rich set of
          inferences from them, and perhaps an equally rich set of
          invalid inferences, and then the knowledge engineering folks
          would build the ontology to avoid all the invalid inferences
          and support as many of the valid inferences as they can (until
          the money runs out). &nbsp;</div>
        <div><br>
        </div>
        <div>Are there any examples of this approach? &nbsp;&nbsp;&nbsp;</div>
        <div><br>
        </div>
        <div>Arlin</div>
        <div><br>
          <blockquote type="cite"><span class="Apple-style-span"
              style="border-collapse: separate; color: rgb(0, 0, 0);
              font-family: Helvetica; font-style: normal; font-variant:
              normal; font-weight: normal; letter-spacing: normal;
              line-height: normal; orphans: 2; text-indent: 0px;
              text-transform: none; white-space: normal; widows: 2;
              word-spacing: 0px; font-size: medium;">
              <div bgcolor="#FFFFFF">
                <div>Who is it for? What will it enable them to do? Do
                  they want/need to do it?&nbsp;<br>
                  <div><br>
                  </div>
                </div>
                <div><br>
                  On 13 Nov 2010, at 08:30, Kevin Richards &lt;<a
                    moz-do-not-send="true"
                    href="mailto:RichardsK@landcareresearch.co.nz">RichardsK@landcareresearch.co.nz</a>&gt;
                  wrote:<br>
                  <br>
                </div>
                <blockquote type="cite">
                  <div>'Effective tools' to do X, Y &amp; Z always seem
                    to be on the agenda, but I'm not sure it is the
                    tools that are the hold up. &nbsp;Unfortunately I think
                    it boils down to funding... I'm sure if we had
                    adequate funding to get people together for the
                    required length of time, working on the right stuff
                    etc, etc, then we would make fantastic progress.<span
                      class="Apple-converted-space">&nbsp;</span><br>
                    <br>
                    I'm thinking a really good session with a basic UML
                    tool would be a big step forward. &nbsp;I have got hold
                    of a UML tool and intend to have a go at a core tdwg
                    model. &nbsp;I think it would be great then if we could
                    organise a session on working on this model.<br>
                    <br>
                    Kevin<br>
                    <br>
                    Sent from my HTC<br>
                    <br>
                    <div id="htc_header">----- Reply message -----<br>
                      From: "Lee Belbin" &lt;<a moz-do-not-send="true"
                        href="mailto:leebelbin@gmail.com">leebelbin@gmail.com</a>&gt;<br>
                      Date: Sat, Nov 13, 2010 3:42 pm<br>
                      Subject: [tdwg-content] Relation of GNA to TDWG
                      vocabularies<br>
                      To: "<a moz-do-not-send="true"
                        href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a>"
                      &lt;<a moz-do-not-send="true"
                        href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a>&gt;<br>
                      <br>
                    </div>
                    <font size="2">
                      <div class="PlainText">Well stated Stan, but I'd
                        add a third-<br>
                        <br>
                        3. Effective tool/s for viewing (graph,
                        sub-graph, tables, properties etc.),<br>
                        add/delete/modify with adaptable governance
                        control (e.g., assigned management<br>
                        to sub-graph domains), annotate (with full
                        logging of who did what, when and<br>
                        how...). This is in effect a collaboration tool.<br>
                        <br>
                        Until we have a tool (preferable to tools) that
                        can be intuitive and effective<br>
                        for building, managing and deploying /exporting
                        vocabs or ontologies, we will<br>
                        struggle with this socially and technically
                        tough, but very necessary task. The<br>
                        social issues are the hardest, but an effective
                        collaboration tool would be a<br>
                        big help.<br>
                        <br>
                        A tool that will be readily embraced&nbsp; by #2 (the
                        domain specialists) seems far<br>
                        more important than the tools I've seen so far
                        that are embraced by #1 (e.g.<br>
                        Prot&eacute;g&eacute;).<br>
                        <br>
                        That we don't have a TDWG ontology is an
                        increasing worry.<br>
                        <br>
                        Lee<br>
                        <br>
                        Lee Belbin<br>
                        Geospatial Team Leader<br>
                        Atlas of Living Australia<br>
                        <br>
                        <br>
                        -----Original Message-----<br>
                        From:<span class="Apple-converted-space">&nbsp;</span><a
                          moz-do-not-send="true"
                          href="mailto:tdwg-content-bounces@lists.tdwg.org">tdwg-content-bounces@lists.tdwg.org</a><br>
                        [<a moz-do-not-send="true"
                          href="mailto:tdwg-content-bounces@lists.tdwg.org">mailto:tdwg-content-bounces@lists.tdwg.org</a>]
                        On Behalf Of Blum, Stan<br>
                        Sent: Saturday, 13 November 2010 9:43 AM<br>
                        To:<span class="Apple-converted-space">&nbsp;</span><a
                          moz-do-not-send="true"
                          href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
                        Subject: Re: [tdwg-content] Relation of GNA to
                        TDWG vocabularies<br>
                        <br>
                        Progress on the TDWG ontology seems to require:<br>
                        <br>
                        1) one or more people with good sense of what
                        can be done with ontologies, both<br>
                        in the near-term and long-term; and<br>
                        2) one or more people who understand the way
                        information is partitioned in this<br>
                        domain and how it could fit together.<br>
                        <br>
                        I think we have a lot of #2, but not many of #1.<br>
                        <br>
                        FYI, we have seed money to bring these
                        categories together.<br>
                        <br>
                        -Stan<br>
                        <br>
                        <br>
                        On 11/12/10 2:25 PM, "Bob Morris" &lt;<a
                          moz-do-not-send="true"
                          href="mailto:morris.bob@gmail.com">morris.bob@gmail.com</a>&gt;
                        wrote:<br>
                        <br>
                        &gt; On Fri, Nov 12, 2010 at 4:57 PM, Richard
                        Pyle<span class="Apple-converted-space">&nbsp;</span><br>
                        &gt; &lt;<a moz-do-not-send="true"
                          href="mailto:deepreef@bishopmuseum.org">deepreef@bishopmuseum.org</a>&gt;<br>
                        &gt; wrote:<br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><br>
                        &gt;&gt; [...] the current status of the
                        TDWG-Ontology efforts. &nbsp;The Google<span
                          class="Apple-converted-space">&nbsp;</span><br>
                        &gt;&gt; Code website seems a bit anemic,<br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><br>
                        &gt; Ooh, I love that line.&nbsp; I think I'll put it
                        in the script of my next<span
                          class="Apple-converted-space">&nbsp;</span><br>
                        &gt; animation, to be titled: "Alpha and Beta
                        discuss the current status of<span
                          class="Apple-converted-space">&nbsp;</span><br>
                        &gt; of the TDWG-Ontology efforts"<br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><br>
                        &gt; Thanks for correcting the URL.<br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><br>
                        &gt; Bob<br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><br>
                        &gt; Robert A. Morris<br>
                        &gt; Emeritus Professor&nbsp; of Computer Science
                        UMASS-Boston<br>
                        &gt; 100 Morrissey Blvd<br>
                        &gt; Boston, MA 02125-3390<br>
                        &gt; Associate, Harvard University Herbaria<br>
                        &gt; email:<span class="Apple-converted-space">&nbsp;</span><a
                          moz-do-not-send="true"
                          href="mailto:morris.bob@gmail.com">morris.bob@gmail.com</a><br>
                        &gt; web:<span class="Apple-converted-space">&nbsp;</span><a
                          moz-do-not-send="true"
                          href="http://bdei.cs.umb.edu/">http://bdei.cs.umb.edu/</a><br>
                        &gt; web:<span class="Apple-converted-space">&nbsp;</span><a
                          moz-do-not-send="true"
                          href="http://etaxonomy.org/mw/FilteredPush">http://etaxonomy.org/mw/FilteredPush</a><br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><a
                          moz-do-not-send="true"
                          href="http://www.cs.umb.edu/%7Eram">http://www.cs.umb.edu/~ram</a><br>
                        &gt; phone (+1) 857 222 7992 (mobile)<br>
                        &gt;
                        _______________________________________________<br>
                        &gt; tdwg-content mailing list<br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><a
                          moz-do-not-send="true"
                          href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><a
                          moz-do-not-send="true"
                          href="http://lists.tdwg.org/mailman/listinfo/tdwg-content">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
                        &gt;<span class="Apple-converted-space">&nbsp;</span><br>
                        <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">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
                      </div>
                    </font><br>
                    <hr><font color="Green" face="Arial" 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.<span
                        class="Apple-converted-space">&nbsp;</span><a
                        moz-do-not-send="true"
                        href="http://www.landcareresearch.co.nz">http://www.landcareresearch.co.nz</a><br>
                    </font></div>
                </blockquote>
                <blockquote type="cite">
                  <div><span>_______________________________________________</span><br>
                    <span>tdwg-content mailing list</span><br>
                    <span><a moz-do-not-send="true"
                        href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a></span><br>
                    <span><a moz-do-not-send="true"
                        href="http://lists.tdwg.org/mailman/listinfo/tdwg-content">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a></span><br>
                  </div>
                </blockquote>
                <span>&lt;ATT00001.txt&gt;</span></div>
            </span></blockquote>
        </div>
        <br>
        <div apple-content-edited="true"> <span
            class="Apple-style-span" style="border-collapse: separate;
            color: rgb(0, 0, 0); font-family: Helvetica; font-style:
            normal; font-variant: normal; font-weight: normal;
            letter-spacing: normal; line-height: normal; orphans: 2;
            text-indent: 0px; text-transform: none; white-space: normal;
            widows: 2; word-spacing: 0px; font-size: medium;">
            <div style="word-wrap: break-word;">
              <div>
                <div style="font-size: 12px;">-------</div>
                <div style="font-size: 12px;">Arlin Stoltzfus (<a
                    moz-do-not-send="true" href="mailto:arlin@umd.edu">arlin@umd.edu</a>)</div>
                <div style="font-size: 12px;">Fellow, IBBR; Adj. Assoc.
                  Prof., UMCP; Research Biologist, NIST</div>
                <div style="font-size: 12px;">IBBR, 9600 Gudelsky Drive,
                  Rockville, MD</div>
                <div style="font-size: 12px;">tel: 240 314 6208; web: <a
                    moz-do-not-send="true" href="http://www.molevol.org">www.molevol.org</a></div>
              </div>
            </div>
          </span> </div>
        <br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
tdwg-content mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a>
<a class="moz-txt-link-freetext" href="http://lists.tdwg.org/mailman/listinfo/tdwg-content">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>