<div dir="ltr"><div style><span><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">From the clarification email that was sent out in response to the arguments re: using Individual instead of Material Sample, we indicated the utility of having distinct ID fields:</span></span></div>
<div style><span><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><br></span></span></div><span id="docs-internal-guid-11003bc6-77cd-d457-81ad-3c349a3c2c5e"><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">"...As was already pointed out, there is no restriction on specifying that an occurence is associated with more than one type, so any occurrence can have both an individualID and a materialSampleID."</span></span><br>
<div><span><span style="font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><br></span></span></div><div style>This allows us to track distinct individuals, occurrences, and material samples in the same archive. Yes, there are other ways this could be modelled but this proposal was constructed to be in line with the current standard.</div>
<div style><br></div><div style>John</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 24, 2013 at 3:37 PM, joel sachs <span dir="ltr"><<a href="mailto:jsachs@csee.umbc.edu" target="_blank">jsachs@csee.umbc.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi John,<br>
<br>
My apologies for the long delay - I wanted to finish reading the draft Darwin Core RDF guide, and recent discussion on it, before responding. I agree with the assertion made in the guide (section 2.6.1) that there's no useful way to use use Darwin Core xxxID terms in RDF. But even were this not the case, I struggle to understand the utility of the xxxID terms.<br>
<br>
MaterialSampleID, as currently proposed, serves two purposes: it provides an identifier for the thing it gets slapped onto, and it also indicates that that thing is a MaterialSample. But this second purpose - indicating that the thing is a MaterialSample - can be done either by asserting it to be<br>
rdf:type dwctype:MaterialSample<br>
or by following the convention described in <a href="http://rs.tdwg.org/dwc/terms/guides/text/index.htm" target="_blank">http://rs.tdwg.org/dwc/terms/<u></u>guides/text/index.htm</a> .<br>
<br>
So all we really need is a mechanism for giving an identifier. Is there a reason not to use dc-elements:identifier for this purpose?<br>
<br>
<br>
Best,<br>
Joel.<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
On Tue, 11 Jun 2013, John Deck wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
On Mon, Jun 10, 2013 at 2:43 PM, joel sachs <<a href="mailto:jsachs@csee.umbc.edu" target="_blank">jsachs@csee.umbc.edu</a>> wrote:<br>
Hi Everyone,<br>
<br>
I was scared to read this thread, but it turned out to be fun.<br>
Despite the excellent clarification that occurred, I still have<br>
some questions. In relation to the proposal below (to introduce<br>
the terms MaterialSample, and MaterialSampleID):<br>
<br>
1. Given that the decision was made to put MaterialSample in<br>
the "dwctype" namespace, why is the definition still "The<br>
category of information pertaining to the physical results of a<br>
sampling event …"? Shouldn't the definition be "The physical<br>
results of a sampling event ..."?<br>
(Ramona pointed this out in a message that didn't get posted to<br>
the list, but which Rich responded to [1].)<br>
<br>
<br>
yes, I agree with this...<br>
<br>
2. I believe Steve asked why there needs to be a<br>
MaterialSampleID, when none of the other dwctype terms<br>
(preservedSpecimen, etc.) have IDs. JohnD gave a sound defence<br>
of MaterialSampleID [2], but his reasoning seems to apply<br>
equally to preservedSpecimenID, DigitalStilImageID, etc. Did I<br>
miss the explanation of why MaterialSamples are so different<br>
from the other dwctype terms? Or is the idea that we will<br>
define, e.g.,<br>
<br>
dwctype:preservedSpecimen rdfs:subClassOf<br>
dwctype:MaterialSample<br>
<br>
so that preservedSpecimens will inherit MaterialSampleIDs ?<br>
<br>
<br>
MaterialSample doesn't necessarily have to be an occurrence and there could<br>
possibly be multiple occurrences in a sample (or vice versa). Thus we need<br>
the Identifier to track this (especially in the context of DwC represented<br>
as a flat-file) <br>
<br>
3. In RDF, all resources are identified by URI, and (should be)<br>
referenced by appropriate predicates (hasIndividual,<br>
hasOccurrence, etc.) So my understanding is that all the recent<br>
discussion about xxxIDs pertains only to non-RDF records. Is<br>
that correct?<br>
<br>
<br>
Not necessarily.<br>
<br>
Many thanks for the clarification already provided, and for any<br>
yet to come -<br>
Joel.<br>
<br>
1.<br>
<a href="http://lists.tdwg.org/pipermail/tdwg-content/2013-May/003008.html" target="_blank">http://lists.tdwg.org/<u></u>pipermail/tdwg-content/2013-<u></u>May/003008.html</a><br>
2.<br>
<a href="http://lists.tdwg.org/pipermail/tdwg-content/2013-May/003006.html" target="_blank">http://lists.tdwg.org/<u></u>pipermail/tdwg-content/2013-<u></u>May/003006.html</a><br>
<br>
On Sat, 25 May 2013, John Deck wrote:<br>
<br>
<br>
Steve,<br>
<br>
Thanks for your comments. Responding to both of<br>
your emails here.<br>
<br>
<br>
We’ve removed the class and now have just the<br>
MaterialSample dwctype and a materialSampleID<br>
property.<br>
dwctype:MaterialSample refines<br>
<a href="http://purl.obolibrary.org/obo/OBI_0000747" target="_blank">http://purl.obolibrary.org/<u></u>obo/OBI_0000747</a>.<br>
Also, we’ve updated<br>
materialSampleID to be a new term in the dwc/terms<br>
namespace instead of referencing the MiXS<br>
namespace. In<br>
our original proposal, we suggested using the MIxS<br>
RDF namespace for this property, however, the GSC<br>
did<br>
not make MIxS-as-RDF a standard, as decided<br>
recently at GSC15, so we’ve chosen not to use that<br>
term (by<br>
convention) and instead propose creating our own<br>
materialSampleID property in the dwc/terms<br>
namespace. (A<br>
side note: the GSC is still very much interested in<br>
MIxS as RDF and we’ll continue to maintain and<br>
implement <a href="https://code.google.com/p/mixs-as-rdf/" target="_blank">https://code.google.com/p/<u></u>mixs-as-rdf/</a> in<br>
conjunction with the MIxS developers).<br>
<br>
<br>
Modification to proposed terms:<br>
<br>
<br>
Term Name: MaterialSample<br>
<br>
Identifier:<br>
<a href="http://rs.tdwg.org/dwc/dwctype/MaterialSample" target="_blank">http://rs.tdwg.org/dwc/<u></u>dwctype/MaterialSample</a><br>
<br>
Namespace: http:/<a href="http://rs.tdwg.org/dwctype/" target="_blank">rs.tdwg.org/dwctype/</a><br>
<br>
Label: Material Sample<br>
<br>
Definition: The category of information pertaining<br>
to the physical results of a sampling (or<br>
subsampling)<br>
event. In biological collections, the material<br>
sample is typically collected, and either preserved<br>
or<br>
destructively processed.<br>
<br>
Comment: For discussion see<br>
<a href="http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary" target="_blank">http://code.google.com/p/<u></u>darwincore/wiki/<u></u>DwCTypeVocabulary</a><br>
(there will be no<br>
further documentation here until the term is<br>
ratified)<br>
<br>
Type of Term:<br>
<a href="http://www.w3.org/2000/01/rdf-schema#Class" target="_blank">http://www.w3.org/2000/01/rdf-<u></u>schema#Class</a><br>
<br>
Refines: <a href="http://purl.obolibrary.org/obo/OBI_0000747" target="_blank">http://purl.obolibrary.org/<u></u>obo/OBI_0000747</a><br>
<br>
Status: proposed<br>
<br>
Date Issued: 2013-03-28<br>
<br>
Date Modified: 2013-05-25<br>
<br>
Has Domain:<br>
<br>
Has Range:<br>
<br>
Refines:<br>
<br>
Version: MaterialSample-2013-05-25<br>
<br>
Replaces:<br>
<br>
IsReplaceBy:<br>
<br>
Class:<br>
<br>
ABCD 2.0.6: not in ABCD (someone please confirm or<br>
deny this)<br>
<br>
<br>
Term Name: materialSampleID<br>
<br>
Identifier:<br>
<a href="http://rs.tdwg.org/dwc/terms/MaterialSampleID" target="_blank">http://rs.tdwg.org/dwc/terms/<u></u>MaterialSampleID</a><br>
<br>
Namespace: <a href="http://rs.tdwg.org/dwc/terms/" target="_blank">http://rs.tdwg.org/dwc/terms/</a><br>
<br>
Label: Material Sample ID<br>
<br>
Definition: An identifier for the MaterialSample<br>
(as opposed to a particular digital record of the<br>
material<br>
sample). In the absence of a persistent global<br>
unique identifier, construct one from a combination<br>
of<br>
identifiers in the record that will most closely<br>
make the materialSampleID globally unique.<br>
<br>
Comment: For discussion see<br>
<a href="http://code.google.com/p/darwincore/wiki/MaterialSample" target="_blank">http://code.google.com/p/<u></u>darwincore/wiki/MaterialSample</a><br>
(this page will not<br>
exist until the term is ratified).<br>
<br>
Type of Term:<br>
<a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property" target="_blank">http://www.w3.org/1999/02/22-<u></u>rdf-syntax-ns#Property</a><br>
<br>
Refines: <a href="http://purl.org/dc/terms/identifier" target="_blank">http://purl.org/dc/terms/<u></u>identifier</a><br>
<br>
Status: proposed<br>
<br>
Date Issued: 2013-03-28<br>
<br>
Date Modified: 2013-05-25<br>
<br>
Has Domain:<br>
<br>
Has Range:<br>
<br>
Version: materialSampleID-2013-05-25<br>
<br>
Replaces:<br>
<br>
IsReplaceBy:<br>
<br>
Class: <a href="http://rs.tdwg.org/dwc/terms/Occurrence" target="_blank">http://rs.tdwg.org/dwc/terms/<u></u>Occurrence</a><br>
<br>
ABCD 2.0.6: not in ABCD (someone please confirm or<br>
deny this)<br>
<br>
<br>
John D. and John W.<br>
<br>
<br>
On Mon, May 20, 2013 at 7:39 PM, Steve Baskauf<br>
<<a href="mailto:steve.baskauf@vanderbilt.edu" target="_blank">steve.baskauf@vanderbilt.edu</a>> wrote:<br>
Here is the second question. The proposal<br>
proposes a new MaterialSample class<br>
<a href="http://rs.tdwg.org/dwc/terms/MaterialSample" target="_blank">http://rs.tdwg.org/dwc/terms/<u></u>MaterialSample</a><br>
which is in the "main"<br>
(dwc:=<a href="http://rs.tdwg.org/dwc/terms/" target="_blank">http://rs.tdwg.org/dwc/<u></u>terms/</a> ) namespace. I<br>
guess my question is<br>
why we need this class. I can definitely see<br>
a rational for a new class defined as part of the<br>
DwC type vocabulary (i.e.<br>
dwctype:MaterialSample). It would be used to type<br>
resources that are<br>
material samples. But the class terms in the<br>
main (dwc:) namespace are used as a convenient<br>
way to group DwC property terms that might<br>
reasonably be used with instances of that class. <br>
However, there really aren't any such terms. <br>
<br>
We already have a convention in which not<br>
every type vocabulary class term has a<br>
corresponding<br>
class term in the main (dwc:) namespace. <br>
There are dwctype:PreservedSpecimen,<br>
dwctype:LivingSpecimen,<br>
dwctype:FossilSpecimen, dwctype:HumanObservation,<br>
dwctype:MachineObservation, and<br>
dwctype:<u></u>NomenclaturalChecklist, none of which have<br>
dwc:<br>
namespace analogues. So why does<br>
MaterialSample need a dwc: namespace analog? <br>
<br>
Steve<br>
<br>
John Wieczorek wrote:<br>
Dear all,<br>
<br>
TDWG could see a lot of activity in<br>
2013 in anticipation of the meeting in Florence<br>
in October. Much of the activity is<br>
related to enabling integration across multiple<br>
parts of our domain. We have the<br>
Audubon Core under review for biodiversity-related<br>
media and an impending RDF Guide to<br>
supplement the already extant Text and XML<br>
Guides for Darwin Core.<br>
<br>
This message is to bring your attention<br>
to another integrative initiative, to<br>
introduce terms into Darwin Core that<br>
will form a nexus between Occurrences and the<br>
interesting things that happen with<br>
physical materials that result from them, such<br>
as, but not limited to, genetic<br>
sequencing. A series of meetings for a little over<br>
the past year have inspired our<br>
colleagues in the Genomics Standards Consortium<br>
(GSC) to propose to their constituency<br>
to align their terms with Darwin Core,<br>
including adopting some of the Darwin<br>
Core terms in place of their own that have<br>
the same meaning. Out of these<br>
discussions has come the realization that neither<br>
community has terms to accommodate the<br>
concept of an identifiable (objectively, not<br>
taxonomically), trackable material<br>
sample. This message constitutes such a<br>
proposal.<br>
<br>
This proposal would have no impact on<br>
those publishing purely taxonomic data. It<br>
would also have no impact on those<br>
publishing occurrence data unless they want to<br>
increase their capacity to distinguish<br>
material samples from organisms more<br>
rigorously than is now possible using<br>
only the dwc:preparations term.<br>
<br>
The initial request for new terms can<br>
be found in the Darwin Core Issue tracker as<br>
<br>
<a href="http://code.google.com/p/darwincore/issues/detail?id=167" target="_blank">http://code.google.com/p/<u></u>darwincore/issues/detail?id=<u></u>167</a>.<br>
Below I have elaborated<br>
nad formalized the request into the<br>
three distinct terms under consideration,<br>
initiating the 30 day minimum public<br>
review process to seek consensus on their<br>
inclusion in the Darwin Core standard.<br>
Your job, should you choose to accept it, is<br>
to discuss the merits or any perceived<br>
problems in the inclusion of these three<br>
terms in Darwin Core.<br>
<br>
Below I will give the proposed<br>
properties of three terms as they would appear in<br>
the Darwin Core Quick Reference Guide,<br>
though these properties would be included in<br>
the RDF of the normative form of the<br>
documentation.<br>
<br>
A new MaterialSample class: This is for<br>
the purpose of organizing properties, just<br>
as the existing classes (Occurrence,<br>
Event, Location, GeologicalContext,<br>
Identification, Taxon, etc.) do,<br>
without having any terms declare this class as<br>
their domain.<br>
<br>
Term Name: MaterialSample<br>
Identifier:<br>
<a href="http://rs.tdwg.org/dwc/terms/MaterialSample" target="_blank">http://rs.tdwg.org/dwc/terms/<u></u>MaterialSample</a><br>
Namespace: http:/<a href="http://rs.tdwg.org/dwc/terms" target="_blank">rs.tdwg.org/dwc/terms</a><br>
Label: Material Sample<br>
Definition: The category of information<br>
pertaining to the physical results of a<br>
sampling (or subsampling) event. In<br>
biological collections, the material sample is<br>
typically collected, and either<br>
preserved or destructively processed, with the<br>
intention of being representative of a<br>
greater whole.<br>
Comment: For discussion see<br>
<a href="http://code.google.com/p/darwincore/wiki/MaterialSample" target="_blank">http://code.google.com/p/<u></u>darwincore/wiki/MaterialSample</a><br>
(this page will not exist until the<br>
term is ratified).<br>
Type of Term:<br>
<a href="http://www.w3.org/2000/01/rdf-schema#Class" target="_blank">http://www.w3.org/2000/01/rdf-<u></u>schema#Class</a><br>
Refines:<br>
Status: proposed<br>
Date Issued: 2013-03-28<br>
Date Modified: 2013-04-08<br>
Has Domain:<br>
Has Range:<br>
Version: MaterialSample-2013-03-28<br>
Replaces:<br>
IsReplaceBy:<br>
Class:<br>
ABCD 2.0.6: not in ABCD (someone please<br>
confirm or deny this)<br>
<br>
A Darwin Core Type Vocabulary value for<br>
basisOfRecord is needed to represent this<br>
new class of information. Luckily, a<br>
term already exists in the Ontology for<br>
Biomedical Investigations<br>
(<a href="http://www.ontobee.org/browser/rdf.php?o=OBI&iri=http://purl.obolibrary.o" target="_blank">http://www.ontobee.org/<u></u>browser/rdf.php?o=OBI&iri=<u></u>http://purl.obolibrary.o</a><br>
rg/obo/OBI_0000747).<br>
We and the GSC both propose to reuse<br>
this class within Darwin Core as below, making<br>
it the cross-ver point between the two<br>
domains.<br>
<br>
Term Name: MaterialSample<br>
Identifier:<br>
<a href="http://rs.tdwg.org/dwc/terms/MaterialSample" target="_blank">http://rs.tdwg.org/dwc/terms/<u></u>MaterialSample</a><br>
Namespace:<br>
<a href="http://purl.obolibrary.org/obo/OBI_0000747" target="_blank">http://purl.obolibrary.org/<u></u>obo/OBI_0000747</a><br>
Label: material sample<br>
Definition: A material entity that has<br>
the material sample role<br>
Comment: For discussion see<br>
<br>
<a href="http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary" target="_blank">http://code.google.com/p/<u></u>darwincore/wiki/<u></u>DwCTypeVocabulary</a><br>
(there will be no<br>
further documentation here until the<br>
term is ratified)<br>
Type of Term:<br>
<a href="http://www.w3.org/2000/01/rdf-schema#Class" target="_blank">http://www.w3.org/2000/01/rdf-<u></u>schema#Class</a><br>
<br>
Refines:<a href="http://purl.obolibrary.org/obo/OBI_0100051" target="_blank">http://purl.<u></u>obolibrary.org/obo/OBI_0100051</a><br>
Status: recommended<br>
Date Issued: 2013-03-28<br>
Date Modified: 2013-03-28<br>
Has Domain:<br>
Has Range:<br>
Version: MaterialSample-2013-03-28<br>
Replaces:<br>
IsReplaceBy:<br>
Class:<br>
ABCD 2.0.6: not in ABCD<br>
<br>
In keeping with all other classes in<br>
Darwin Core, the Material Sample class would<br>
have a corresponding identifier<br>
property. The Genomics Standards Consortium (GSC)<br>
is in the process of proposing this<br>
term. If it is accepted, we propose to use it,<br>
and its properties would be as below,<br>
otherwise, the properties would be the same,<br>
but have the Darwin Core namespace and<br>
identifier URI.<br>
<br>
Term Name: materialSampleID<br>
Identifier:<br>
<a href="http://gensc.org/ns/mixs/materialSampleID" target="_blank">http://gensc.org/ns/mixs/<u></u>materialSampleID</a><br>
Namespace: <a href="http://gensc.org/ns/mixs" target="_blank">http://gensc.org/ns/mixs</a><br>
Label: Material Sample ID<br>
Definition: An identifier for the<br>
MaterialSample (as opposed to a particular<br>
digital record of the material sample).<br>
In the absence of a persistent global<br>
unique identifier, construct one from a<br>
combination of identifiers in the record<br>
that will most closely make the<br>
materialSampleID globally unique.<br>
Comment: For discussion see<br>
<a href="http://code.google.com/p/darwincore/wiki/MaterialSample" target="_blank">http://code.google.com/p/<u></u>darwincore/wiki/MaterialSample</a><br>
(this page will not exist until the<br>
term is ratified).<br>
Type of Term:<br>
<a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property" target="_blank">http://www.w3.org/1999/02/22-<u></u>rdf-syntax-ns#Property</a><br>
Refines:<br>
<a href="http://purl.org/dc/terms/identifier" target="_blank">http://purl.org/dc/terms/<u></u>identifier</a><br>
Status: proposed<br>
Date Issued: 2013-03-28<br>
Date Modified: 2013-04-08<br>
Has Domain:<br>
Has Range:<br>
Version: materialSampleID-2013-03-28<br>
Replaces:<br>
IsReplaceBy:<br>
Class:<br>
<a href="http://purl.obolibrary.org/obo/OBI_0000747" target="_blank">http://purl.obolibrary.org/<u></u>obo/OBI_0000747</a><br>
ABCD 2.0.6: not in ABCD (someone please<br>
confirm or deny this)<br>
<br>
<br>
--<br>
Steven J. Baskauf, Ph.D., Senior Lecturer<br>
Vanderbilt University Dept. of Biological Sciences<br>
<br>
postal mail address:<br>
PMB 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%20322-4942" value="+16153224942" target="_blank">(615) 322-4942</a><br>
If you fax, please phone or email so that I will<br>
know to look for it.<br>
<a href="http://bioimages.vanderbilt.edu" target="_blank">http://bioimages.vanderbilt.<u></u>edu</a><br>
<br>
______________________________<u></u>_________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
<a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/<u></u>listinfo/tdwg-content</a><br>
<br>
<br>
<br>
<br>
--<br>
John Deck<br>
<a href="tel:%28541%29%20321-0689" value="+15413210689" target="_blank">(541) 321-0689</a><br>
<br>
<br>
<br>
<br>
--<br>
John Deck<br>
<a href="tel:%28541%29%20321-0689" value="+15413210689" target="_blank">(541) 321-0689</a><br>
<br>
</blockquote>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>John Deck<br>(541) 321-0689<br>
</div></div>