[tcs-lc] where to go now..

Kennedy, Jessie J.Kennedy at napier.ac.uk
Thu Mar 10 09:15:48 PST 2005


Hi Sally

thanks for the suggestion - I guess that's what we did when we merged LC into TCS - version 0.09b - we took on board more but basically took that approach.

Jessie

>-----Original Message-----
>From: tcs-lc-admin at ecoinformatics.org
>[mailto:tcs-lc-admin at ecoinformatics.org]On Behalf Of Sally Hinchcliffe
>Sent: 10 March 2005 14:54
>To: tcs-lc at ecoinformatics.org
>Subject: RE: [tcs-lc] where to go now..
>
>
>help ... that's close
>
>Could you just take the part of the LC that covers CanonicalName, 
>CanonicalAuthorship and the Label and drop it into the place where 
>the ABCD name element was in TCS? The rest of LC is optional 
>anyway and afaik those bits of LC are now fairly well agreed? Or 
>am I missing something?
>Of course, I'm not sure how viral names would fit in ...
>
>Sally
>
>
>
>> The date I will have to announce the TCS is March 20th....
>> 
>> Jessie
>> 
>> >-----Original Message-----
>> >From: tcs-lc-admin at ecoinformatics.org
>> >[mailto:tcs-lc-admin at ecoinformatics.org]On Behalf Of Roger Hyam
>> >Sent: 10 March 2005 14:15
>> >To: tcs-lc at ecoinformatics.org
>> >Subject: Re: [tcs-lc] where to go now..
>> >
>> >
>> >Hi Jessie
>> >
>> >Could you put some firm dates on those day counts. I am using 
>> >my fingers 
>> >and a wall planner here but some one else may be doing the 
>> >same and not 
>> >coming up with the same dates.
>> >
>> >Thanks,
>> >
>> >Roger
>> >
>> >Kennedy, Jessie wrote:
>> >
>> >>Dear list
>> >>
>> >>You may or may not be aware of the rules for putting forward 
>> >standards for TDWG but the bottom line is that a standard must 
>> >be given to the exec to be made open for discussion at TDWG 60 
>> >days prior to the meeting. We complied with this last year for 
>> >TCS and had a discussion and agree to make some changes.
>> >>the next stage is to put the standard forward to TDWG for 
>> >voting - this version has to be publicised 180 days before the 
>> >next meeting.
>> >>I had hoped we would be reaching consensus but to be honest 
>> >can't tell if we're getting nearer or further to consensus. I 
>> >really don't know where to go from here.....so need your help! 
>> >>
>> >>As chair of the Names/Concepts subgroup of TDWG I will put 
>> >forward the TCS in time that it might be voted on at TDWG - 
>> >knowing that although it has to be out for discussion 180 days 
>> >in advance we can make some changes in the interim period.
>> >>
>> >>But I don't know what to do yet about the name element in TCS. 
>> >>
>> >>As I've said before I thought LC was replacing the name 
>> >element for TCS but I think what is being proposed for LC is 
>> >very different to what Walter intended by the name element in 
>> >ABCD. TCS was designed with this type of name element in mind 
>> >but we tried to show how nomenclaturalists could use the TCS 
>> >for their purposes. Just like we tried to show how others 
>> >could use it for their purposes. 
>> >>
>> >>I think I would be very happy to at least get agreement on a 
>> >type at the level that was there and what Walter needs 
>> >independent of what the nomenclaturalists need in terms of 
>> >relationships, types etc.
>> >>Then if the nomenclaturalists don't think they can represent 
>> >their information in TCS maybe they should put together an 
>> >alternative schema for discussion this year at TDWG - is this 
>> >a sensible way to go ahead?
>> >>
>> >>Jessie
>> >>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. 
>> >>_______________________________________________
>> >>tcs-lc mailing list
>> >>tcs-lc at ecoinformatics.org
>> >>http://www.ecoinformatics.org/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
>> >==============================================
>> >
>> >
>> >
>> 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. 
>> _______________________________________________
>> tcs-lc mailing list
>> tcs-lc at ecoinformatics.org
>> http://www.ecoinformatics.org/mailman/listinfo/tcs-lc
>
>
>*** Sally Hinchcliffe
>*** Computer section, Royal Botanic Gardens, Kew
>*** tel: +44 (0)20 8332 5708
>*** S.Hinchcliffe at rbgkew.org.uk
>_______________________________________________
>tcs-lc mailing list
>tcs-lc at ecoinformatics.org
>http://www.ecoinformatics.org/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. 



More information about the Tcs-lc mailing list