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

[Kennedy, Jessie]

I'm fine with TaxonName

Jessie

> -----Original Message-----
> From: tcs-lc-bounces at ecoinformatics.org [mailto:tcs-lc-
> bounces at ecoinformatics.org] On Behalf Of Richard Pyle
> Sent: 21 September 2005 10:59
> To: Roger Hyam; G. Hagedorn
> Cc: tcs-lc at ecoinformatics.org
> Subject: Re: [tcs-lc] Proposal: revise ObjectType names in TCS
> 
> 
> I *DEFINITELY* agree with "TaxonName".  It contrasts perfectly with
> "TaxonConcept".  Funny -- I've now come full circle -- "TaxonName" is what
> I
> used in my very earliest drafts of Taxonomer.  Maybe it's time I went back
> to my roots?
> 
> Aloha,
> Rich
> 
> > -----Original Message-----
> > From: tcs-lc-bounces at ecoinformatics.org
> > [mailto:tcs-lc-bounces at ecoinformatics.org]On Behalf Of Roger Hyam
> > Sent: Tuesday, September 20, 2005 11:37 PM
> > To: G. Hagedorn
> > Cc: tcs-lc at ecoinformatics.org
> > Subject: Re: [tcs-lc] Proposal: revise ObjectType names in TCS
> >
> >
> > Raised NameObject -> TaxonNameObject as issue 038. In fact I think this
> > should be TaxonName as we are talking about a data structure that may or
> > may not be represented as a software object....
> >
> > Raised Voucher -> Specimen as issue 039.
> >
> > Personally I have  no problems with these changes. In fact I much prefer
> > TaxonName. We will need to sit down check the changes don't set off a
> > chain reaction but can probably get them in version 1 I think.
> >
> > Roger
> >
> >
> > Gregor Hagedorn wrote:
> >
> > >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
> > >
> > >
> > >
> >
> > --
> >
> > ==============================================
> >  Roger Hyam
> > ----------------------------------------------
> >  Biodiversity Informatics
> >  Independent Web Development
> > ----------------------------------------------
> >  http://www.hyam.net  roger at hyam.net
> > ----------------------------------------------
> >  2 Janefield Rise, Lauder, TD2 6SP, UK.
> >  T: +44 (0)1578 722782 M: +44 (0)7890 341847
> > ==============================================
> >
> >
> > _______________________________________________
> > Tcs-lc mailing list
> > Tcs-lc at ecoinformatics.org
> > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/tcs-lc
> 
> 
> _______________________________________________
> 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.