⇐ ⇒

[CF-metadata] Are There Best Practices for Developing New NetCDF Conventions?

From: Philip Bentley <philip.bentley>
Date: Wed, 11 Jul 2007 09:11:07 +0100

Hi John

Rather than invent another namespace separator - with potentially
unforeseen side-effects - might an alternative solution be simply to use
XML itself? For example:

  char time(record=63, time_len=21);
    time:long_name = "forecast date and time";
    time:xml_attr = "<dc:title>Field Guide To CF</dc:title>
    time:xml_attr = "<dc:creator>J R Luser</dc:creator>

or

  char time(record=63, time_len=21);
    time:long_name = "forecast date and time";
    time:xml_metadata = "<dc:title>Field Guide To
CF</dc:title><dc:creator>J R Luser</dc:creator> ... "

However, I guess the logical end game, using this approach, would be to
put ALL the CF metadata in a single attribute!

  char time(record=63, time_len=21);
    time:xml_metadata = "<cf:long_name>forecast date and
time</cf:long_name><cf:standard_name>time</cf:standard_name><dc:title>Field Guide To CF</dc:title><dc:creator>J R Luser</dc:creator> ... "

Gulp!!

Regards,

Phil



>
>
> I could see mimicking XML namespaces somewhat, by adding a prefix to attribute names, but what should the seperator charactor be? Unfortunately the ":" wont work, since right now in CDL syntax we have:
>
> char time(record=63, time_len=21);
> time:long_name = "forecast date and time";
>
> suppose you want to add an attribute "title" and indicate its in the "Dublin Core" namespace. Possible examples:
>
> char time(record=63, time_len=21);
> time:long_name = "forecast date and time";
> time:dc_title = "forecast date and time";
>
> char time(record=63, time_len=21);
> time:long_name = "forecast date and time";
> time:dc/title = "forecast date and time";
>
> char time(record=63, time_len=21);
> time:long_name = "forecast date and time";
> time:dc#title = "forecast date and time";
>
> char time(record=63, time_len=21);
> time:long_name = "forecast date and time";
> time:dc at title = "forecast date and time";
>
> etc. At the moment the "/" seems the most natural with less possible conflicts.
>
>
> this would just be a convention, but we could start a "namespace" convention page, to minimize conflicts, just listing them:
>
> Prefix Convention XML namespace Owner
> dc Dublin Core "http://purl.org/dc/elements/1.1/" Dublin Core Initiative
> thredds THREDDS "http://unidata.ucar.edu/thredds/" Unidata
> ...
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20070711/21923af4/attachment-0002.html>
Received on Wed Jul 11 2007 - 02:11:07 BST

This archive was generated by hypermail 2.3.0 : Tue Sep 13 2022 - 23:02:40 BST

⇐ ⇒