- tdwg-content - lists.tdwg.org

Simple Darwin Core to Dublin Core mapping...
by Paul R Butler 30 Mar '10

30 Mar '10

Howdy all! I am creating an xslt to crosswalk from Simple Darwin Core to Dublin Core. I was wondering if anyone has created a mapping between the two element sets that they would be willing to share. Cheers and have a great day! Paul ------------------------------ UIUC MLS Student President UIUC ALA Student Chapter Graduate Assistant - History, Philosophy, and Newspaper Library University of Illinois, Urbana-Champaign 1408 W. Gregory Drive Urbana, IL 61801 butler9(a)illinois.edu http://people.lis.illinois.edu/~butler9

2 1

[tdwg-phylo] Phyloinformatics Summer of Code 2009 - Call for student applications
by Hilmar Lapp 27 Mar '10

27 Mar '10

*** Please disseminate widely at your local institutions, including *** *** posting to message and job boards, so that we reach as many *** *** students as possible . *** PHYLOINFORMATICS SUMMER OF CODE 2010 http://hackathon.nescent.org/Phyloinformatics_Summer_of_Code_2010 The Phyloinformatics Summer of Code program provides a unique opportunity for undergraduate, masters, and PhD students to obtain hands-on experience writing and extending open-source software for evolutionary informatics under the mentorship of experienced developers from around the world. The program is the participation of the US National Evolutionary Synthesis Center (NESCent) as a mentoring organization in the Google Summer of Code(tm) (http://code.google.com/soc/ ). Students in the program will receive a stipend from Google (and possibly more importantly, a T-shirt solely available to successful participants), and may work from their home, or home institution, for the duration of the 3 month program. Each student will have at least one dedicated mentor to show them the ropes and help them complete their project. NESCent is particularly targeting students interested in both evolutionary biology and software development. Initial project ideas are listed on the website. These range from phylogenetics pipeline development to a user interface for MIAPA-driven annotation of experiments, interactive animations of gene tree evolution, and rendering phylogenies on Google Earth. All project ideas are flexible and many can be adjusted in scope to match the skills of the student. We also welcome novel project ideas that dovetail with student interests. TO APPLY: Apply online at the Google Summer of Code website (http://socghop.appspot.com/ ), where you will also find GSoC program rules and eligibility requirements. The 12-day application period for students opens on Monday March 29th and runs through Friday, April 9th, 2010. INQUIRIES: phylosoc {at} nescent {dot} org. We strongly encourage all interested students to get in touch with us with their ideas as early on as possible. 2010 NESCent Phyloinformatics Summer of Code: http://hackathon.nescent.net/Phyloinformatics_Summer_of_Code_2010 Google Summer of Code FAQ: http://socghop.appspot.com/document/show/program/google/gsoc2010/faqs DataONE Summer 2010 Internship Program (managed separately, and different from GSoC; postdocs also eligible): http://d1-lab.appspot.com/ --------- Todd Vision and Hilmar Lapp National Evolutionary Synthesis Center http://nescent.org

1 1

[tdwg-phylo] Call for Abstracts open for Conference on Informatics for Phylogenetics, Evolution, and Biodiversity (iEvoBio)
by Hilmar Lapp 03 Mar '10

03 Mar '10

The Call for Abstracts for full talks is now open for the inaugural conference on Informatics for Phylogenetics, Evolution, and Biodiversity (iEvoBio), at http://ievobio.org/ocs/index.php/ievobio/ 2010. See below for instructions. Accepted talks will be about 15-20 minutes in length and will be presented during the full talk sessions in the morning of each of the two conference days, following the day's keynote presentation. Submitted talks should be in the area of informatics aimed at advancing research in phylogenetics, evolution, and biodiversity, including new tools, cyberinfrastructure development, large-scale data analysis, and visualization. Submissions consist of a title and an abstract at most 1 page long. The abstract should provide an overview of the talk's subject. As the number of program slots for full talks is limited, the abstract should give enough detail so reviewers can decide whether the submission merits a full talk or whether it should be moved to one of the lightning talk sessions. If the subject of the talk is a specific software for use by the research community, the abstract must state the license and give the URL where the source code is available so reviewers can verify that the open-source requirement(*) is met. The deadline for submission is April 8, 2010. We intend to notify authors of accepted talks before early registration for iEvoBio (and Evolution) ends. Further instructions for submission are at the following URL: http://ievobio.org/ocs/index.php/ievobio/2010/information/presenters Full talks are 1 of 5 kinds of contributed content that iEvoBio will feature. The other 4 are: 1) Lightning talks (5 mins long), 2) Challenge entries, 3) Software bazaar demonstrations, and 4) Birds-of- a-Feather gatherings. The Call for Challenge entries is already open (see http://ievobio.org/challenge.html), and information on how to contribute to the other 3 sessions is forthcoming. More details about the program and guidelines for contributing content are available at http://ievobio.org. You can also find continuous updates on the conference's Twitter feed at http://twitter.com/iEvoBio. iEvoBio is sponsored by the US National Evolutionary Synthesis Center (NESCent) in partnership with the Society of Systematic Biologists (SSB). Additional support has been provided by the Encyclopedia of Life (EOL). The iEvoBio 2010 Organizing Committee: Rod Page (University of Glasgow) Cecile Ane (University of Wisconsin at Madison) Rob Guralnick (University of Colorado at Boulder) Hilmar Lapp (NESCent) Cynthia Parr (Encyclopedia of Life) Michael Sanderson (University of Arizona) (*) iEvoBio and its sponsors are dedicated to promoting the practice and philosophy of Open Source software development (see http://www.opensource.org/docs/definition.php) and reuse within the research community. For this reason, if a submitted talk concerns a specific software system for use by the research community, that software must be licensed with a recognized Open Source License (see http://www.opensource.org/licenses/), and be available for download, including source code, by a tar/zip file accessed through ftp/http or through a widely used version control system like cvs, Subversion, git, Bazaar, or Mercurial. Authors of full talks who cannot meet this requirement at the time of submission should state their intentions, and are advised that the requirement must be met by June 27 at the latest.

1 0

Specimen citations
by Willem Coetzer 18 Feb '10

18 Feb '10

Good day My colleagues and I are developing an idea that could help to keep biodiversity information current. In particular, it will allow a new determination to be added, timeously, to a specimen's determination history. Online publishers of taxonomic articles, such as ZooKeys, are an important component of the proposed system. Suppose you want to publish an article describing a new species. The online journal would require you to submit the traditional 'material examined' section of the manuscript as a spreadsheet. The publisher would upload these data to GBIF. The collection manager responsible for the specimens you examined would receive this information from GBIF. In fact, this information could even be used to update that collection manager's database automatically (after validation by the collection manager), by adding a new determination to each of the affected collection objects, complete with the determiner's name, date of determination, determination confidence etc. Now that the information is updated at source (the museum specimen database), and is disseminated by GBIF, everyone can benefit from the latest determinations made by expert taxonomists. If you're interested in these ideas, please read our manuscript: http://docs.google.com/Doc?docid=0AW4Pz09fjmYaZGN3bmtjOWNfNGR3azVkNmR2&hl=en We would appreciate your feedback. Willem Coetzer Information Manager South African Institute for Aquatic Biodiversity Grahamstown, South Africa Tel. +27 (0)46 603 5841 Fax +27 (0)46 622 2403 www.saiab.ac.za

2 1

[tdwg-img] testing list; ignore
by Bob Morris 17 Feb '10

17 Feb '10

ignore this messsage -- Robert A. Morris Professor of Computer Science (nominally retired) UMASS-Boston 100 Morrissey Blvd Boston, MA 02125-3390 Associate, Harvard University Herbaria email: ram(a)cs.umb.edu web: http://bdei.cs.umb.edu/ web: http://etaxonomy.org/FilteredPush http://www.cs.umb.edu/~ram phone (+1)617 287 6466

1 0

Indicating which Occurrence resources are useful for documenting distributions
by Steve Baskauf 16 Feb '10

16 Feb '10

I have had several off-list email exchanges about this topic and have been encouraged to bring the topic to this list for comment. Along with addressing this topic specifically, I'd like to include clarification of how I view Occurrences, based partly on emails written during the October/November tdwg-content list discussion regarding the conflict between Darwin Core and Dublin Core usage of dcterms:type, partly on some off-list email discussions about various DwC terms and their appropriate application, and partly on my own view of the relationship between Occurrences and the proposed Darwin Core class Individual. If I have misrepresented anything, please reply to the list with your perspective on the situation. (The following namespaces are used for brevity: dcterms="http://purl.org/dc/terms/", dcmitype="http://purl.org/dc/dcmitype/", dwc="http://rs.tdwg.org/dwc/terms/", and dwctype="http://rs.tdwg.org/dwc/dwctype/".) A. CHARACTERISTICS OF MEMBERS OF THE CLASS dwc:Occurrence 1. Instances of the DwC class Occurrence represent evidence that a particular organism existed at some point in time. Thus a photo of a certain bird would qualify as an Occurrence, while a painting that was made by looking at a number of stuffed and live birds (but no particular one bird) would not be an Occurrence. 2. Categorization of a resource as an Occurrence does not imply fitness of use for any particular purpose. An Occurrence may or may not be useful for any of the following purposes: serve to document the presence of an organism in nature at a particular place and time (i.e. to help model the natural distribution of a species), serve as a teaching tool, facilitate an identification key, illustrate a character state, provide an image for a trademark of the museum, etc. 3. An Occurrence may be typed using dcterms:type (having values such as dcmitype:PhysicalObject, dcmitype:Sound, or dcmitype:StillImage) and dwc:basisOfRecord (having values such as dwctype:PreservedSpecimen, dwctype:LivingSpecimen, and dwctype:HumanObservation). However, the typing of an Occurrence again does not imply fitness of use for any particular purpose. An Occurrence of a particular type may be used for any or all purposes for which it is useful. B. HOW DO WE KNOW WHICH OCCURRENCES ARE USEFUL FOR DOCUMENTING DISTRIBUTIONS? Having made the point that an Occurrence does not have an implied fitness for any particular use, it is true that one of the most common uses of DwC in the past has been to describe the metadata required to document the presence of organisms for the purpose of describing species' distributions. I don't know if there is an official term for this use, but I'm going to refer to it as the "distribution documentation" use. In the current Darwin Core standard, this use is facilitated by the term dwc:establishmentMeans (http://rs.tdwg.org/dwc/terms/index.htm#establishmentMeans), which is defined as "the process by which the biological individual(s) represented in the Occurrence became established at the location." dwc:establishmentMeans helps a metadata user to assess the fitness of a record for distribution documentation by differentiating between individual organisms that occur naturally and those that do not. Because dwc:establishmentMeans allows for values that span the range of native to adventive/naturalized to cultivated, a metadata user can select a level of stringency when searching. dwc:establishmentMeans assumes that any type of Occurrence can be used to document the individual. However, not all Occurrences are suitable for distribution documentation. So an important question is: under what circumstances do Occurrences provide useful information for documenting a species distribution? Another important question which should be addressed is: which Occurrence records should have dwc:establishmentMeans as a property? (or should dwc:establishmentMeans should be a property of something other than Occurrences?) C. EXAMPLES In discussing these questions, I will use some examples which range from a relatively simple circumstance (preserved specimens in a museum or herbarium collection) to more complex networks of various kinds of resources. Example 1: http://people.vanderbilt.edu/~steve.baskauf/conceptual-scheme-herbarium.gif Example 2: http://people.vanderbilt.edu/~steve.baskauf/conceptual-scheme-insect.gif Example 3: http://people.vanderbilt.edu/~steve.baskauf/conceptual-scheme-botanical.gif The starting point in all of these example diagrams is an Individual organism found in the environment. By Individual I mean the object of the term dwc:individualID, which is the entity that a dwcterm:Occurrence documents and is described by the class proposed for DwC at: http://code.google.com/p/darwincore/issues/detail?id=69. (As a practical matter an "Individual" may also represent a small population of organisms of the same species.) This Individual is the entity that dwc:establishmentMeans describes. The Occurrence resources that are created are represented by the rectangles in the diagram. In these examples they are primarily specimens and images but they could also be other types of resources. Each Occurrence is associated with a particular dcmitype:Event in which the Occurrence resource was created (an "Occurrence resource creation event" described by the date/time and dcterms:Location of the event and represented by arrows in the diagram). Because of the one-to-one relationship between an Occurrence resource and the Event in which it is created, I have chosen to think of the metadata for both things as a single unit. One could also divide them conceptually into two separate entities, i.e. different resources having different identifiers. Whether this approach is desirable or not should probably be the subject of a separate thread. D. WHICH OCCURRENCES CONTAIN LOCATION INFORMATION ABOUT INDIVIDUALS? Since each Occurrence resource has location metadata associated with its resource creation event, each one has the potential for providing information to document a distribution. However it is clear from these diagrams that the location metadata for many of these Occurrences has no use for distribution documentation because the Occurrences were created in locations that have no relationship to the Individual (e.g. the location in a lab where a DNA sample was extracted or in a museum where an image was created from a specimen). Examination of all three examples shows that the resource creation events for Occurrences that are derived directly from the Individual (highlighted in gray) provide useful information about where the Individual was at a particular time (i.e. distribution documentation), while the resource creation events for all of the other Occurrences do not. (Note that whether or not an Occurrence documents the distribution of the Individual's species is not related to the type [dcterms:type or dwc:basisOfRecord] of the resource.) It seems to me that there is a need for a Darwin Core term that indicates whether the location metadata for a particular Occurrence resource creation event is useful for distribution documentation - I can't see any terms currently in the standard that can serve this function. Perhaps term could be created such as "documentsDistribution" having values of "true" for those derived directly from the Individual and "false" for those that are not. E. TO WHAT DOES dwc:establishmentMeans APPLY? Currently dwc:establishmentMeans is assigned to the class Occurrence. So theoretically, a value for the dwc:establishmentMeans of the Individual could be assigned to any Occurrence resource/resource creation event derived from the Individual regardless of how far the Occurrence is removed from the Individual through multiple resource creation events. I believe that this would probably be a bad idea, since the person creating the metadata for more distantly derived resources (i.e. a technician doing a DNA extraction or photographing a leg on a pinned specimen in example 2) may not have a clue about the status of the original Individual. At best, that person would just copy the value of dwc:establishmentMeans from the metadata for some other Occurrence resource derived more directly from the Individual, which would be rather pointless. Alternatively, dwc:establishmentMeans could be assigned only to Occurrence resources/resource creation events for which "documentsDistribution"="true". One could argue that each collector/observer (i.e. the object of dwc:recordedBy) of an Occurrence derived directly from the Individual could theoretically make an independent assessment of the correct value of dwc:establishmentMeans for the Individual. It could also be argued that dwc:establishmentMeans should be associated with particular Occurrences because if an Individual's dwc:establishmentMeans status changed over time, then multiple Occurrences recorded from that Individual over time could have different values of dwc:establishmentMeans. However, it is difficult for me to imagine circumstances under which this would happen. An Individual that was "cultivated" is not likely to become "native" or vice-versa. The one situation I can imagine is if a "native" (or "adventive/naturalized") individual were collected and moved to a zoo or botanical garden. However, in that circumstance, upon collection the organism would cease to be in its natural environment and would conceptually become an Occurrence of type dwctype:LivingSpecimen rather than an Individual. In such a circumstance, the value of dwc:establishmentMeans for the LivingSpecimen metadata should be "native" (or "adventive/naturalized") because establishmentMeans refers to "the biological individual(s) represented in the Occurrence", not to the Occurrence itself, and at the time of its collection, the Individual's establishmentMeans was "native" (or "adventive/naturalized"). To me, the most logical thing would be to re-assign dwc:establishmentMeans from the class dwc:Occurrence to the proposed Darwin Core class Individual. That makes sense to me because after all, dwc:establishmentMeans is supposed to tell us something about an Individual. However, there could be a couple problems with this. One is that it is likely that many collectors of preserved specimens (e.g. who have simple resource creation circumstances such as in example 1) are not going to see any reason to bother with the concept of Individuals. If they do not create records for Individuals, then in what context will they assign a value of dwc:establishmentMeans? The other problem that I foresee is if two different collector/observers created recorded Occurrences from the same Individual but assigned the Individual different values of dwc:establishmentMeans. When those two Individual records are merged into one, there would either have to be some kind of rule for determining which value of dwc:establishmentMeans to use, or two values of dwc:establishmentMeans would have to be allowed for a single Individual. However, it seems to me that this circumstance would probably occur only very rarely. F. SUMMARY It seems to me that two things are needed here to meet the needs of users who create complex networks of Occurrence resources such as in Examples 2 and 3. 1. A term such as "documentsDistribution" is needed to unambiguously indicate whether the dcterms:Location and dcmitype:Event (i.e. resource creation event) metadata for a particular Occurrence provide useful information about the Individual that the Occurrence represents. 2. Clarification of whether the term dwc:establishmentMeans should be a part of the metadata for individual Occurrence resources (and if so, which ones) or whether it should be moved to the proposed class Individual. Comments??? Steve Baskauf -- 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 http://bioimages.vanderbilt.edu

1 1

[tdwg-phylo] Registration Open for Conference on Informatics for Phylogenetics, Evolution, and Biodiversity (iEvoBio)
by Hilmar Lapp 13 Feb '10

13 Feb '10

Registration is now open for the inaugural conference on Informatics for Phylogenetics, Evolution, and Biodiversity (iEvoBio), at http://www.evolutionsociety.org/SSE2010/Register.html . iEvoBio aims to bring together biologists working in evolution, systematics, and biodiversity, with software developers, and mathematicians, both to develop new tools, and to increase awareness of existing technologies (ranging from standards and reusable toolkits to mega-scale data analysis to rich visualization). The 2-day meeting will take place June 29-30, 2010, in Portland, OR, jointly with the Evolution Meetings as a satellite conference. The event will feature traditional elements, including a keynote presentation at the beginning of each day and contributed talks, as well as more dynamic and interactive elements, including a challenge, lightning talk-style sessions, a software bazaar, and Birds-of-a- Feather gatherings. Attendees can register jointly for Evolution and iEvoBio at a discount, or only for the iEvoBio conference. For more information about registration, venue, travel, or accommodations visit the Evolution 2010 website at http://www.evolutionsociety.org/SSE2010/. More details about the program and guidelines for contributing content are available at http://ievobio.org. You can also find continuous updates on the conference's Twitter feed at http://twitter.com/iEvoBio. iEvoBio is sponsored by the US National Evolutionary Synthesis Center (NESCent) in partnership with the Society of Systematic Biologists (SSB). Additional support has been provided by the Encyclopedia of Life (EOL). The iEvoBio 2010 Organizing Committee: Rod Page (University of Glasgow) Cecile Ane (University of Wisconsin at Madison) Rob Guralnick (University of Colorado at Boulder) Hilmar Lapp (NESCent) Cynthia Parr (Encyclopedia of Life) Michael Sanderson (University of Arizona)

1 0

Fwd: BasisOfrecord flavors; which one to choose
by John R. WIECZOREK 10 Feb '10

10 Feb '10

---------- Forwarded message ---------- From: Francisco Pando <pando(a)gbif.es> Date: Tue, Feb 9, 2010 at 8:57 AM Subject: RE: BasisOfrecord flavors; which one to choose To: "John R. WIECZOREK" <tuco(a)berkeley.edu> Cc: "dremsen(a)gbif.org" <dremsen(a)gbif.org> Hi John, Thanks a lot, I have a clearer picture now. Please go ahead and post whatever you think could be useful of this on TDWG-Content. All the best, Paco Francisco Pando Responsable GBIF.ES, Unidad de Coordinación Tel.+34 91 420 3017 x 274 Real Jardín Botánico - CSIC Fax +34 91 429 2405 Plaza de Murillo, 2 pando(a)gbif.es 28014 Madrid, Spain www.gbif.es *From:* gtuco.btuco(a)gmail.com [mailto:gtuco.btuco@gmail.com] *On Behalf Of *John R. WIECZOREK *Sent:* martes, 09 de febrero de 2010 17:25 *To:* Francisco Pando *Cc:* dremsen(a)gbif.org *Subject:* Re: BasisOfrecord flavors; which one to choose Hi Paco, The only difference between the first list ( http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm) and the third list ( http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary) is the Event term. Actually I believe that the Event term shouldn't be on the first list, because it is a Dublin Core term and already a controlled vocabulary term for dcterms:type. I think you should go under that assumption. In any case, I doubt that people will want to share biodiversity records that are Events that are not one of the subtypes of Events on the third list. I updated the Google Code wiki page to be more explicit that the Event and PhysicalObject terms come from Dublin Core. There has been some discussion on the tdwg-content list about other possible basisOfRecord vocabulary to try to better distinguish digital media. The original argument for this is captured in an Issue on the Darwin Core Google Code site at http://code.google.com/p/darwincore/issues/detail?id=68. This is a good example of how the type vocabulary might be expanded to cover new cases. I don't know what to tell you about the GBIF vocabulary except that it was devised in April of last year before the type vocabularies for Darwin Core reached their current state of maturity. As this discussion may be useful to others, I'd like to request that you post it to tdwg-content as well, or give me permission to do so. Hope that helps, John On Tue, Feb 9, 2010 at 1:07 AM, Francisco Pando <pando(a)gbif.es> wrote: Dear David, dear John, We are in the process of updating some of our software to make it compliant with the approved DwC standard. We decided to start on something we thought it was easy, BasisOfrecord. However we found: http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm "The Type Vocabulary is a recommended set of values to use for the basisOfRecord term to categorize Darwin Core resources." *Vocabulary for basisOfRecord* Occurrence<http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#Occurrence> Event <http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#Event> Location <http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#Location> Taxon <http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#Taxon> PreservedSpecimen<http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#PreservedSpecimen> FossilSpecimen<http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#FossilSpecimen> LivingSpecimen<http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#LivingSpecimen> HumanObservation<http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#HumanObservation> MachineObservation<http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#MachineObservation> NomenclaturalChecklist<http://rs.tdwg.org/dwc/terms/type-vocabulary/index.htm#NomenclaturalCheckli…> Date Modified: 2009-12-07 http://vocabularies.gbif.org/vocabularies/basis_of_record Concepts in the *basisOfRecord* vocabulary FossilSpecimen <http://vocabularies.gbif.org/basis_of_record/FossilSpecimen> HumanObservation<http://vocabularies.gbif.org/basis_of_record/HumanObservation> LivingSpecimen <http://vocabularies.gbif.org/basis_of_record/LivingSpecimen> MachineObservation<http://vocabularies.gbif.org/basis_of_record/MachineObservation> MovingImage <http://vocabularies.gbif.org/basis_of_record/MovingImage> NomenclaturalAct<http://vocabularies.gbif.org/basis_of_record/NomenclaturalAct> PreservedSpecimen<http://vocabularies.gbif.org/basis_of_record/PreservedSpecimen> StillImage <http://vocabularies.gbif.org/basis_of_record/StillImage> TaxonDistribution<http://vocabularies.gbif.org/basis_of_record/TaxonDistribution> TaxonName <http://vocabularies.gbif.org/basis_of_record/TaxonName> TaxonNameUsage <http://vocabularies.gbif.org/basis_of_record/TaxonNameUsage> Submitted by admin <http://vocabularies.gbif.org/users/admin> on Tue, 2009-04-21 23:34 http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary The Type Vocabulary used in Darwin Core consists of two parts, vocabulary to describe the record in terms consistent with the Dublin Core Type vocabulary (using the dcterms:type term) and vocabulary to describe the specific biodiversity-related content for a record (using the basisOfRecord term). The list of valid values for the basisOfRecord include: *Term* *Subtype of* Occurrence Event PreservedSpecimen PhysicalObject FossilSpecimen PhysicalObject LivingSpecimen PhysicalObject HumanObservation Event MachineObservation Event Taxon Location NomenclaturalChecklist Updated Jan 17, 2010 by gtuco.btuco I seems safer to go for the Google Code option, but shouldn’t the three sources be coherent? Best wishes, Paco Francisco Pando Responsable GBIF.ES, Unidad de Coordinación Tel.+34 91 420 3017 x 274 Real Jardín Botánico - CSIC Fax +34 91 429 2405 Plaza de Murillo, 2 pando(a)gbif.es 28014 Madrid, Spain www.gbif.es

3 2

Re: [tdwg-content] [tdwg-tag] Indicating living versus deceased status in Darwin Core
by Bob Morris 30 Jan '10

30 Jan '10

Jason The GBIF Multimedia Resource Task Group (MRTG) is shortly to begin the process of submission to TDWG of its draft proposal for metadata on multimedia objects and collections. Later this year GBIF expects to support this in the Integrated Publishing Toolkit, so it might be of particular interest to you for any of the image management in your tools. The current draft is at http://www.keytonature.eu/wiki/MRTG_Schema_v0.9 The TDWG standards process will present further opportunity to comment on the proposal, but the aforementioned wiki also solicits comments (To do so, you will need to register for that wiki to comment, but not to view). Bob Morris On Fri, Jan 29, 2010 at 1:35 PM, Jason Holmberg <holmbergius(a)gmail.com> wrote: > Thanks for the responses! > > If I'm understanding this correctly...should I then propose a new term as > discussed by John? > > As background, we have a successful multi-user, Web-based mark-recapture > software platform at www.whaleshark.org that we would like to open source. > Before open sourcing it, I would like it to be as "standards-based" as > possible. One measure of this is to use DarwinCore attributes in the > database tables, allowing for the easy mapping of TapirLink into the db and > therefore easier data exposure. > > If this group can think of other standards that it would be goods to > support, please let me know. I would like to build interoperability directly > into the software before releasing it, allowing adopters of the platform to > expose data meaningfully with minimal effort. > > Thanks, > Jason > > > On Thu, Jan 28, 2010 at 5:25 PM, Phillip C. Dibner <pcd(a)ecosystem.com> > wrote: >> >> On Jan 28, 2010, at 4:17 PM, Kevin Richards wrote: >> >>> There is probably another (external to TDWG) vocab / ontology that could >>> handle this?? >> >> I'm not certain at this time. However .... >> >>> (which, I think, we ought to be encouraging anyway???) >> >> Concur. We are falling into the realm where a generic observation model >> would be useful. Otherwise, we will encounter an increasing number of ad >> hoc treatments for other attributes, without a consistent underlying >> framework. >> >> May I point, as a matter of interest, to the SONet Project: >> https://sonet.ecoinformatics.org/ >> >> Best regards, >> Flip >> >> > > > _______________________________________________ > tdwg-tag mailing list > tdwg-tag(a)lists.tdwg.org > http://lists.tdwg.org/mailman/listinfo/tdwg-tag > > -- Robert A. Morris Professor of Computer Science (nominally retired) UMASS-Boston 100 Morrissey Blvd Boston, MA 02125-3390 Associate, Harvard University Herbaria email: ram(a)cs.umb.edu web: http://bdei.cs.umb.edu/ web: http://etaxonomy.org/FilteredPush http://www.cs.umb.edu/~ram phone (+1)617 287 6466

1 0

Re: [tdwg-content] [tdwg-tag] Indicating living versus deceased status in Darwin Core
by John R. WIECZOREK 29 Jan '10

29 Jan '10

Hi Jason, The (only) slightly more appropriate place to post this is the tdwg-content list, which I've cc'd. You've posed an interesting scenario that I suspect was never imagined during Darwin Core development. I know I didn't. More and more discussion about individuals and their status over time is emerging, and I find the process of "testing" Darwin Core against these interesting. I think there are lots of ways to accommodate the information you've mentioned using the Darwin Core as it is. Some are more satisfying and reusable than others. And if Darwin Core as it now stands ends up failing, there are ways to extend it. Here are a few ways the sighting information could be accommodated now. 1) Use the dwc:behavior term. This would be particularly suitable if you had a richer vocabulary that just alive or dead, but could be used nevertheless as long as no one gets too upset about alive and dead not being traditional behavior descriptors. Well, maybe if we assume that "dead" is a hypothesis and think about the animal "acting dead" then there might be fewer objections. ;-) 2) Use the dwc:eventRemarks term. I'm loathe to suggest this because I hate putting data with analytical potential into an ad hoc field where it can get lost or misunderstood for not having a strong context. 3) Use the dwc:dynamicProperties term. The intention of this term is pretty well documented on the Simple Darwin Core page under "Doing More with Simple Darwin Core" (http://rs.tdwg.org/dwc/terms/simple/index.htm#domore). Here's the relevant verbiage from the Simple Darwin Core page to get the full idea, along with the pros and cons of this technique. "Another way to get more out of the Darwin Core without adding a term is to "payload" the dynamicProperties term as shown in the example below, to contain a list of key-value pairs. The keys in this case would act as new unofficial terms. This is perfectly legal, since it doesn't compromise the meaning of the term. Some of the weaknesses of payloading are that it is prone to errors, inconsistencies, and lack of stable or well-defined semantics. Still, this might be a reasonable way to at least allow you to share all of your data, even if there might be problems with people using it reliably." Basically, for your example, you could include in this field the key-value pair for your data field, whatever you call it. Suppose you called it liveStatus. You could load information in Darwin Core records via the dwc:dynamicProperties term that included "liveStatus=alive" or "liveStatus=dead". In XML that could look something like this: <dwc:dynamicProperties>liveStatus=alive</dwc:dynamicProperties> 4) Finally, if none of the above are fully satisfying, you can propose that a new term be added to the Darwin Core. The process for doing so is documented on the Namespace Policy page under the Term Change Policy section (http://rs.tdwg.org/dwc/terms/namespace/index.htm#classesofchanges), specifically section 3.4 Addition of Darwin Core term declarations to existing Darwin Core namespaces. And though that section says that requests for changes should be submitted to the TDWG-TAG, there is a well-documented procedure and infrastructure for it on the Darwin Core Project Site for Discussion and Development. The details can be found on the wiki page about Submitting Issues (http://code.google.com/p/darwincore/wiki/SubmittingIssues). It's worth reading the whole thing, despite that the section of particular interest in this case is the one called "New Term Request", accessible from the link with that title. 5) Of course, you can start making your own library of terms and give them a namespace to use in tandem with Darwin Core. This may be necessary if you can't make a strong enough case for a new term - for example, because it is too specialized to be of use across communities. I'm not saying that's the case here, only that this would be cause to have to define your own namespace and terms for those specialized concepts. The advantage of creating a new Darwin Core term is that it will definitely reach a wider audience than something project based, and will thereby promote re-use and integration between data sets. Temptations I would avoid include the following: I would not use occurrenceStatus, as its meaning is pretty clear. An animal would be present, whether alive or dead. I also wouldn't use dwc:lifeStage, not because death couldn't be argued to be a life stage, but because it would be a mix of semantics to include "alive" when the term is meant to capture something about categorical ages. Now you're an expert! Good luck and respond here to tdwg-content if you have further queries about this or similar Darwin Core Issues. Cheers, John On Wed, Jan 27, 2010 at 10:32 AM, Jason Holmberg <holmbergius(a)gmail.com> wrote: > > Hello! Apologies for the newbie question, which I am hoping has reached the > correct list. > > I'm altering the names of tables in a mark-recapture database to reflect > Darwin Core labels as part of a larger open source initiative. I need to > indicate in a new field whether a whale shark sighting (occurrence) > represents a living or deceased whale shark. Which Darwin Core field would > best represent this? A look through the terms in the Quick Reference did not > yield an immeidate match for me, but apologies if I missed the obvious. Can > you recommend an appropriate field? > > Thanks in advance! > Jason Holmberg > ECOCEAN Whale Shark Photo-identification Library > http://www.whaleshark.org > > > > _______________________________________________ > tdwg-tag mailing list > tdwg-tag(a)lists.tdwg.org > http://lists.tdwg.org/mailman/listinfo/tdwg-tag > >

2 1