<div dir="ltr">Does anyone have similar concerns about iao:example?</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 5, 2015 at 2:09 PM, Paul J. Morris <span dir="ltr"><<a href="mailto:mole@morris.net" target="_blank">mole@morris.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, 5 Feb 2015 11:17:58 -0500<br>
Bob Morris <<a href="mailto:morris.bob@gmail.com">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>
</span>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 class="HOEnZb"><font color="#888888"><br>
-Paul<br>
--<br>
Paul J. Morris<br>
Biodiversity Informatics Manager<br>
Harvard University Herbaria/Museum of Comparative Zoölogy<br>
<a href="mailto:mole@morris.net">mole@morris.net</a> AA3SD PGP public key available<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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></div>