[tcs-lc] Proposal: revise ObjectType names in TCS

[Kennedy, Jessie]

I am happy with the proposal to prefix the names with Taxon.

Did we agree to change Voucher to specimen or Unit as in ABCD - I guess Roger took notes..

Jessie

> -----Original Message-----
> From: tcs-lc-bounces at ecoinformatics.org [mailto:tcs-lc-
> bounces at ecoinformatics.org] On Behalf Of Gregor Hagedorn
> Sent: 19 September 2005 20:26
> To: tcs-lc at ecoinformatics.org
> Subject: [tcs-lc] Proposal: revise ObjectType names in TCS
> 
> When thinking about how TCS components would integrate into a larger
> modular
> schema (encompassing name, concept, collection, descriptive data, perhaps
> entire online-flora-fauna-monographs), I believe that the core object type
> names in TCS should be revised.
> 
> At the meeting in St. Petersburg, "Voucher" (a role name specific
> to the relation of a specimen to taxon name or concept) was already
> discussed,
> and renaming it to "Specimen" was accepted.
> 
> I believe similarly, "NameObject" and "RelationshipAssertions" are too
> general
> and depend on the context of being embedded inside TCS.
> 
> I propose to rename them to TaxonNameObject and
> TaxonRelationshipAssertions.
> 
> Gregor
> 
> 
> ----------------------------------------------------------
> Gregor Hagedorn (G.Hagedorn at bba.de)
> Institute for Plant Virology, Microbiology, and Biosafety
> Federal Research Center for Agriculture and Forestry (BBA)
> Königin-Luise-Str. 19           Tel: +49-30-8304-2220
> 14195 Berlin, Germany           Fax: +49-30-8304-2203
> 
> _______________________________________________
> Tcs-lc mailing list
> Tcs-lc at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/tcs-lc
This message is intended for the addressee(s) only and should not be read, copied or disclosed to anyone else outwith the University without the permission of the sender.
It is your responsibility to ensure that this message and any attachments are scanned for viruses or other defects. Napier University does not accept liability for any loss
or damage which may result from this email or any attachment, or for errors or omissions arising after it was sent. Email is not a secure medium. Email entering the 
University's system is subject to routine monitoring and filtering by the University.