Hi Steve,<div><br></div><div>It is not if there are not examples of things that seem to work in this space, it is that those alternatives that could be incorporated into the DarwinCore are largely ignored unless they they come from the "right people". </div>
<div><br></div><div>How these "right people" are defined is not quite clear to me but what seems strange is that many of the issues that are being rehashed over and over again I have already live working examples of. </div>
<div><br></div><div>If there are any flaws. or features lacking. is because I have spent far too much time, as you have, trying to get people on the list to some of the problems with the system they have proposed.</div><div>
<br></div><div>I believe that you are right and that we need to represent individuals in the RDF version, but I have implemented them in a slightly different way.</div>
<div><br></div><div><<a href="http://lod.taxonconcept.org/ses/iuCXz#Species" target="_blank">http://lod.taxonconcept.org/ses/iuCXz#Species</a>> txn:speciesConceptHasSpeciesIndividualTag <<a href="http://lod.taxonconcept.org/ses/iuCXz#Individual" target="_blank">http://lod.taxonconcept.org/ses/iuCXz#Individual</a>></div>
<div><br></div><div>That this creates is a usable type for an "individual of that species concept." It is of type <b>txn:SpeciesIndividualTag</b></div><div><b><br></b></div><div><b><span style="font-weight:normal">Now you can easily query for all the "individuals" or all the "individuals that are of a particular species concept".</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">We could be using the species concept URI's that I have setup but instead we see a perfect example of the folly of LSID's.</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">Those listed above do not resolve to anything that tells me what they mean. </span></b></div><div><b><span style="font-weight:normal"><br>
</span></b></div><div><b><span style="font-weight:normal">(I tried, not because I wanted show the folly of LSID's but to see if the LSID was for something that I had a URI for.</span></b></div><div><b><span style="font-weight:normal"><br>
</span></b></div><div><b><span style="font-weight:normal">A URI that could be used in the interim.)</span></b></div><div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">What I got was an LSID that despite being resolved through a proxy, returned nothing.</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">I can always add the zoobank LSID to the metadata to the description for that concept which would allow some tracking and use of LSID's.</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">Frankly, I don't know what is really going on, but there is something very strange about how this entire process is operating.</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">Some of these issue are better handled by people who already understand RDF, but instead are being rehashed here.</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">Why do I keep seeing this "pull" to create a specific subsection of the semantic web or even informatics rather that benefit from all the related work happening a few email lists away?</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">One thing that you might be missing, is that in RDF something can have many types so you can have something that is both a depiction of a speciesconcept and a depiction of an individual.</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal"><b><span style="font-weight: normal; ">Just like you had can have a depiction of a "Firehouse" that is also a depiction of the "West Washington Firehouse" </span></b></span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">I have thought that there may a need to be some additional "tag" like identifiers like Image or Media, which has Image as a subclass.</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">Also since the dwc is not really "live" and and working like it should, we can't really test it in the ways it need to be tested.</span></b></div>
<div><b><span style="font-weight:normal"><br></span></b></div><div>In summary, I feel your pain.</div><div><b><span style="font-weight:normal"><br>
</span></b></div><div><b><span style="font-weight:normal">Respectfully,</span></b></div><div><b><span style="font-weight:normal"><br></span></b></div><div><b><span style="font-weight:normal">- Pete<br></span></b><br>
<div class="gmail_quote">On Wed, Oct 13, 2010 at 9:07 PM, Steve Baskauf <span dir="ltr"><<a href="mailto:steve.baskauf@vanderbilt.edu" target="_blank">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">
<div bgcolor="#ffffff" text="#000000">
I was just ready to leave work when I wrote this and since then I'm
feeling like I should clarify just what I mean by "wrong" ways of using
RDF. I recognize that TDWG encourages flexibility in the ways that
standards such as DwC are used. As such, it doesn't usually define
"right" and "wrong" ways of using the standards. What I mean by
calling some uses "wrong" is not intended to discourage the creative
use of DwC terms in RDF. What I mean is that one must be careful to
make sure that RDF statements mean what is intended. Here is an
example. The Dublin Core term dcterms:language means "the language of
the resource". On multiple occasions, I've seen this term used in RDF
as a property of a resource whose metadata is written in a certain
language. This is "wrong" because the subject of the statement is the
resource itself, not the resource's metadata. The need for this kind
of clarity is apparent in the case of media. For example, if we are
providing metadata in English that describes a nature film which has
audio in German, the correct statement is that [film] dcterms:language
"de", NOT [film] dcterms:language "en". This problem is handled
appropriately in the MRTG schema by creating the (required) term
mrtg:metadataLanguage. The correct statement would be [film]
mrtg:metadataLanguage "en" . (I'm using "[film]" in lieu of a URI
identifier for the film.) If, however, we were writing RDF to describe
the metadata itself rather than the film, then it would be appropriate
to say [film's metadata] dcterms:language "en" . In straight XML, we
might get away with semantic sloppiness if the senders and receivers of
the XML "understand" what the intended subject is of the term
dcterms:language. But in RDF, we have to assume that the receiver of
the RDF is a "stupid" computer which only infers exactly what is said
and not what we MEANT to say. <br>
<br>
I believe that this is a very important point that all parties need to
keep in mind before we happily march off creating RDF templates for the
general public to use. In particular, I have some serious problems
with the way that people are associating properties with instances of
the dwc:Occurrence class. I believe that these "wrong" ways originate
with the historical roots of Darwin Core as a means to describe
specimens. I will illustrate what I mean. In many cases, a specimen
is created by killing an organism and gluing it to a piece of paper (if
it's a plant) or putting it in a jar (if it's an animal). It is
natural to ask the question "what kind of species is the specimen?".
We can look at the specimen and make a statement like [specimen]
dwc:scientificName "Drosophila melanogaster" and it pretty much makes
sense. However, in the new Darwin Core standard, we have a broader
category of "things" (a.k.a. resources) that we call Occurrences which
include specimens but which also includes observations and probably all
kinds of things like images, DNA samples, and a whole lot of other
things. If we try to apply the same kind of statement to other kinds
of Occurrences besides specimens we immediately run into problems. If
we say that [digital image] dwc:scientificName "Drosophila
melanogaster" we are making a nonsensical statement. The digital image
can have properties like its photographer, its format, its pixel
dimensions, etc. but the image itself does not have a scientific name.
The scientific name is a property of the thing that was photographed.
It makes even less sense if we are talking about observations. An
observation is a situation where somebody observes an organism. The
observation can have properties like the observer, the location, etc.
However, if we say [observation] dwc:scientificName "Drosophila
melanogaster" we are saying that that act of observing has a scientific
name. That is an incorrect statement. So the general statement
[Occurrence] dwc:scientificName "Drosophila melanogaster" does not make
sense when applied to all possible types of Occurrences. Rather, the
organism that we are observing is the thing that has a scientific
name. <br>
<br>
In all of the examples above, the correct statement is [individual
organism] dwc:scientificName "Drosophila melanogaster". The specimen
is an occurrence of the individual organism. The image is an
occurrence of the individual organism. The observation is an
occurrence of the individual organism. These statements may seem odd
because we are used to thinking of an Occurrence being an occurrence of
the "species" but it's not really. The image is not an image of the
Drosophila species concept nor is it an image of the string "Drosophila
melanogaster". The image is an image of an individual fruit fly. The
individual fruit fly is a representative of the taxon, the image and
the observation are not. <br>
<br>
This point becomes more clear if we look at a situation where several
types of occurrence records are collected from the same individual.
Let's say that we capture a bird, photograph it, collect a feather from
it, collect a DNA sample and band it and let it go. Later somebody
sees the band and reports that as an observation. How do we connect
all of these things? Do we create an identifier for the specimen (the
feather) and then say that the image and the DNA sample came from it?
That would be wrong. We could take an image of the feather, but that
would be a different thing from an image of the bird. We didn't get
the DNA sample from the feather, we got it via a blood sample from the
bird. The band observation is not an observation of the feather, or
the image or the DNA sample. It's an observation of the bird which was
never any kind of specimen living or dead. The bird is an individual
organism and that's what we need to call it. Right now we don't have
anything in Darwin Core that can be used to rdfs:type the bird, which
is why I proposed Individual as a Darwin Core class. <br>
<br>
I could say these things more clearly in RDF, but since because many
members of the audience of this message aren't familiar with RDF/XML
they would probably zone out and the point would be lost. The point is
that we need to have identifiable classes of "resources" (the technical
name for "things" like physical artifacts, concepts, and electronic
representations) for all of the things that that we need to describe
and inter-relate in the Darwin Core world. Right now, we are missing
one of the important pieces that we need, which is a class for the
Individual. If we are satisfied with creating an RDF model that only
works for specimens and one-time observations, then we probably don't
need Individual as a Darwin Core class. On the other hand, if TDWG and
GBIF are really serious about creating a system (Darwin Core and RDF
based on it) that can handle other types of Occurrences like multiple
images of live organisms, observations of the same organism over time,
and multiple types of Occurrences collected from the same organism,
then this capability should be built into the system from the start.
When I got back from the TDWG meeting, I was all excited about trying
to use Darwin Core Archives with my live plant image collection.
However, it quickly became evident that it could not work because
Occurrences were at the center of the diagram rather than Individuals.
So unless something changes, we are already embarking on the process of
locking out these other Occurrence types.<br>
<br>
I hate to sound like a broken record (do we have those any more?), but
read my paper on this subject. It explains the rationale better than
this email, has nice diagrams, and gives RDF examples to illustrate
everything (<a href="https://journals.ku.edu/index.php/jbi/article/view/3664" target="_blank">https://journals.ku.edu/index.php/jbi/article/view/3664</a>).
If somebody has a better idea of how to develop an internally
consistent system that can handle the problems I've raised here that
DOESN'T involve Individuals (i.e. other "right"[=semantically accurate]
ways to express properties and relationships among Identifications,
Taxa, diverse types of Occurrences, etc.) I'd like to hear what it is.
Or perhaps as Stan has suggested, there needs to be a task group that
can hash out alternative views. But let's have the discussion before
we post models and suggest people use them.<br>
<br>
Steve<br>
<br>
Steve Baskauf wrote:
<blockquote type="cite">
Stan,<br>
Thanks for the clarification. My concern here is that standard or not,
if examples are posted on the Google Darwin Code site, they will have
an implied "stamp of approval" and will be used by others as a template
(despite that site being labeled as "for discussion and development"
not everyone can post to it and that implies some authority). In the
case of straight XML, that isn't really that big of an issue. XML can
mean whatever one wants as long as there is an agreement between the
sender and the receiver (perhaps in the form of a formal XML schema) as
to what the elements represent. I believe that RDF is a different
beast. When one exposes RDF, the receiver is unknown. Therefore, the
RDF has to actually "mean" something to the receiver without a
pre-arranged agreement. In a generic XML document, the elements can
simply be a list of string values of terms with no implied "meaning"
except what might be inferred by grouping them in a container element.
In RDF, the elements represent properties of particular resources. I
believe strongly that although there may be several "right" ways to
express properties of members of DwC classes, there are many more
"wrong" ways that should not be used. By "right" I mean that they make
sense semantically in that the properties logically are ones that
should actually belong to the described resource. I do not believe
that the discussion of these issues has progressed to the point where
there is a consensus on the "right" use of DwC terms for some types of
resources and therefore I am opposed to the posting of RDF examples on
any official Darwin Core sites without a lot more discussion UNLESS the
examples are clearly labeled as examples intended for discussion and
not for use as templates. If you want such examples, I can provide<br>
<a href="http://bioimages.vanderbilt.edu/vanderbilt/4-145.rdf" target="_blank">http://bioimages.vanderbilt.edu/vanderbilt/4-145.rdf</a>
as an example for
an Individual<br>
<a href="http://bioimages.vanderbilt.edu/baskauf/79695.rdf" target="_blank">http://bioimages.vanderbilt.edu/baskauf/79695.rdf</a>
as am example of an
Occurrence that is a live plant image and<br>
<a href="http://bioimages.vanderbilt.edu/rdf/examples/lsu000/0138.rdf" target="_blank">http://bioimages.vanderbilt.edu/rdf/examples/lsu000/0138.rdf</a>
as an
example of an Occurrence that is an herbarium specimen<br>
I would be happy to discuss the reasons why I structured the RDF as I
did (although mostly those examples are already rationalized in
<a href="https://journals.ku.edu/index.php/jbi/article/view/3664" target="_blank">https://journals.ku.edu/index.php/jbi/article/view/3664</a>),
but I would
not go so far as to say that they are "right" without some discussion.<br>
<br>
What I intended when I suggested that I might write some kind of guide
for Darwin Core represented in RDF/XML was really a document that
explained to beginners what the point was of RDF, the basics of how one
can structure properties in RDF using examples that are Darwin Core
terms, and options for creating URIs that refer to resources that are
described in separate files or within the same file. I wasn't really
suggesting that it be a full-blown recommendation with specific
guidelines for the use of particular terms or structuring of files for
particular classes of resources, although that would be a good thing
ultimately. I guess I was seeing some kind of a beginner's guide as a
way to involve more people (who aren't up on RDF) in the discussion. I
don't think that it should be necessary to complete full "standards"
process before such a document were made available. It would probably
be better to have some kind of road map where that document would be
the first segment but would later be followed by guidelines for
specific classes of resources with examples. I think that such a
modular approach would be the most beneficial because pieces of it
could actually get done in a timely fashion rather than requiring the
whole thing to be complete before any of it would be accepted. <br>
<br>
I do think a task group for Darwin Core RDF would be a good idea. If
nobody is in a huge hurry, I don't mind trying to charter such a group,
although I'd be just as happy if somebody else wanted to do it and I
would just try be an active participant. I will look at the links you
suggested, thanks.<br>
<br>
Steve<br>
<br>
<br>
Blum, Stan wrote:
<blockquote type="cite">
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">Steve,<br>
<br>
The TDWG process for creating standards is here: <a href="http://www.tdwg.org/about-tdwg/process/" target="_blank">http://www.tdwg.org/about-tdwg/process/</a>
This is worth reading if you haven’t done so already. <br>
<br>
Another document worth reading is the standards format specifiation <a href="http://www.tdwg.org/standards/147/" target="_blank">http://www.tdwg.org/standards/147/</a>
I never pushed this “standard” through public review, but it still
functions a guideline for formatting and our view of what is isn’t
within scope of a “standard”. In other words, we are doing our best to
follow the basic ideas laid out there about the kinds of specifications:<br>
<br>
Type 1 -- normative specification, versioned; <br>
Type 2 -- versioned, supplementary documentation;<br>
Type 3 — uncontrolled supplementary documentation. <br>
<br>
The page of examples John and others have put up on the DarwinCore site
is non-normative, uncontrolled documentation. <br>
<br>
The thing you were proposing sounded like an applicability statement —
offering guidance about how another standard, RDF, should be used in
biodiversity informatics. These can also be treated as standards, and
get TDWG ratification as standard, but don’t create a de-novo standard.<br>
<br>
Interest groups and task groups are explained in the Process. If you
want to create an applicability statement for RDF and DarwinCore, you
could prepare a task group charter and submit it to the executive for
approval. Approval would make it a formal Task Group. See other task
group charters for examples.<br>
<br>
-Stan<br>
<br>
<br>
<br>
<br>
On 10/13/10 6:33 AM, "Steve Baskauf" <<a href="http://steve.baskauf@vanderbilt.edu" target="_blank">steve.baskauf@vanderbilt.edu</a>>
wrote:<br>
<br>
</span></font>
<blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">OK, because of a momentary heavy work load
I'm still in the process of getting caught up on this thread, but this
is moving so fast I feel like I'm being left in the dust. Last week I
offered to help facilitate creating some guidelines and examples for
RDF/XML in Darwin Core. I was told that we should follow the community
process of forming an interest group, getting participants, etc. and
have been waiting for some guidelines on how that process is supposed
to work. Now we are surging ahead with examples and help pages again.
Are we following a process or not and if so, what is it?<br>
Steve<br>
<br>
Tim Robertson (GBIF) wrote: <br>
</span></font>
<blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">I will also help with examples. If we are
doing XML / RDF formats, lets get an example record conforming to the
Text guidelines in there as well for completeness (most useful when
dealing with checklists). <br>
<br>
<br>
<br>
<br>
<br>
On Oct 12, 2010, at 10:31 PM, John Wieczorek wrote:<br>
<br>
<br>
</span></font>
<blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">I am interested in helping with an examples
page. The page could have XML and RDF examples illustrating particular
use cases, as you have recommended. Create an "Examples" page on the
Table of Contents and then have all of the examples on one page with an
index of links to specific examples at the top? I made a straw man page
to show what I am thinking at <a href="http://code.google.com/p/darwincore/wiki/Examples" target="_blank">http://code.google.com/p/darwincore/wiki/Examples</a>.<br>
<br>
<br>
On Tue, Oct 12, 2010 at 11:41 AM, "Markus Döring (GBIF)" <<a href="http://mdoering@gbif.org" target="_blank">mdoering@gbif.org</a>>
wrote:<br>
<br>
</span></font>
<blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">Would we have the energy to compile example
dwc records on how to use darwin core for certain use cases?<br>
The lack of guidance on how to use darwin core was mentioned earlier.
An additional example webpage for the dwc website would surely be
really helpful for not only newbies. A dwc record for bird watching,
vegetation plot surveys, insect specimen collection, herbarium sheets,
zoological garden visits, tissue sample, dna sequence, marine fishing
net catches, etc<br>
<br>
Id volunteer to do the html page if Im given example records with a
short use case description...<br>
<br>
<font color="#888888">Markus<br>
</font> <br>
<br>
<br>
<br>
On Oct 12, 2010, at 13:14, Roger Hyam wrote:<br>
<br>
> Wow - what a thread to come back to.<br>
><br>
> I saw my name mentioned so I ought to chip in. I also think we are
conflating two distinct things under the name "occurrence".<br>
><br>
> This point is largely just expanding on what Kevin just said.
Going down the road he was wise enough not to go down!<br>
><br>
> The vocabulary I briefly presented at TDWG was aimed at occurrence
of taxa in regions but the general thrust of my talk was intended to
pose the questions: Why should we score taxa to regions at all?
Shouldn't this always be the results of a query on occurrence records?
The answer will always depend on the question asked.<br>
><br>
> Take two examples.<br>
><br>
> A tiger roaming "free" in London living off a diet of squirrels
and tourists. Occurrence records for this organism are just occurrence
records. Why the tiger is in London (climate change, introduction,
invasion, escape) is not a quality of it being there. They are value
judgements added later.<br>
><br>
> A tiger sitting in a cage a London Zoo is "managed" in that it is
being maintained there by a human effort. We are recording the fact
that someone has placed it there and held it in that position for our
edification.<br>
><br>
> As Kevin says, when I observe an individual (or flock of
individuals) I do not observe their "introducedness" or their
"nativeness" this is something that is derived from combining multiple
observations of occurrence of individuals.<br>
><br>
> I would therefore advocate that we just have a flag on an
occurrence record that says "intended for distribution" i.e. this is
not maintained here in a garden/zoo/farm etc. To say any more on a
occurrence record is misleading and there are occasions when even this
flag will be ignored in analysis. I think we already have this field.<br>
><br>
> There are of course grey areas (biology always has grey areas). A
Scots Pine growing in the highlands may be part of a 150 year old
naturalistic plantation. It is therefore native to the region, possibly
of local genetic stock but has been planted in that position. For some
applications this could be considered managed and for others not.<br>
><br>
> The status of taxa in regions is a completely different thing. As
soon as we talk about aggregating multiple observations (or lack of
them) then we are talking about the results of analysis instead of
primary observations. Only at this point should we be talking about
the status of the "occurrence" in terms of native/invasive/naturalised
etc. This may not even be based on extant records. For example, a taxon
can be invasive in an area without actually occurring there. i.e. it
used to be there but is presumed to be irradiated.<br>
><br>
> Does the problem occur because we are using the same term
"occurrence" to mean both a primary unit of data gathering and the
result of an analysis (possibly even just a hypothesis if it is the
result of niche modelling)? How could we differentiate between these
two? The discussion probably comes back to 'basisOfRecord' again and
our fundamental classes of object.<br>
><br>
> Sorry to be long winded.<br>
><br>
> Roger<br>
><br>
><br>
> On 12 Oct 2010, at 09:36, Kevin Richards wrote:<br>
><br>
>> I also have always felt that "nativeness" should apply more to
an occurrence than a taxon, but have swayed from one opinion to the
other on a regular basis. So my conclusion is that "nativeness" is a
propety of both, and require both, in a way - and that these different
perspectives are actually the same thing.<br>
>><br>
>> Eg, if we describe (in a basic way) :<br>
>> Ocurrence = Taxon at Location<br>
>><br>
>> then if we say that Nativeness is a property of a Taxon that
is restricted by Location (jerry's view)<br>
>> then this is equivalent to saying that Nativeness is a
property of an Ocurrence ! (Rich's view)<br>
>><br>
>> As Rich points out, it doesnt make a whole lot of sense to
apply Nativeness to a single occurrence, but I'm not sure this is what
is meant by stating that "this specimen of Poa anceps that I collected
from Christchurch is 'Native'" - but more that "I have found a specimen
of Poa anceps in Christchurch and from knowledge of other previously
recorded ocurrences, I know that this occurence/taxon is Native in this
area"<br>
>><br>
>> Also I tend to feel that a lot of biodiversity properties are
properties of ocurrences - EVEN taxon names are a property of an
occurrence and not of this 'concept' of a species - but I wont go down
that road right now :-)<br>
>><br>
>> Also, we discussed this topic a while ago on the tdwg content
list, having worked out that "nativeness" or what we call "biostatus"
is a fairly complicated topic, involving taxon names, locations, time,
and aspects like 'origin' and 'presence', ...<br>
>><br>
>> Kevin<br>
>><br>
>> ________________________________________<br>
>> From: <a href="http://tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>
[<a href="http://tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>]
On Behalf Of Richard Pyle [<a href="http://deepreef@bishopmuseum.org" target="_blank">deepreef@bishopmuseum.org</a>]<br>
>> Sent: Tuesday, 12 October 2010 5:41 p.m.<br>
>> To: Jerry Cooper; <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>; <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a><br>
>> Subject: Re: [tdwg-content] What I learned at the
TechnoBioBlitz<br>
>><br>
>> Hi Jerry,<br>
>><br>
>> Before we agree to disagree, let me try to elaborate a bit
more:<br>
>><br>
>> I think we both agree that "Nativeness" (to borrow Dave's
term) is a<br>
>> property of a taxon at a geographic locality (it could also be
a property of<br>
>> a taxon in a class of habitat, but few people actually frame
it this way).<br>
>><br>
>> The reason I think that "Nativeness" is best represented as a
property of an<br>
>> Occurrence, rather than of a taxon, is that a taxon is a
circumscribed set<br>
>> of organisms, usually based on evolutionary relatedness or
morphological or<br>
>> genetic similarity. By contrast, an Occurrence is about the
presence of a<br>
>> member or multiple members of a taxon concept in space and
time (i.e., at a<br>
>> particular place and time).<br>
>><br>
>> We often think of Occurrence records in terms of individual
organisms (e.g.,<br>
>> specimens, or specific observed or photographed organisms),
and I agree,<br>
>> it's weird to think of "Nativeness" as it applies to an
individual organism.<br>
>> However, my understanding is that Occurrence instances can
also apply to<br>
>> populations -- which is what terms such as establishmentMeans
and<br>
>> occurrenceStatus fit into this class.<br>
>><br>
>> More generally, if we agree that "Nativeness" is a property of
a taxon at a<br>
>> particular locality, the way that this intersection is usually
manifest in<br>
>> DwC is via Occurrence and Event instances.<br>
>><br>
>> How else would you represent "Nativeness" within DwC?<br>
>><br>
>> Aloha,<br>
>> Rich<br>
>><br>
>>> -----Original Message-----<br>
>>> From: <a href="http://tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a><br>
>>> [<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">mailto:tdwg-content-bounces@lists.tdwg.org</a>]
On Behalf Of Jerry Cooper<br>
>>> Sent: Monday, October 11, 2010 6:02 PM<br>
>>> To: <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>; <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a><br>
>>> Subject: Re: [tdwg-content] What I learned at the
TechnoBioBlitz<br>
>>><br>
>>> We will have to agree to disagree.<br>
>>><br>
>>> For me at least 'Native', 'Invasive' etc are clearly not<br>
>>> properties associated with a collection event. They are<br>
>>> collective statements, not necessarily about properties of<br>
>>> the taxon as a whole, but about the properties of a taxon
in<br>
>>> some restricted sense - usually geographically restricted.<br>
>>><br>
>>> GISIN, like our model here in NZ, pulls together such
items<br>
>>> under a triplet of taxon/occurrence statement/geographical<br>
>>> extent linked to a publication.<br>
>>><br>
>>><br>
>>> Jerry<br>
>>><br>
>>><br>
>>> -----Original Message-----<br>
>>> From: Richard Pyle [<a href="mailto:deepreef@bishopmuseum.org" target="_blank">mailto:deepreef@bishopmuseum.org</a>]<br>
>>> Sent: Tuesday, 12 October 2010 4:23 p.m.<br>
>>> To: Jerry Cooper<br>
>>> Cc: <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>; <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a><br>
>>> Subject: RE: [tdwg-content] What I learned at the
TechnoBioBlitz<br>
>>><br>
>>> Hi Jerry,<br>
>>><br>
>>> Yes, this is a road I've been down before. Intuitively,<br>
>>> these terms seem like they should apply to taxon concepts,<br>
>>> but it turns out that's not the right way to do it. Things<br>
>>> like "native" and "invasive" are not properties of taxon<br>
>>> concepts; they're the property of an occurrence (which, I<br>
>>> suspect, is why establishmentMeans is included in the<br>
>>> Occurrence class in DwC; e.g., see the examples at<br>
>>> <a href="http://rs.tdwg.org/dwc/terms/index.htm#establishmentMeans" target="_blank">http://rs.tdwg.org/dwc/terms/index.htm#establishmentMeans</a><br>
>>><br>
>>> Rich<br>
>>><br>
>>> ________________________________<br>
>>><br>
>>> From: <a href="http://tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a><br>
>>> [<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">mailto:tdwg-content-bounces@lists.tdwg.org</a>]
On Behalf Of Jerry Cooper<br>
>>> Sent: Monday, October 11, 2010 4:38 PM<br>
>>> Cc: <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>;<br>
>>> <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a><br>
>>> Subject: Re: [tdwg-content] What I learned at the<br>
>>> TechnoBioBlitz<br>
>>><br>
>>><br>
>>><br>
>>> Rich,<br>
>>><br>
>>><br>
>>><br>
>>> Let's not confuse those terms which are best applied<br>
>>> to a taxon concept rather than a specific<br>
>>> collection/observation of a taxon at a location.<br>
>>><br>
>>><br>
>>><br>
>>> There are existing vocabularies for taxon-related<br>
>>> provenance, like those in GISIN, or the vocabulary Roger<br>
>>> mentioned in his PESI talk at TDWG.<br>
>>><br>
>>><br>
>>><br>
>>> However, against a specific collection you can only<br>
>>> record what the recorder actually knows at that location
for<br>
>>> that specific collected taxon, and not to infer a status
like<br>
>>> 'introduced' etc.<br>
>>><br>
>>><br>
>>><br>
>>> So, to me, the vocabulary reduces even further - and<br>
>>> the obvious ones are 'in cultivation', 'in captivity',<br>
>>> 'border intercept' . Our botanical collection management<br>
>>> system would hold more data on provenance of a specific<br>
>>> collection and linkages between events - from the wild at
t=1,<br>
>>> x=1 to cultivation in botanic garden Y at t=2, X=2 etc. But<br>
>>> then we often have that data because we are generating it.<br>
>>><br>
>>><br>
>>><br>
>>> Jerry<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> From: <a href="http://tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a><br>
>>> [<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">mailto:tdwg-content-bounces@lists.tdwg.org</a>]
On Behalf Of Richard Pyle<br>
>>> Sent: Tuesday, 12 October 2010 3:27 p.m.<br>
>>> To: <a href="http://Donald.Hobern@csiro.au" target="_blank">Donald.Hobern@csiro.au</a>; <a href="http://tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a><br>
>>> Cc: <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>;<br>
>>> <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a><br>
>>> Subject: Re: [tdwg-content] What I learned at the<br>
>>> TechnoBioBlitz<br>
>>><br>
>>><br>
>>><br>
>>> I certainly agree it's important! I was just saying<br>
>>> that a simple flag probably wouldn't be enough. I like the<br>
>>> idea of a controlled vocabulary (as you and John both
allude<br>
>>> to), and I can imagine about a half-dozen terms that our<br>
>>> community will no-doubt adopt with almost no debate.....
:-)<br>
>>><br>
>>><br>
>>><br>
>>> In my mind, the broadest categories (and likely most<br>
>>> useful) would be something like:<br>
>>><br>
>>><br>
>>><br>
>>> Native (was there without any assistance from
humans)<br>
>>><br>
>>> Introduced (got there with the assistance of humans,<br>
>>> but is inhabiting the natural environment)<br>
>>><br>
>>> Captive (brought by humans and still maintained in
captivity)<br>
>>><br>
>>><br>
>>><br>
>>> You might also throw in "Cryptogenic", which is an<br>
>>> assertion that we do not know which of these categories a<br>
>>> particular organism falls (not the same as null, which
means<br>
>>> we don't know whether or not we know)<br>
>>><br>
>>><br>
>>><br>
>>> Of course, each of these can be further subdivded,<br>
>>> but the more we subdivide, the greater the ratio of<br>
>>> fuzzy:clean distinctions. I would say that the terms should<br>
>>> be established in consultation with those most likely to
use<br>
>>> them (e.g., as you suggest, distribution analysis, niche
modellers,<br>
>>> etc.) For example, it might be useful to distinguish
between<br>
>>> an organism that was itself introduced, compared to the<br>
>>> progeny (or a well-established<br>
>>> population) of an intoduced organism. This information can
be<br>
>>> useful for separating things likely to become established
in<br>
>>> new localities, vs. things that do not seem to "take" in a<br>
>>> novel environment.<br>
>>><br>
>>> Anyway...I didn't want to say a lot on this topic<br>
>>> (too late?); I just wanted to steer more towards controlled<br>
>>> vocabulary, than simple flag field.<br>
>>><br>
>>><br>
>>><br>
>>> Aloha,<br>
>>><br>
>>> Rich<br>
>>><br>
>>><br>
>>><br>
>>> ________________________________<br>
>>><br>
>>> From: <a href="http://Donald.Hobern@csiro.au" target="_blank">Donald.Hobern@csiro.au</a><br>
>>> [<a href="mailto:Donald.Hobern@csiro.au" target="_blank">mailto:Donald.Hobern@csiro.au</a>]<br>
>>> Sent: Monday, October 11, 2010 3:44 PM<br>
>>> To: Richard Pyle; <a href="http://tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a><br>
>>> Cc: <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>;<br>
>>> <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a><br>
>>> Subject: RE: [tdwg-content] What I learned
at<br>
>>> the TechnoBioBlitz<br>
>>><br>
>>> Hi Rich.<br>
>>><br>
>>><br>
>>><br>
>>> I recognise this (and could probably define<br>
>>> many different useful flags). The bottom line is really<br>
>>> whether or not the location is one which should be used for<br>
>>> distribution analysis, niche modelling and similar<br>
>>> activities. There will certainly be many grey areas, but
it<br>
>>> would be good if software could weed out captive
occurrences.<br>
>>><br>
>>><br>
>>><br>
>>> Donald<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> untitled<br>
>>><br>
>>><br>
>>><br>
>>> Donald Hobern, Director, Atlas of<br>
>>> Living Australia<br>
>>><br>
>>> CSIRO Ecosystem Sciences, GPO Box 1700,<br>
>>> Canberra, ACT 2601<br>
>>><br>
>>> Phone: (02) 62464352 Mobile: 0437990208<br>
>>><br>
>>> Email: <a href="http://Donald.Hobern@csiro.au" target="_blank">Donald.Hobern@csiro.au</a><br>
>>> <<a href="mailto:Donald.Hobern@csiro.au" target="_blank">mailto:Donald.Hobern@csiro.au</a>><br>
>>><br>
>>> Web: <a href="http://www.ala.org.au/" target="_blank">http://www.ala.org.au/</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> From: Richard Pyle [<a href="mailto:deepreef@bishopmuseum.org" target="_blank">mailto:deepreef@bishopmuseum.org</a>]<br>
>>> Sent: Tuesday, 12 October 2010 12:33 PM<br>
>>> To: Hobern, Donald (CES, Black Mountain);<br>
>>> <a href="http://tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a><br>
>>> Cc: <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>;<br>
>>> <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a><br>
>>> Subject: RE: [tdwg-content] What I learned
at<br>
>>> the TechnoBioBlitz<br>
>>><br>
>>><br>
>>><br>
>>> I'm not so sure a simple flag will do it.
We<br>
>>> have examples ranging from animals in zoos, to escaped<br>
>>> animals, to intentionally and unintentionally introduced<br>
>>> populations, to naturalized populations -- and just about<br>
>>> everything in-between. Where on this spectrum would you
draw<br>
>>> the line for flagging something as "naturally occurring"?<br>
>>><br>
>>><br>
>>><br>
>>> Rich<br>
>>><br>
>>><br>
>>><br>
>>> ________________________________<br>
>>><br>
>>> From:<br>
>>> <a href="http://tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a><br>
>>> [<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">mailto:tdwg-content-bounces@lists.tdwg.org</a>]
On Behalf Of<br>
>>> <a href="http://Donald.Hobern@csiro.au" target="_blank">Donald.Hobern@csiro.au</a><br>
>>> Sent: Monday, October 11, 2010 2:59
PM<br>
>>> To: <a href="http://tuco@berkeley.edu" target="_blank">tuco@berkeley.edu</a><br>
>>> Cc: <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>;<br>
>>> <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a><br>
>>> Subject: Re: [tdwg-content] What I<br>
>>> learned at the TechnoBioBlitz<br>
>>><br>
>>> Thanks, John.<br>
>>><br>
>>><br>
>>><br>
>>> This is useful, but completely<br>
>>> uncontrolled - effectively a verbatimEstablishmentMeans.<br>
>>> Having a more controlled version or a simple flag which
could<br>
>>> be machine-processible in those cases where providers can<br>
>>> supply it would be useful.<br>
>>><br>
>>><br>
>>><br>
>>> Donald<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> untitled<br>
>>><br>
>>><br>
>>><br>
>>> Donald Hobern, Director,<br>
>>> Atlas of Living Australia<br>
>>><br>
>>> CSIRO Ecosystem Sciences, GPO Box<br>
>>> 1700, Canberra, ACT 2601<br>
>>><br>
>>> Phone: (02) 62464352 Mobile:
0437990208<br>
>>><br>
>>> Email: <a href="http://Donald.Hobern@csiro.au" target="_blank">Donald.Hobern@csiro.au</a><br>
>>> <<a href="mailto:Donald.Hobern@csiro.au" target="_blank">mailto:Donald.Hobern@csiro.au</a>><br>
>>><br>
>>> Web: <a href="http://www.ala.org.au/" target="_blank">http://www.ala.org.au/</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> From: <a href="http://gtuco.btuco@gmail.com" target="_blank">gtuco.btuco@gmail.com</a><br>
>>> [<a href="mailto:gtuco.btuco@gmail.com" target="_blank">mailto:gtuco.btuco@gmail.com</a>]
On Behalf Of John Wieczorek<br>
>>> Sent: Tuesday, 12 October 2010
11:34 AM<br>
>>> To: Hobern, Donald (CES, Black
Mountain)<br>
>>> Cc: <a href="http://jsachs@csee.umbc.edu" target="_blank">jsachs@csee.umbc.edu</a>;<br>
>>> <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a>;
<a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
>>> Subject: Re: [tdwg-content] What I<br>
>>> learned at the TechnoBioBlitz<br>
>>><br>
>>><br>
>>><br>
>>> Natural occurrence is meant to be<br>
>>> captured through the term dwc:establishmentMeans<br>
>>> (<a href="http://rs.tdwg.org/dwc/terms/index.htm#establishmentMeans" target="_blank">http://rs.tdwg.org/dwc/terms/index.htm#establishmentMeans</a>).<br>
>>><br>
>>> On Mon, Oct 11, 2010 at 5:16 PM,<br>
>>> <<a href="http://Donald.Hobern@csiro.au" target="_blank">Donald.Hobern@csiro.au</a>>
wrote:<br>
>>><br>
>>> Thanks, Joel.<br>
>>><br>
>>> Nice summary. One addition which we<br>
>>> do need to resolve (and which has been suggested in recent<br>
>>> months) is to have a flag to indicate whether a record
should<br>
>>> be considered to show a "natural"<br>
>>> occurrence (in distinction from cultivation, botanic
gardens,<br>
>>> zoos, etc.).<br>
>>> This is not so much an issue in a BioBlitz, but is
certainly<br>
>>> a factor with citizen science recording in general - see
the<br>
>>> number of zoo animals in the Flickr EOL group.<br>
>>><br>
>>> Donald<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> Donald Hobern, Director, Atlas of<br>
>>> Living Australia<br>
>>> CSIRO Ecosystem Sciences, GPO Box<br>
>>> 1700, Canberra, ACT 2601<br>
>>> Phone: (02) 62464352 Mobile:
0437990208<br>
>>> Email: <a href="http://Donald.Hobern@csiro.au" target="_blank">Donald.Hobern@csiro.au</a><br>
>>> Web: <a href="http://www.ala.org.au/" target="_blank">http://www.ala.org.au/</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> -----Original Message-----<br>
>>> From: <a href="http://tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a><br>
>>> [<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">mailto:tdwg-content-bounces@lists.tdwg.org</a>]
On Behalf Of joel sachs<br>
>>> Sent: Monday, 11 October 2010 10:47
PM<br>
>>> To: <a href="http://tdwg-bioblitz@googlegroups.com" target="_blank">tdwg-bioblitz@googlegroups.com</a>;<br>
>>> <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
>>> Subject: [tdwg-content] What I<br>
>>> learned at the TechnoBioBlitz<br>
>>><br>
>>> One of the goals of the recent<br>
>>> bioblitz was to think about the suitability and<br>
>>> appropriatness of TDWG standards for citizen science.
Robert<br>
>>> Stevenson has volunteered to take the lead on preparing a<br>
>>> technobioblitz lessons learned document, and though the
scope<br>
>>> of this document is not yet determined, I think the
audience<br>
>>> will include bioblitz organizers, software developers, and<br>
>>> TDWG as a whole. I hope no one is shy about sharing lessons<br>
>>> they think they learned, or suggestions that they have. We<br>
>>> can use the bioblitz google group for this discussion, and<br>
>>> copy in 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<br>
>>> right for citizen science. However, there is a desperate
need<br>
>>> for examples and templates of its use. To illustrate this<br>
>>> need: one of the developers spoke of the design choice<br>
>>> between "a simple csv file and a Darwin Core record". But a<br>
>>> simple csv file is a legitimate representation of Darwin<br>
>>> Core! To be fair to the developer, such a sentence might
not<br>
>>> have struck me as absurd a year ago, before Remsen said<br>
>>> "let's use DwC for the bioblitz".<br>
>>><br>
>>> We provided a couple of example DwC<br>
>>> records (text and rdf) in the bioblitz data profile [1]. I<br>
>>> think the lessons learned document should include an
on-line<br>
>>> catalog of cut-and-pasteable examples covering a variety of<br>
>>> use cases, together with a dead simple desciption of DwC,<br>
>>> something like "Darwin Core is a collection of terms,<br>
>>> together with definitions."<br>
>>><br>
>>> Here are areas where we augemented
or<br>
>>> diverged from DwC in the bioblitz:<br>
>>><br>
>>> i. We added obs:observedBy [2],
since<br>
>>> there is no equivalent property in DwC, and it's important
in<br>
>>> Citizen Science (though often not available).<br>
>>><br>
>>> ii. We used geo:lat and geo:long [3]<br>
>>> instead of DwC terms for latitude and longitude. The geo<br>
>>> namespace is a well used and supported standard, and
records<br>
>>> with geo coordinates are automatically mapped by several<br>
>>> applications. Since everyone was using GPS to retrieve
their<br>
>>> coordinates, we were able to assume WGS-84 as the datum.<br>
>>><br>
>>> If someone had used another Datum,<br>
>>> say XYZ, we would have added columns to the Fusion table so<br>
>>> that they could have expressed their coordiantes in 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<br>
>>> kosher DwC to express the above as simply XYZ:lat and<br>
>>> 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<br>
>>> user friendly than taxonomy:binomial and the other taxonomy<br>
>>> machine tags EOL uses for flickr images. If<br>
>>> DwC:scientificName isn't self-explanatory enough, a user
can<br>
>>> look it up, and see that any scientific name is acceptable,<br>
>>> at any taxonomic rank, or not having any rank. And once we<br>
>>> have a scientific name, higher ranks can be inferred.<br>
>>><br>
>>> 3. Catalogue of Life was an
important<br>
>>> part of the workflow, but we had some problems with it.<br>
>>> Future bioblitzes might consider using something like a CoL<br>
>>> fork, as recently described by Rod Page [4].<br>
>>><br>
>>> 4. We didn't include "basisOfRecord"<br>
>>> in the original data profile, and so it wasn't a column in<br>
>>> the Fusion Table [5]. But when a transcriber felt it was<br>
>>> necessary to include in order to capture data in a
particular<br>
>>> field sheet, she just added the column to the table. This<br>
>>> flexibility of schema is important, and is in harmony with<br>
>>> the semantic web.<br>
>>><br>
>>> 5. There seemed to be enthusiasm for<br>
>>> another field event at next year's TDWG. This could be an<br>
>>> opportunity to gather other types of data (eg.<br>
>>> character data) and thereby<br>
>>> i) expose meeting particpants to<br>
>>> another set of everyday problems from the world of<br>
>>> biodiversity workflows, and ii) try other TDWG technology
on<br>
>>> for size, e.g. the observation exchange format, annotation<br>
>>> framework, etc.<br>
>>><br>
>>><br>
>>> Happy Thanksgiving to all in Canada
-<br>
>>> Joel.<br>
>>> ----<br>
>>><br>
>>><br>
>>> 1.<br>
>>> <a href="http://groups.google.com/group/tdwg-bioblitz/web/tdwg-bioblitz" target="_blank">http://groups.google.com/group/tdwg-bioblitz/web/tdwg-bioblitz</a><br>
>> -profile-v1-1<br>
>>> 2. Slightly bastardizing our old<br>
>>> 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.<br>
>>> <a href="http://iphylo.blogspot.com/2010/10/replicating-and-forking-dat" target="_blank">http://iphylo.blogspot.com/2010/10/replicating-and-forking-dat</a><br>
>> a-in-2010.html<br>
>>> 5.<br>
>>> <a href="http://tables.googlelabs.com/DataSource?dsrcid=248798" target="_blank">http://tables.googlelabs.com/DataSource?dsrcid=248798</a><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> tdwg-content mailing list<br>
>>> <a href="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
>>><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="http://tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br>
>>><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>
>>> ________________________________<br>
>>><br>
>>> Please consider the environment before printing
this email<br>
>>> Warning: This electronic message together with any<br>
>>> attachments is confidential. If you receive it in error:
(i)<br>
>>> you must not read, use, disclose, copy or retain it; (ii)<br>
>>> please contact the sender immediately by reply email and
then<br>
>>> delete the emails.<br>
>>> The views expressed in this email may not be those
of<br>
>>> Landcare Research New Zealand Limited.<br>
>>> <a href="http://www.landcareresearch.co.nz" target="_blank">http://www.landcareresearch.co.nz</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> Please consider the environment before printing this email<br>
>>> Warning: This electronic message together with any<br>
>>> attachments is confidential. If you receive it in error:
(i)<br>
>>> you must not read, use, disclose, copy or retain it; (ii)<br>
>>> please contact the sender immediately by reply email and
then<br>
>>> delete the emails.<br>
>>> The views expressed in this email may not be those of<br>
>>> Landcare Research New Zealand Limited.<br>
>>> <a href="http://www.landcareresearch.co.nz" target="_blank">http://www.landcareresearch.co.nz</a><br>
>>> _______________________________________________<br>
>>> tdwg-content mailing list<br>
>>> <a href="http://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/listinfo/tdwg-content</a><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> tdwg-content mailing list<br>
>> <a href="http://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/listinfo/tdwg-content</a><br>
>><br>
>> Please consider the environment before printing this email<br>
>> Warning: This electronic message together with any
attachments is confidential. If you receive it in error: (i) you must
not read, use, disclose, copy or retain it; (ii) please contact the
sender immediately by reply email and then delete the emails.<br>
>> The views expressed in this email may not be those of Landcare
Research New Zealand Limited. <a href="http://www.landcareresearch.co.nz" target="_blank">http://www.landcareresearch.co.nz</a><br>
><br>
> _______________________________________________<br>
> tdwg-content mailing list<br>
> <a href="http://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/listinfo/tdwg-content</a><br>
<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a href="http://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/listinfo/tdwg-content</a><br>
<br>
<br>
<br>
</span></font></blockquote>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt"> <br>
<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a href="http://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/listinfo/tdwg-content</a><br>
<br>
</span></font></blockquote>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt"> <br>
<br>
<br>
<br>
</span></font></blockquote>
</blockquote>
</blockquote>
<br>
<pre cols="72">--
Steven J. Baskauf, Ph.D., Senior Lecturer
Vanderbilt University Dept. of Biological Sciences
postal mail address:
VU Station B 351634
Nashville, TN 37235-1634, U.S.A.
delivery address:
2125 Stevenson Center
1161 21st Ave., S.
Nashville, TN 37235
office: 2128 Stevenson Center
phone: (615) 343-4582, fax: (615) 343-6707
<a href="http://bioimages.vanderbilt.edu" target="_blank">http://bioimages.vanderbilt.edu</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Steven J. Baskauf, Ph.D., Senior Lecturer
Vanderbilt University Dept. of Biological Sciences
postal mail address:
VU Station B 351634
Nashville, TN 37235-1634, U.S.A.
delivery address:
2125 Stevenson Center
1161 21st Ave., S.
Nashville, TN 37235
office: 2128 Stevenson Center
phone: (615) 343-4582, fax: (615) 343-6707
<a href="http://bioimages.vanderbilt.edu" target="_blank">http://bioimages.vanderbilt.edu</a>
</pre>
</div>
<br>_______________________________________________<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/listinfo/tdwg-content</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>----------------------------------------------------------------<br>Pete DeVries<br>Department of Entomology<br>University of Wisconsin - Madison<br>445 Russell Laboratories<br>
1630 Linden Drive<br>Madison, WI 53706<br><a href="http://www.taxonconcept.org/" target="_blank">TaxonConcept Knowledge Base</a> / <a href="http://lod.geospecies.org/" target="_blank">GeoSpecies Knowledge Base</a><br><a href="http://about.geospecies.org/" target="_blank">About the GeoSpecies Knowledge Base</a><br>
------------------------------------------------------------<br>
</div>