Not to be misunderstood: I welcome the introduction of <composers>.
It's the suggested change of getting <composer> to not parse <display composer> that I feel would be consequential to <artist> & <artists> as they both currently use the same behavior.
The suggestion is valid, the way I see it too, but if taken up, won't it necessitate a change in the result/output of <artist> as well? (for uniformity/consistency)
For me, then <Composer> will be a singular value (it could be "Composer1, Composer2" though, note the use of a comma instead of a semicolon)
<Composers> will contain all 'composers', which in my case (using Picard) will automatically get populated with all the people that had some significant role in how the composition came to be.
Will <composers> be a writable tag? I got the impression that it would only be for display purposes in the virtual tag editor and other concerned areas.
I'm most probably confused or uninformed on how composers actually work - I can't understand at the moment why you don't prefer <composer> having multi-values.
If <composers> is to work the same as <artists> (as I've understood it), it will merely be a readable tag that contains all the individual <composer> tags.
The same multiple tags that you plan to add onto <composers>, I don't get why you haven't added them as individual <composer> tags yet.
I have a feeling that I missed the mark completely, but I wouldn't like for you to derail the purpose of this thread by explaining the concept of composers to me.
This wouldn't be the topic for that. Ignore my statements if they are truly missing the point.