I did choose to not use other standards as the main features of Meelo (multiple album/song versions, getting B-Sides, etc.) are not supported by them.
The server's API follows its own design.
It makes sense, since Meelo's main strength is the rich metadata model. You'd have to butcher it into a lowest-common-denominator format, which in many of these subtle cases would be missing the entire point.
I think people who would rather use streaming apps should just stick to Jellyfin or Navidrome.
I still prefer to listen to music through a native/dedicated app on desktop (and definitely on mobile). As much as I don't like Electron, Cider went with it and it's not that bad.
I think you'll find the population anal enough about different album versions and the one who can't do without gapless playback overlaps significantly.
I'll add that proper ReplayGain handling is also a must.
I'm not sure if I understood your question, so here's a quick brief on how I handle this:
If the tag (from the path or the embedded metadata) is 'Compilation' or any other string specified in the settings, the album will have no main artist. Such albums cannot be grouped by series or sth (although that would be a great idea for version 4.0).
As of today, on the web app, there is no page that lists all 'compilation' albums.
Typically with these, I put the Album Artist as "Diverse System" (this is the name of the "record label"). Each track will have it's own artist. In Jellyfin, there is an Album Artist tab inside a music library, which will group these albums into the Diverse System artist, and artists that only appear as a member of one of these albums will not appear in that tab (as they aren't the artist of an album).
So a bit different from a Compilation as you state it.
This should be compatible, as a song's artist does not have to be the same as an album's artist.
A song has to have an artist, an album does not.
In Meelo, an artist that does not have an album but only songs would not be listed in a library's artist list for example.
