Uploaded image for project: 'MusicBrainz Style'
  1. MusicBrainz Style
  2. STYLE-2355

Clarify the purpose of language/script for both the current schema and near-future schema changes

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Guidelines
    • None

      How does MusicBrainz envision alternate tracklists utilizing existing language/script data, if at all? (MBS-4501, MBS-2544)  Is the ideal purpose of language/script to disambiguate tracklists from each other?  Or is the purpose of language/script to quiz users on their math skills?

      e.g., VGMdb has "Japanese" and "English" tracklists that don't depend on math skills, and it makes sense to most people - less than 10% of a tracklist needs to use Japanese to be considered Japanese here: https://vgmdb.net/album/4494. If MusicBrainz applied math to these tracklists, both would be marked "English/Latin" and the fields would serve no purpose.  The only logical use case of the fields IMO is to disambiguate the tracklists.

            reosarevok Nicolás Tamargo
            yindesu yindesu
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:

                Version Package