Graphical design component

r8 - 11 Jun 2007 - 11:12:35 - RogerHyamYou are here: TWiki >  TAG Web > TaxonNameLsidVoc > LsidVocs > SpecimenLsidVoc

SpecimenLsidVoc


warning This vocabulary has been superseded by the TaxonOccurrenceLsidVoc. Read more about it on the TaxonOccurrenceLsidVoc page.

This is a summary of the LSID Vocabulary for Specimen. Read LsidVocs information on LSID Vocabularies in general.

See OccurrenceRecordLsidVoc for a diagram illustrating the relationships between an occurrence and a Specimen. The Avowed schemas and CNS files for OccurrenceRecord? and Specimen are very similar because they embed one another.

Resources

The RDF OWL vocabulary http://rs.tdwg.org/ontology/voc/Specimen
Example XML Instance Being developed
Avowed XML Schema http://rs.tdwg.org/ontology/voc/tapir/structure/Specimen/Specimen.xsd
TAPIR CNS file http://rs.tdwg.org/ontology/voc/tapir/structure/Specimen/Specimen.txt
TAPIR CNS file 2 http://rs.tdwg.org/ontology/voc/tapir/structure/Specimen/Specimen_basic.txt (a slightly cut down version that is simpler to use for flat table mapping)
Concept Docs SpecimenLsidVocDoc - documentation for TAPIR style concepts.

Deployments

  • not yet!

Discussion

Visiting the first link under Resources above with a modern web browser will display the documentation for the vocabulary. Please read this first. If you then have any discussion points or questions please add them below.


  • Locality
I believe that it is an error to include the geographic-object attributes (coordinates, etc.) as part of the specimen. Many other objects need them as well, especially taxon observations. -- Gregor Hagedorn, 2007-05-03

I don't follow Gregor's objection. OccurrenceRecordLsidVoc indeed has such attributes. But there seem to be two issues: (a). OccurrenceRecordLsidVoc supports both geocoded and named locality, but SpecimenLsidVoc seems to support only the former and (b)even if this is an oversight, there is a data integrity issue if an OccurrenceRecord? and its voucher specimen have different localities. One possible solution is to have a voucher class (generalizing both specimens and e-vouchers) and put the location only on vouchers. This would probably give rise to a need to have a sort of empty voucher that contains little but locality and something representing the source of the voucher (collecter, photographer, publication, ...) -- BobMorris - 27 May 2007


Linking Topics

Edit | Attach | Printable | Backlinks: Web, All Webs | History: r8 < r7 < r6 < r5 < r4 | More topic actions
 
Back to TDWG Homepage TDWG Wiki > TAG
This site is powered by the TWiki collaboration platform

Valid XHTML 1.0 Transitional
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback