<br><br><div class="gmail_quote">On Mon, Oct 11, 2010 at 6:38 AM, "Markus Döring (GBIF)" <span dir="ltr"><<a href="mailto:mdoering@gbif.org">mdoering@gbif.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I see. From what I understand (please correct me if Im wrong, John) dwc:recordedBy is rather the primary observer in the field than the person keying in the dwc metadata record about it. </blockquote><div><br></div><div>Yes. DwC doesn't have a term for the person creating the record - recordedBy is meant to be the collector(s) or observer(s) in the field who made the determination that a species occurred there.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">If that's the missing bit I would use dcterm:creator instead: <a href="http://dublincore.org/documents/dcmi-terms/#elements-creator" target="_blank">http://dublincore.org/documents/dcmi-terms/#elements-creator</a> and we could think about including this into the official record level terms in darwin core.<br>
<br>
dc:source is another record level term I personally include very often although not explicitly listed in the dwc guide. For species checklists I often want to include a link back to the often richer source webpage.<br></blockquote>
<div><br></div><div>dcterms:source seems like a reasonable addition to the record-level terms borrowed from Dublin Core. There is no evidence that we ever attempted to include it, which means at least that we didn't have a reason to reject it.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
Markus<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
On Oct 11, 2010, at 14:53, joel sachs wrote:<br>
<br>
> Markus,<br>
><br>
> The issue is that the observer and the the recorder are not always the same person. A student or a team member might report the observation to a teacher/team leader, who then creates the record. As you and Tim point out, the definition of recordedBy does allow us to use the term for both observers and record creators, but then we lose the distinction between the two.<br>
><br>
> Joel.<br>
><br>
><br>
><br>
><br>
> On Mon, 11 Oct 2010, "Markus Döring (GBIF)" wrote:<br>
><br>
>> Joel,<br>
>> thanks for this nice summary. Darwin Core definitely needs far more examples to illustrate its use. We should probably provide various examples for all the different use cases we already know dwc can be used for.<br>
>><br>
>> Darwin Core has a recordedBy term. Did that not fit your obs:observedBy property and if not what exactly is the difference?<br>
>> See <a href="http://rs.tdwg.org/dwc/terms/index.htm#recordedBy" target="_blank">http://rs.tdwg.org/dwc/terms/index.htm#recordedBy</a><br>
>><br>
>> Thanks,<br>
>> Markus<br>
>><br>
>><br>
>> On Oct 11, 2010, at 13:46, joel sachs wrote:<br>
>><br>
>>> One of the goals of the recent bioblitz was to think about the suitability<br>
>>> and appropriatness of TDWG standards for citizen science. Robert Stevenson<br>
>>> has volunteered to take the lead on preparing a technobioblitz lessons<br>
>>> learned document, and though the scope of this document is not yet<br>
>>> determined, I think the audience will include bioblitz organizers,<br>
>>> software developers, and TDWG as a whole. I hope no one is shy about<br>
>>> sharing lessons they think they learned, or suggestions that they have. We<br>
>>> can use the bioblitz google group for this discussion, and copy in<br>
>>> tdwg-content when our discussion is standards-specific.<br>
>>><br>
>>> Here are some of my immediate observations:<br>
>>><br>
>>> 1. Darwin Core is almost exactly right for citizen science. However, there<br>
>>> is a desperate need for examples and templates of its use. To illustrate<br>
>>> this need: one of the developers spoke of the design choice between "a<br>
>>> simple csv file and a Darwin Core record". But a simple csv file is a<br>
>>> legitimate representation of Darwin Core! To be fair to the developer,<br>
>>> such a sentence might not have struck me as absurd a year ago, before<br>
>>> Remsen said "let's use DwC for the bioblitz".<br>
>>><br>
>>> We provided a couple of example DwC records (text and rdf) in the bioblitz<br>
>>> data profile [1]. I think the lessons learned document should include an<br>
>>> on-line catalog of cut-and-pasteable examples covering a variety of use<br>
>>> cases, together with a dead simple desciption of DwC, something like<br>
>>> "Darwin Core is a collection of terms, together with definitions."<br>
>>><br>
>>> Here are areas where we augemented or diverged from DwC in the bioblitz:<br>
>>><br>
>>> i. We added obs:observedBy [2], since there is no equivalent property in<br>
>>> DwC, and it's important in Citizen Science (though often not available).<br>
>>><br>
>>> ii. We used geo:lat and geo:long [3] instead of DwC terms for latitude and<br>
>>> longitude. The geo namespace is a well used and supported standard, and<br>
>>> records with geo coordinates are automatically mapped by several<br>
>>> applications. Since everyone was using GPS to retrieve their coordinates,<br>
>>> we were able to assume WGS-84 as the datum.<br>
>>><br>
>>> If someone had used another Datum, say XYZ, we would have added columns to<br>
>>> the Fusion table so that they could have expressed their coordiantes in<br>
>>> DwC, as, e.g.:<br>
>>> DwC:decimalLatitude=41.5<br>
>>> DwC:decimalLongitude=-70.7<br>
>>> DwC:geodeticDatum=XYZ<br>
>>><br>
>>> (I would argue that it should be kosher DwC to express the above as simply<br>
>>> XYZ:lat and XYZ:long. DwC already incorporates terms from other<br>
>>> namespaces, such as Dublin Core, so there is precedent for this.<br>
>>><br>
>>> 2. DwC:scientificName might be more user friendly than taxonomy:binomial<br>
>>> and the other taxonomy machine tags EOL uses for flickr images. If<br>
>>> DwC:scientificName isn't self-explanatory enough, a user can look it up,<br>
>>> and see that any scientific name is acceptable, at any taxonomic rank, or<br>
>>> not having any rank. And once we have a scientific name, higher ranks can<br>
>>> be inferred.<br>
>>><br>
>>> 3. Catalogue of Life was an important part of the workflow, but we<br>
>>> had some problems with it. Future bioblitzes might consider using<br>
>>> something like a CoL fork, as recently described by Rod Page [4].<br>
>>><br>
>>> 4. We didn't include "basisOfRecord" in the original data profile, and so<br>
>>> it wasn't a column in the Fusion Table [5]. But when a transcriber felt it<br>
>>> was necessary to include in order to capture data in a particular field<br>
>>> sheet, she just added the column to the table. This flexibility of schema<br>
>>> is important, and is in harmony with the semantic web.<br>
>>><br>
>>> 5. There seemed to be enthusiasm for another field event at next year's<br>
>>> TDWG. This could be an opportunity to gather other types of data (eg.<br>
>>> character data) and thereby<br>
>>> i) expose meeting particpants to another set of everyday problems from the<br>
>>> world of biodiversity workflows, and ii) try other TDWG technology on<br>
>>> for size, e.g. the observation exchange format, annotation framework, etc.<br>
>>><br>
>>><br>
>>> Happy Thanksgiving to all in Canada -<br>
>>> Joel.<br>
>>> ----<br>
>>><br>
>>><br>
>>> 1. <a href="http://groups.google.com/group/tdwg-bioblitz/web/tdwg-bioblitz-profile-v1-1" target="_blank">http://groups.google.com/group/tdwg-bioblitz/web/tdwg-bioblitz-profile-v1-1</a><br>
>>> 2. Slightly bastardizing our old observation ontology -<br>
>>> <a href="http://spire.umbc.edu/ontologies/Observation.owl" target="_blank">http://spire.umbc.edu/ontologies/Observation.owl</a><br>
>>> 3. <a href="http://www.w3.org/2003/01/geo/" target="_blank">http://www.w3.org/2003/01/geo/</a><br>
>>> 4. <a href="http://iphylo.blogspot.com/2010/10/replicating-and-forking-data-in-2010.html" target="_blank">http://iphylo.blogspot.com/2010/10/replicating-and-forking-data-in-2010.html</a><br>
>>> 5. <a href="http://tables.googlelabs.com/DataSource?dsrcid=248798" target="_blank">http://tables.googlelabs.com/DataSource?dsrcid=248798</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>
> _______________________________________________<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>
</div></div></blockquote></div><br>