The whole point of the prefered artist order and TV Size marker is to aim for a more standardized approach and it was one of the solutions I came up with. Something that would be fair. Other options for the artist order were to use First Name Last Name, or reverse for everything. Or go back to the Eastern Artists must use Family Given thingy we had in the past.
Standardized metadata is being adapted to make it easier to apply metadata. Take a look at wikipedia. They always list singers in a First Name, Last Name basis, regardless of country of origin. Other database / fansites will always have their own preference as well. So instead of having to look for obscure website reference of what specific TV Size or Artist order preference, we attempted to build our own rules to make metadata more streamlined and simple with a standardized process.
I'll say one thing. It's a hell of a lot easier to google search the Japanese letters of a singer and look at the results.
http://puu.sh/AKn1N.jpg for example, and just simply reverse the order, rather than have to dig deep into a ton of different websites and maybe find a preferred romanization order. This is the whole point of standardized metadata.
"Delete Circles"
Circle feat. singer/composer definitely seems like the best standardization method at the moment. I'm down for this.
"This is weird"
@Oko. This could also apply if some unicode uses different characters or even capitalization options. It should definitely say metadata in general. Bombs away for example does have a release as Bombs Away on the back of an official CD cover so the user could choose either of these to use in the unicode field.
"There's a loophole here"
As discussed, yes this needs to be added.
"Source is a headache"
We could probably remove the whole theming part and just let the mapper choose any official source. But I'd still like to see a themed map use that specific source rather than something else. Say you have one themed around Hatsune Miku's Sega games but then use a SVDX source. Right, it doesn't really make sense.
Let's say we revert back to the old way. Do we want to enforce the most precise source or stick with the optional franchise part as well? We should probably make it clear this time around.
"This needs revision"
Yes.
"Robots"
"Unless the creator or singer is impossible to find" added on to the end I guess.
"Delete this"
The original idea of it meant for the base title, artist, and source fields and not for additional info as they can be adjusted for standardization or converted in either fashion.
"Regarding half-width & full-width usages of characters in the Unicode & source fields:
(Brought up to me by S o h)
Special characters should retain their original full-width/half-width characters in the Unicode fields. An exception to this is when it used for additional complimentary info like the CV section or mix descriptors. Improper usages can result in errors while searching. https://osu.ppy.sh/ss/10623085
Example using "カラフル。(Extended edit)"
The period cannot be substituted for its counterpart. "カラフル.(Extended edit)" is not acceptable.
The parenthesis may be either half or full-width. "カラフル。(Extended edit)" is acceptable.
Original width usages should still be prioritized in the unicode field when possible. "
My original post. Let's aim for this instead. Standardization edits like vs. and whitespaces should also be included in this as exempt.
I believe that covers what you have there. I need to read the updated draft when I have more time, so if something was already applied or a better method was used, then awesome.