Hi Heinke,
I am involved in this issue through an IODE/SCOR group on data publication. I see the development of identifier allocation and URI resolution as outside the scope of CF. It is something that needs to be provided as a service by a dedicated organisation with a high level of professionalism. If existing service providers fall short of the mark then this should be documented and taken up with the service providers. IODE, SCOR and possibly CF governance are appropriate vehicles for this.
Your e-mail triggered the thought in my mind that now we have versioning fully implemented on the Vocabulary Server bringing it up to publication standard there is the possibility of assigning a DOI to each published version of a vocabulary. I'll give this some thought.
Cheers, Roy.
-----Original Message-----
From: cf-metadata-bounces at cgd.ucar.edu [mailto:cf-metadata-bounces at cgd.ucar.edu] On Behalf Of Heinke Hoeck
Sent: 28 October 2009 10:40
To: V. Balaji; cf-metadata at cgd.ucar.edu
Subject: Re: [CF-metadata] Dealing with large numbers of flag valuesinnetcdf cf
V. Balaji wrote:
> Bryan Lawrence writes:
>
>> My job is to persist data indefinitely, and I'm relying on vocabulary
>> servers ... (and in particular, Roy's ... ) somehow we will persist
>> the vocab.ndg.nerc.ac.uk address, regardless of nerc's future, and of
>> ndg's future, although if ac.uk went away we might be in trouble :-).
>
> Could happen...
>
> http://www.guardian.co.uk/politics/2009/oct/18/conservatives-defence
>
> I see nerc.co.uk coming...
I would like to discuss the use of persistent identifiers.
Presently, We are using the DOI and URN persistent identifiers
for the publication and reference of primary data (www.std-doi.de).
For our application, of course, the DOI (
http://dx.doi.org/) and URN
(
http://www.persistent-identifier.de/resolving/ResolverDemo.php)
systems are not adequate. However, the idea of persistent identifiers
or keywords could solve the problem of the persistent metadata
identification in the NetCDF-CF header. The persistent identifier
doesn't need to contain semantic meaning. The URL before it could be
changed but the object (meaning) behind must be persistent.
We wold need a resolver system which should be installed at more than
one institute. I am not an expert to set up a resolver system but
may be there is anyone who has experience with it.
Best wishes
Heinke
_______________________________________________
CF-metadata mailing list
CF-metadata at cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/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 Oct 28 2009 - 04:51:30 GMT
