This message came from the CF Trac system. Do not reply. Instead, enter your comments in the CF Trac system at https://cf-pcmdi.llnl.gov/trac/.
#99: Taxon Names and Identifiers -----------------------------+---------------------------------------------- Reporter: lowry | Owner: [email protected] Type: enhancement | Status: new Priority: high | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: -----------------------------+---------------------------------------------- Comment (by lowry): Thanks Jonathan for your constructive feedback, with which I have no issues. I did initially consider a variable for each id, but felt my suggestion in the example would be more acceptable.[[BR]] As to John's point I strongly feel that a name given should be from an authoritative source and that source should provide an identifier that does something useful. I also strongly feel that acceptable sources should be named and that WoRMS and ITIS should be included as both of these offer a governance that provide a mechanism for verifying and adding proposals for new names. However, I don't believe that the list of two should be prescriptive. Should the community require it then obviously the list could be extended. [[BR]] On the specific point of whether S2000 should be added depends on whether LSIDs are in active use in the community likely to use CF. In my community (SeaDataNet) they aren't - we use aphiaIDs, but common sense has prevailed and the aphiaID has been incorporated into the LSID. For example, my favourite copepod C finmarchicus as an LSID of urn:lsid:marinespecies.org:taxname:104464 and an aphiaID of 104464. So, the list could be extended as and when required, but at the moment I don't feel anything is gained by adding S2000. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/99#comment:5> CF Metadata <http://cf-pcmdi.llnl.gov/> CF Metadata This message came from the CF Trac system. To unsubscribe, without unsubscribing to the regular cf-metadata list, send a message to "[email protected]" with "unsubscribe cf-metadata" in the body of your message.
