@DocOtak, thanks for restarting this. In light of past difficulties, I move to split the issue.
I think it would be possible to break out the more difficult parts of this topic into new and separate issues. I suggest that this issue #141 be narrowed to only a single essential ingredient: scalar string-type attributes as an alternative for traditional character-type attributes. Can we agree to move the following to new Github issues, and focus for now only on legalizing scalar string-type attributes? * Array string-type attributes. * All discussion of character sets, UTF-8 or otherwise. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/141#issuecomment-598909876 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
