Hi Jonathan
Including slashes in standard names (e.g. lake/river/sea) doesn't strike me as a good idea as the Standard Name strings are used in URLs where slashes cause problems. Other delimiters to avoid are '%' and '?'
Either stick with underscores, try '|' (which signifies 'or' in some usage) or go with something like lakeOrRiverOrSea.
Cheers, Roy.
>>> Jonathan Gregory <j.m.gregory at reading.ac.uk> 03/13/08 9:52 AM >>>
Dear Heinke
> water_vapor_mixing_ratio is more precisely but has the same definition as
> humidity_mixing_ratio.
I agree that water_vapor_mixing_ratio would be clearer.
> > Maybe the solution to our problem with "sea" is to use the rather long, but
> > explicit, "sea/lake/river" as a replacement for "sea" is standard names.
> >
> We would prefere Roy's proposal (25.2) to say water_body. In the
> standard name description this could be explained:
> water_body means sea, lake and river.
I feel that your explicit description is clearer; water_body is less obvious
to me. For instance, to replace the current standard_name
sea_water_temperature
the choice is between
lake/river/sea_water_temperature (I put them in alphabetical order)
or
water_body_water_temperature
The former appears clearer to me, and is only slightly longer. I wonder what
other people think. Of course, there is also the option (assumed implicitly
up to now) to define "sea" to mean lake/river/sea, but I think that general
opinion is less happy with that.
Cheers
Jonathan
_______________________________________________
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 Thu Mar 13 2008 - 04:11:45 GMT
