Hi. I'm opposed to the addition of a standard name. Standard names are intended to identify classes, or types of things. As I look at it, the goal is to keep implementation details out of standard names. ISO8601 is an implementation, so I think it has no place in the standard name vocabulary. Simple as that.
The units attribute is the natural (and current) place where the way the time is represented is described. Why change this? Now, if the proposal is to define a new entity, datetime, that is *not* time, and that would not be valid for use where time is used, then we could certainly add a standard name "datetime". That's my percocet-fueled thoughts on this topic. (I am recovering from sinus surgery.) Grace and peace, Jim Jim Biard Research Scholar Cooperative Institute for Climate and Satellites Remote Sensing and Applications Division National Climatic Data Center 151 Patton Ave, Asheville, NC 28801-5001 jim.bi...@noaa.gov 828-271-4900
_______________________________________________ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
