Re: [CF-metadata] Convention attribute

2011-12-22 Thread Jonathan Gregory
Dear all The existing Unidata recommendation is OK and we could incorporate it into CF but it would help to be more precise, for instance: If the Conventions att includes no commas, it is interpreted as a blank-separated list of conventions; if it contains at least one comma, it is interpreted as

Re: [CF-metadata] Convention attribute

2011-12-22 Thread Lorenzo Bigagli
Hi all, my opinion is to keep with the current recommendation, which better supports automatic parsing and the existing conforming datasets. In particular, I would avoid any parsing rule for the conventions attribute, keeping its syntax as simple as possible (as Jonathan points out,

Re: [CF-metadata] Convention attribute

2011-12-22 Thread Nan Galbraith
Thanks Russ, Dave(s), Jonathan and Lorenzo - Thanks for the clarifications. I agree that it makes sense to require that convention names not contain spaces, and that it's easier (and more CF-like, hence better!) to parse space separated terms. Cheers - Nan The recommendation on the Unidata

Re: [CF-metadata] Convention attribute

2011-12-22 Thread Jim Biard
It is easier (not by much, code-wise) to not to allow commas as delimiters, but if you want to allow for machine-recognition of convention names, how are you going to handle conventions that have spaces in their names? Telling everyone else to get rid of spaces isn't a practical solution, and

Re: [CF-metadata] Convention attribute

2011-12-22 Thread john caron
On 12/22/2011 2:11 AM, Jonathan Gregory wrote: Dear all The existing Unidata recommendation is OK and we could incorporate it into CF but it would help to be more precise, for instance: If the Conventions att includes no commas, it is interpreted as a blank-separated list of conventions; if it

Re: [CF-metadata] Convention attribute

2011-12-22 Thread Benno Blumenthal
Russ (and thus core netcdf) has always been explicit about space-delimited conventions, so really there shouldn't be any conventions with spaces in the names. On the other hand, we have adopted the technique of using the convention name as a pattern to match against the convention attribute, so

Re: [CF-metadata] Convention attribute

2011-12-22 Thread Jonathan Gregory
Dear all This is certainly a lively thread! :-) An array of strings would be nice but I don't think we should do that because it's not compatible with the Unidata convention and it depends on the non- classic netCDF model. In this case we can probably get by without it. While we can't control