I would also add: 1. `source` attribute when holding many filenames, or 1. `references` attribute with more than one reference identifier.
One long concatenated string is not the most appropriate container for a collection of string-valued _things_. As @Dave-Allured's recent [post](#issuecomment-407954242) and example file illustrate, specifying string encoding for the `char` datatype is burdened by the past. Adding the `string` datatype provides us a chance to do it a little bit better by explicitly stating Unicode character set and UTF-8 encoding. A larger issue lurking in the background is how to signal file content that breaks backward compatibility. This is something we discussed at the Reading workshop but no way forward was laid out. This proposal is not going to be the only backward-incompatible one. For example, [group hierarchies](https://github.com/diwg/cf2/blob/master/group/cf2-group.adoc) are coming. -- 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-408546065
