Dear John and Jonathan,
Resurrecting Trac ticket 99 has been on my Todo list for some time - thanks John. I'm not in the office until Tuesday and my Trac login credentials are on my work PC. Hence this reply via the normal list.
Since the last correspondence on this ticket, SeaDataNet have adopted a LSID URI syntax incorporating the AphiaID driven by standards from the OBIS community for identifying taxa. It would make a lot of sense to adopt this in CF. I don't have the details to hand, but if anyone from VLIZ or ICES is watching this thread maybe they could provide the precise syntax of this URI. If not, I'll dig it out next week. As Jonathan says, this will need to be a string array.
John - are you able to write draft text for inclusion in the CF documentation?
Cheers, Roy.
________________________________________
From: Jonathan Gregory [j.m.gregory at reading.ac.uk]
Sent: 23 April 2014 16:47
Subject: Re: [CF Metadata] #99: Taxon Names and Identifiers
#99: Taxon Names and Identifiers
-----------------------------+------------------------------
Reporter: lowry | Owner: cf-conventions_at_?
Type: enhancement | Status: new
Priority: high | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
\
\
\
\
\
\
Comment (by jonathan):
Dear John
Thank you for moving this forward. I am not an expert and defer to you and
Roy, but what you propose seems fine to me. I think the text for the
standard would need to be more specific about the content of a variable
containing taxon global identifiers. Wouldn't it have to be string data,
in order to be able to say (as a URN) what sort of identifier it is, as in
your example? Can it be required to be a URN? If the `col` variable is an
array of strings, following the netCDF classic model (as we do so far in
CF), it should be a 2D char array.
I note with sadness that ''F. excelsior'' is currently threatened by a
nasty disease in England.
Jonathan
\
\
\
--
Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/99#comment:10>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
Received on Wed Apr 23 2014 - 10:10:07 BST
