<div><div><div class="gmail_quote">On Mon, Jul 11, 2011 at 9:45 PM, Steven J. Baskauf <span dir="ltr"><<a href="mailto:steve.baskauf@vanderbilt.edu" target="_blank" title="[GMCP] Compose a new mail to steve.baskauf@vanderbilt.edu" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=steve.baskauf@vanderbilt.edu','Compose new message','width=640,height=480');return false" rel="noreferrer">steve.baskauf@vanderbilt.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Given the uses John suggests (non-RDF data sharing, providing a<br>
controlled value for basisOfRecord), I think that adding the terms<br>
StillImage, Sound, and MovingImage to the Darwin Core type vocabulary is<br>
a reasonable course of action. For more complex descriptions (i.e.<br>
RDF), additional information can be provided in the metadata to indicate<br>
whether the resource is available in digital form.<br>
<br>
Although these three terms are in the DCMI type vocabulary, the DCMI<br>
type vocabulary does not provide the controlled values for<br>
basisOfRecord, so they need to be in the DwC type vocabulary.<br></blockquote><div><br></div><div>I have added three new issues (115-117) in the Darwin Core Issue Tracker (<a href="http://code.google.com/p/darwincore/issues/list">http://code.google.com/p/darwincore/issues/list</a>) to make sure these changes get committed, if there are no objections by the end of the comment period (3 August 2011). </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
While we are on the subject of the DwC type vocabulary, is it also<br>
possible to fix the subclass issues (see<br>
<a href="http://code.google.com/p/darwincore/source/browse/trunk/rdf/dwctype.rdf" target="_blank">http://code.google.com/p/darwincore/source/browse/trunk/rdf/dwctype.rdf</a>), i.e.<br>
saying that an Occurrence is a subclass of an Event, and that a<br>
PreservedSpecimen is a subclass of an Occurrence? Simplest solution<br>
there is to not make any of the DwC types be subclasses of any other types.<br></blockquote><div><br></div><div>Yes, the subtyping can be removed. That will be more flexible going forward than committing to an implied ontology that hasn't been fully developed.<div>
<br><div>For those new to this topic and interested in its history, discussions began in late October 2010 on tdwg-content with the post archived at <span class="Apple-style-span" style="font-family: monospace; font-size: 12px; white-space: pre-wrap; background-color: rgb(255, 255, 255); "><a href="http://lists.tdwg.org/pipermail/tdwg-content/2010-October/001778.html" rel="nofollow" style="color: rgb(0, 0, 204); ">http://lists.tdwg.org/pipermail/tdwg-content/2010-October/001778.html</a>.</span></div>
<div><br></div><div>I have entered 6 issues (109-114) in the Darwin Core Issue tracker (<a href="http://code.google.com/p/darwincore/issues/list">http://code.google.com/p/darwincore/issues/list</a>) to make sure these changes get committed, unless any objections are expressed by the end of the comment period (3 August 2011).</div>
<div> </div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Steve<br>
<div><div></div><div><br>
On 7/4/2011 4:35 PM, John Wieczorek wrote:<br>
> Darwin Core Issue 68: <a href="http://goo.gl/Q7TRn" target="_blank">http://goo.gl/Q7TRn</a><br>
><br>
> This term has undergone extensive public commentary since January 2010<br>
> when it was first proposed. I will do my best to summarize the<br>
> thinking on these issues, but please see the full corpus of<br>
> discussions on tdwg-content to see the full history.<br>
><br>
> It has been suggested that DigitalStillImage is not necessary as a<br>
> Darwin Core Type vocabulary term (one of the controlled vocabulary<br>
> terms for basisOfRecord) for at least two reasons:<br>
><br>
> 1) Dublic Core comments on StillImage<br>
> (<a href="http://dublincore.org/documents/dcmi-type-vocabulary/" target="_blank">http://dublincore.org/documents/dcmi-type-vocabulary/</a>) as: "Note that<br>
> Image may include both electronic and physical representations."<br>
><br>
> 2) The basisOfRecord term has no real purpose and without it, there<br>
> was no need for DigitalStillImage as one of its controlled values.<br>
><br>
> The context for the second statement was the use of Darwin Core in<br>
> RDF. The basisOfRecord term is essential in data sharing mechanisms<br>
> such as in Simple Darwin Core text files or Darwin Core Archives where<br>
> there is no other way to express what is the fundamental concept for a<br>
> record.<br>
><br>
> The impetus for proposing DigitalStillImage was to allow the<br>
> basisOfRecord to show that the evidence for an Occurrence was based on<br>
> a digital image (similar to a PreservedSpecimen being evidence). This<br>
> purpose still has merit.<br>
><br>
> Discussions on DigitalStillImage touched on many other issues related<br>
> to ontology and missing or inferred Classes in the Darwin Core. To<br>
> achieve the original goal behind DigitalStillImage for RDF is more<br>
> complicated and involves the idea of a Class to represent a concept<br>
> that could be described as "Evidence". I will create a separate thread<br>
> for the continuation of that discussion, reserving this thread for the<br>
> closure of the issue of having no way currently to express that a<br>
> digital image is the basis for a Darwin Core resource.<br>
><br>
> To achieve the original goal for the case of non-RDF data sharing<br>
> mechanisms, I propose that StillImage be added to the list of<br>
> recommendations for the Darwin Core Type Vocabulary, along with<br>
> MovingImage and Sound. Doing so will create no backward<br>
> incompatibilities in the Darwin Core.<br>
</div></div>> _______________________________________________<br>
> tdwg-content mailing list<br>
> <a href="mailto:tdwg-content@lists.tdwg.org" title="[GMCP] Compose a new mail to tdwg-content@lists.tdwg.org" rel="noreferrer" target="_blank" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=tdwg-content@lists.tdwg.org','Compose new message','width=640,height=480');return false">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>
<br>
--<br>
Steven J. Baskauf, Ph.D., Senior Lecturer<br>
Vanderbilt University Dept. of Biological Sciences<br>
<br>
postal mail address:<br>
VU Station B 351634<br>
Nashville, TN 37235-1634, U.S.A.<br>
<br>
delivery address:<br>
2125 Stevenson Center<br>
1161 21st Ave., S.<br>
Nashville, TN 37235<br>
<br>
office: 2128 Stevenson Center<br>
phone: <a href="tel:%28615%29%20343-4582" value="+16153434582" target="_blank">(615) 343-4582</a>, fax: <a href="tel:%28615%29%20343-6707" value="+16153436707" target="_blank">(615) 343-6707</a><br>
<a href="http://bioimages.vanderbilt.edu" target="_blank">http://bioimages.vanderbilt.edu</a><br>
<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org" title="[GMCP] Compose a new mail to tdwg-content@lists.tdwg.org" rel="noreferrer" target="_blank" onclick="window.open('https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=tdwg-content@lists.tdwg.org','Compose new message','width=640,height=480');return false">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>
</blockquote></div><br>
</div></div>