<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:0in;
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.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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><div class=WordSection1><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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Aloha,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rich<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></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"'> tdwg-content-bounces@lists.tdwg.org [mailto:tdwg-content-bounces@lists.tdwg.org] <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<br><b>Cc:</b> TDWG Content Mailing List; Ramona Walls<br><b>Subject:</b> Re: [tdwg-content] Darwin Core Proposal - term content recommendations to comments<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Does anyone have similar concerns about iao:example?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></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:<o:p></o:p></p><p class=MsoNormal>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>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 class=hoenzb>-Paul</span><br><span class=hoenzb>--</span><br><span class=hoenzb>Paul J. Morris</span><br><span class=hoenzb>Biodiversity Informatics Manager</span><br><span class=hoenzb>Harvard University Herbaria/Museum of Comparative Zoölogy</span><br><span class=hoenzb><a href="mailto:mole@morris.net">mole@morris.net</a> AA3SD PGP public key available</span></span><o:p></o:p></p><div><div><p class=MsoNormal>_______________________________________________<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><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>