<div dir="ltr"><div><div>As far as I know, iao:example of usage also allows both literals and URLs as the range. However, I fail to see a serious problem with that, and to me, the benefits of re-using existing properties far outway the benefits I could see from having a separate set of properties for literals. Also, I don't know anyone who reasons over annotations properties, although I am sure there are those who do.<br><br></div>In response to Paul Morris's comment, simply using iao:example of usage does not import all of IAO, and therefore does not include any of the "baggage" of using IAO.<br><br></div>Ramona<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">------------------------------------------------------<br>Ramona L. Walls, Ph.D.<br>Scientific Analyst, The iPlant Collaborative, University of Arizona<br>Research Associate, Bio5 Institute, University of Arizona<br>Laboratory Research Associate, New York Botanical Garden</div></div></div>
<br><div class="gmail_quote">On Thu, Feb 5, 2015 at 10:48 AM, Richard Pyle <span dir="ltr"><<a href="mailto:deepreef@bishopmuseum.org" target="_blank">deepreef@bishopmuseum.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Like others, I like the idea in principle, but I’m not well-versed in the implications of alternate approaches to implementation to weigh in on that. Whatever technical solution is adopted, I would like to hope that it supports the representation of more than a single example; as sometimes it is useful to show alternate forms of acceptable content.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Aloha,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Rich<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><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""> <a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a> [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>] <b>On Behalf Of </b>John Wieczorek<br><b>Sent:</b> Thursday, February 05, 2015 7:22 AM<br><b>To:</b> Paul J. Morris<span class=""><br><b>Cc:</b> TDWG Content Mailing List; Ramona Walls<br></span><b>Subject:</b> Re: [tdwg-content] Darwin Core Proposal - term content recommendations to comments<u></u><u></u></span></p></div></div><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">Does anyone have similar concerns about iao:example?<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">On Thu, Feb 5, 2015 at 2:09 PM, Paul J. Morris <<a href="mailto:mole@morris.net" target="_blank">mole@morris.net</a>> wrote:<u></u><u></u></p><p class="MsoNormal">On Thu, 5 Feb 2015 11:17:58 -0500<br>Bob Morris <<a href="mailto:morris.bob@gmail.com" target="_blank">morris.bob@gmail.com</a>> wrote:<br>> But skos:note and its subproperties (including skos:example) can take<br>> literals or references [1]. To me, that weighs more than the<br>> baggage of minting two new terms.<br><br>Also, SKOS, unless care is taken to import the Owl-DL version, brings<br>you into Owl-Full, with undesirable consequences for those who wish to<br>do reasoning. In early versions of dwcFP, we did include SKOS terms,<br>but removed them because of the consequences for reasoning.<br><br>SKOS has some nice terms, reuse is a nice idea, but it comes with<br>significant knowledge engineering consequences.<br><span style="color:#888888"><br><span>-Paul</span><br><span>--</span><br><span>Paul J. Morris</span><br><span>Biodiversity Informatics Manager</span><br><span>Harvard University Herbaria/Museum of Comparative Zoölogy</span><br><span><a href="mailto:mole@morris.net" target="_blank">mole@morris.net</a> AA3SD PGP public key available</span></span><u></u><u></u></p><div><div><p class="MsoNormal">_______________________________________________<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><u></u><u></u></p></div></div></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div></div></blockquote></div><br></div>