<div dir="ltr">I concur with Peter, and as I am focused on implementation, I need one place to go to get the definitions and examples. It may even be possible to integrate AppleCore into a resource like <a href="http://rs.gbif.org/core/dwc_occurrence.xml" target="_blank" style="font-family:arial,sans-serif;font-size:12.727272033691406px">http://rs.gbif.org/core/dwc_occurrence.xml</a><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"> with "tags" for botanical implementation, which avoids having to reference yet another site and may lead to better adoption...</span><div>
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">Best, JAmes</span></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br>
</span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 10, 2013 at 8:33 AM, DESMET, Peter <span dir="ltr"><<a href="mailto:Peter.DESMET@inbo.be" target="_blank">Peter.DESMET@inbo.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">John, +1 from me for the changes you suggest.<br>
<br>
If this does not become part of the term definitions (and I understand the arguments made by Joel and Hilmar), I think users of Simple Darwin Core would greatly benefit from a separate list of terms WITH those recommendations and examples. I always go to <a href="http://rs.tdwg.org/dwc/terms/index.htm" target="_blank">http://rs.tdwg.org/dwc/terms/index.htm</a> as a source for guidance, but a more specific list might be in order, for example <a href="http://rs.gbif.org/core/dwc_occurrence.xml" target="_blank">http://rs.gbif.org/core/dwc_occurrence.xml</a> (ideally maintained/endorsed by TDWG).<br>
<br>
Cheers,<br>
<br>
Peter<br>
<br>
<br>
<br>
________________________________________<br>
Van: <a href="mailto:tdwg-content-bounces@lists.tdwg.org">tdwg-content-bounces@lists.tdwg.org</a> [<a href="mailto:tdwg-content-bounces@lists.tdwg.org">tdwg-content-bounces@lists.tdwg.org</a>] namens joel sachs [<a href="mailto:jsachs@csee.umbc.edu">jsachs@csee.umbc.edu</a>]<br>
Verzonden: dinsdag 8 oktober 2013 19:19<br>
Aan: John Wieczorek<br>
CC: TDWG Content Mailing List<br>
Onderwerp: Re: [tdwg-content] Delimiters for Darwin Core list-type terms<br>
<div><div class="h5"><br>
On Tue, 8 Oct 2013, John Wieczorek wrote:<br>
<br>
> Dear all,<br>
><br>
> There has been some momentum toward solutions to the problems as<br>
> originally presented. I would like to summarize what I perceive as the<br>
> middle ground between them and ask anyone with dissenting opinions to<br>
> please express them in reply.<br>
><br>
> a) Make all of the changes in the term definitions rather than in type<br>
> 3 documentation.<br>
><br>
> b) Retain unchanged the definitions of terms on the list I gave that<br>
> are already described without reference to being a list<br>
> (informationWitheld, dataGeneralizations, vernacularName).<br>
><br>
> c) For terms that are designed to contain lists (dynamicProperties,<br>
> recordedBy, preparations, otherCatalogNumbers,<br>
> previousIdentifications, associatedMedia, associatedReferences,<br>
> associatedOccurrences, associatedSequences, associatedTaxa,<br>
> higherGeography, georeferencedBy, georeferenceSources, identifiedBy,<br>
> identificationReferences, typeStatus, higherClassification,<br>
> measurementDeterminedBy), recommend in the term definition that the<br>
> list be delimited with a vertical bar '|' and no white space.<br>
<br>
John,<br>
<br>
I didn't see any objection to the suggestion made by Tim that the<br>
recommendation to use a concatenated list be moved from the term<br>
definitions to the Text Guide. Did I miss it?<br>
<br>
Thanks,<br>
Joel.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
> Please<br>
> note that I missed some terms from this category in my original list.<br>
><br>
> Here is an example of what such a definition might look like:<br>
><br>
> higherClassification: "A list (concatenated and separated) of taxa<br>
> names terminating at the rank immediately superior to the taxon<br>
> referenced in the taxon record. Recommended best practice is to order<br>
> the list starting with the highest rank and separate the names for<br>
> each rank with a vertical bar ('|')."<br>
><br>
> d) For terms in the list in c), above, include one example with a<br>
> single value (where appropriate) and one example with a list showing<br>
> the concatenation with the delimiter.<br>
><br>
> Here is an example of what such a comment might look like:<br>
><br>
> georeferencedBy: "Example: "Brad Millen (ROM)", "Kristina Yamamoto<br>
> (MVZ)|Janet Fang (MVZ)".<br>
><br>
> e) For higherGeography, recommend an order for the terms in the list<br>
> from least specific to most specific.<br>
><br>
> f) For associatedTaxa, change the comment to use a format equivalent<br>
> to that for dynamicProperties.<br>
><br>
> g) Defer other concerns with specific terms. If these persists beyond<br>
> the current conversation, I encourage you to submit a Term Definition<br>
> issue in the issue tracker<br>
> (<a href="https://code.google.com/p/darwincore/issues/list" target="_blank">https://code.google.com/p/darwincore/issues/list</a>).<br>
><br>
> Cheers,<br>
><br>
> John<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>
><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>* * * * * * * * * * * * * D I S C L A I M E R * * * * * * * * * * * * *<br>
Dit bericht en eventuele bijlagen geven enkel de visie van de schrijver weer en binden het INBO onder geen enkel beding, zolang dit bericht niet bevestigd is door een geldig ondertekend document.<br>
The views expressed in this message and any annex are purely those of the writer and may not be regarded as stating an official position of INBO, as long as the message is not confirmed by a duly signed document.<br>
<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>