<div class="gmail_quote">On Tue, Aug 24, 2010 at 9:20 AM, Mark Wilden <span dir="ltr"><<a href="mailto:mark@mwilden.com">mark@mwilden.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Aug 24, 2010 at 7:28 AM, John Wieczorek <<a href="mailto:tuco@berkeley.edu">tuco@berkeley.edu</a>> wrote:<br>
<br>
> Recommended best practice is to use a controlled vocabulary.<br>
<br>
</div><div class="im">This sounds like an incorrect usage of the term "best practice," to<br>
me. It can't be a "best practice" to do something that is impossible,<br>
and if a controlled vocabulary doesn't exist... As you indicate, this<br>
has a requirement that hasn't yet been met.<br></div></blockquote><div><br></div><div>It is not a requirement, it is a recommendation. It is not impossible, just make a vocabulary. Well, hopefully with some community buy-in and open access. GBIF's vocabulary registry (<a href="http://vocabularies.gbif.org/">http://vocabularies.gbif.org/</a>) comes to mind as a solution.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
</div><div><div></div><div class="h5">///ark<br>
Web Applications Developer<br>
Center for Applied Biodiversity Informatics<br>
California Academy of Sciences<br>
_______________________________________________<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>