"Michael Smethurst" <[EMAIL PROTECTED]> writes: > <snip>They should never be the exact same audio object with different > [isrc] codes.</snip> > I'm just not sure this happens in practice. According to our production > staff ISRC codes are not as reliable as intended > > Don't think i was too clear on the description of the live stuff > What we wanna do is provide set lists eg glastonbury > The band may play some songs off singles, some off albums and maybe a > cover or two > These "songs" can't be mapped to "tracks" on releases cos they're not > the same audio object. So we need to model a concept of song as an > abstract entity that may have multiple renditions as tracks > At the mo no music data providers model the song; only tracks > This is one of the changes we're considering asking brainz for > > Any more suggestions?
You could have songs, performances (renditions?) and tracks. You *might* have multiple tracks from a single performance. Consider all those deadheads with their 8 tracks of the same happening. An orchestra might choose to release multiple tracks of the same performance for remixing purposes. -- Nic Ferrier http://www.tapsellferrier.co.uk for all your tapsell ferrier needs - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
