I am generally in support of this `string` attributes proposal, including UTF-8 characters. However, for CF controlled attributes, I recommend an explicit preference for type `char` rather than `string`. This is for compatibility with large amounts of existing user code that access critical attributes directly, and would need to be reworked for type `string`.
I suggest not including a constraint for scalar strings, simply because it seems redundant. I think that existing CF language strongly implies single strings in most cases of CF defined attributes. -- 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-407185855
