On 8/7/06, Nikki <
nikki@...> wrote:
> Firstly, implement the relationship:
> <a> is an alternate language/script track listing of <b>
> <b> is an alternate language/script track listing of <a>
Just curious, did you mean:
<a> is the original language/script track listing of <b>
<b> is an alternate language/script track listing of <a>
?
That would be the best pairing in my mind, because there /can/
potentially be any number of alternates.
> Once we have this, we should add the type 'virtual' to the release
> attributes. I've already spoken to mo about this and he said he'll add it
> to his restructuring proposal.
+1, sounds good.
> Some time in the future when we have NGS, these track listings can then be
> grouped together.
+1, again. Ideally, all this data should be in the same release, and
a preference will dictate which language you view in.
I'm an original language purist, regardless of whether or not I can read it.
Some people are readability purists, or can use none latin characters.
I understand that it's a significant change, and will take time. So
virtual releases are nice *in the interim* (and I already have my eye
on a TON of releases I can tag as virtual).
_______________________________________________
Musicbrainz-style mailing list
Musicbrainz-style@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
