Hello Ed,
To Roy's comment I'll add that I would like to complement in-file metadata with additional online info, not replace it. E.g. for the tag NT0908 I have a name "Paran? flooded savanna" which can go in the file, but there is a web page giving the full characterisation of what is meant by "Paran? flooded savanna", and this includes an extended description, references and photographs. It would be unreasonable to include all these photos etc in the file, so a convenient means of referring to them would be helpful.
Regards,
Martin
> -----Original Message-----
> From: Lowry, Roy K [mailto:rkl at bodc.ac.uk]
> Sent: 27 October 2009 15:45
> To: Ed Hartnett; Juckes, Martin (STFC,RAL,SSTD)
> Cc: cf-metadata at cgd.ucar.edu; Weatherall, Pauline
> Subject: RE: [CF-metadata] Dealing with large numbers of flag
> valuesinnetcdf cf
>
> Hi Ed,
>
> Establishing on-line metadata resources with permanence is the name of
> my game. If I didn't have confidence it would be around in 15 years I
> wouldn't be promoting it.
>
> Cheers, Roy.
>
> -----Original Message-----
> From: Ed Hartnett [mailto:ed at unidata.ucar.edu]
> Sent: 27 October 2009 15:37
> To: martin.juckes at stfc.ac.uk
> Cc: Lowry, Roy K; cf-metadata at cgd.ucar.edu; Weatherall, Pauline
> Subject: Re: [CF-metadata] Dealing with large numbers of flag
> valuesinnetcdf cf
>
> <martin.juckes at stfc.ac.uk> writes:
>
> > Hello Roy,
> >
> > That is an interesting idea. There are definitions of these areas on
> a WWF site, of the form
> >
> http://www.worldwildlife.org/wildworld/profiles/terrestrial/nt/nt0908_f
> ull.html where "nt0908" is a tag associated with a particular flag
> value.
> >
> > My first thought was:
> > URI="
> http://www.worldwildlife.org/wildworld/profiles/terrestrial/[flag_meani
> ng]_full.html" with "nt/nt0908" in the flag_meanings attribute, but it
> appears that the cf-checker does not like having a "/" in
> flag_meanings. This means we need to either have a more complex syntax,
> or set up our definition URLs along the lines you suggest.
> >
> > A more complex syntax might be:
> > URI="
> http://www.worldwildlife.org/wildworld/profiles/terrestrial/[flag_meani
> ng][0:2]/[flag_meaning]_full.html"
> >
> > Since the above returns html rather than skos/xml it should perhaps
> be complemented by a uri_content_type attribute, with value
> 'html/text'.
> >
> > I'll think about the option of setting up something like your vocab
> server -- or possibly putting some more definitions in the ndg vocab
> server?
> >
> > Regards,
> > Martin
>
> Howdy all!
>
> I really don't think you should store metadata for a file on the
> web. Just put it in the file.
>
> Most scientific data are around a lot longer than most URLs. What
> happens in 15 years when someone wants to understand this data, and the
> URL has vanished? It the metadata were stored in the file, then it
> would
> be there for that programmer of the future. (And that programmer may
> well be you! <insert scary Halloween laughter here>)
>
> If the metadata seem too large to put in the file, consider storing
> them
> in variables, and then use netCDF-4 with compression turned on for
> those
> variables.
>
> Thanks,
>
> Ed
>
>
>
> --
> Ed Hartnett -- ed at unidata.ucar.edu
>
> --
> 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.
--
Scanned by iCritical.
Received on Tue Oct 27 2009 - 10:36:44 GMT
