Based on the expressed concern so far for backward compatibility I suggested the former: always be of type `char`. Leave the character set and encoding unspecified since the values of those attributes are controlled by the convention.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/141#issuecomment-407759059
