Connecting a mo:Label to a mo:Release
Steven Gravell
connections I can make between an mo:Label and anything else to give
ownership/distrubution connections to a mo:CD/mo:Release and so on.
What is the best way of doing this? I read some potentially new
additions to the schema in the revision14 page on the wiki, but is
there anything stable I should be using?
Yves Raimond
out the relationships between albums, releases and labels. There
should be a new property mo:release_label linking a release and a
label (which I have been using in the RDF mapping of Musicbrainz at
http://dbtune.org/musicbrainz/). I am starting to think we should get
the obvious things in the todo list (including that one) in a first
new release as soon as possible, and release the complex things later
(the release-specific things that have been discussed on that mailing
list lately).
Cheers,
y
> >
>
Steven Gravell
I've got another question which I've just remembered about too, which is the distinguishing of releases having tracks on compared with having signals/recordings. When I was at last.fm we switching to having a release own a sequence of recordings (similar to that of mo:Recording/Signal) which represented the audio file and then linking that 1:1 to a track which was mostly used to attribute the recording with a title and an artist. In mo: it seems that this is the other way around, and a release has many tracks (with titles) and then a track may have a signal, but what's to say that the signal for that track is the correct one when a track could indeed have different distinct recordings (live, etc)? Or does each of these have to have a separate distinct mo:Track? (which I don't want to do due to duplicate track names).
steve
--
steve - http://mokele.co.uk/
Steven Gravell
Yves Raimond
> Great, thanks a lot for clearing that up. I'll adopt release_label then.
>
> I've got another question which I've just remembered about too, which is the
> distinguishing of releases having tracks on compared with having
> signals/recordings. When I was at last.fm we switching to having a release
> own a sequence of recordings (similar to that of mo:Recording/Signal) which
> represented the audio file and then linking that 1:1 to a track which was
> mostly used to attribute the recording with a title and an artist. In mo:
> it seems that this is the other way around, and a release has many tracks
> (with titles) and then a track may have a signal, but what's to say that the
> signal for that track is the correct one when a track could indeed have
> different distinct recordings (live, etc)? Or does each of these have to
> have a separate distinct mo:Track? (which I don't want to do due to
> duplicate track names).
Well, a signal in MO can express two different things: the master
signal (which will be shared across all releases of that track, e.g.
on the single and the album etc.) and a signal encoded in, say, an
audio file. So you can have something like that:
:signal mo:published_as :track1_on_single, :track10_on_album .
:track1_on_single mo:available_as :my_mp3 .
:my_mp3 mo:encodes :my_signal_with_lots_of_compression_artefacts .
Different versions (e.g. live, studio etc.) will be two different
signals (one of them is the outcome of a performance and one of them
is the outcome of a recording session).
Cheers!
y
Steven Gravell
This to me seems rather confusing since it's actually both the signal and track that seems the same, it's just the mo:trackNum(s) in the mo:Record that end up making this relationship unique. If they were two different recordings by the same name I would be pushed to represent them as the same Track but 2 different Signals, which seems to be the exact opposite of what I am now coming to think MO wants me to do. Either that or I've still got it wrong.
steve
Yves Raimond
> before is that Tracks represented a similar item to what we used at Last.fm,
> which was just a distinct name for a song by an artist that can exist as
> different recordings on different releases (but can exist on neither). But
> what I'm understanding now is that each audible recording that is the same
> on a single and on an album are infact represented by 2 different Tracks?
> (since you represented the :signal as being published as :track1_on_single
> and :track10_on_album).
Yes, if it is coming from the same master signal, then you'd have one
signal for two tracks. A track in MO is a track within a particular
album (hence the mo:track_number property on tracks).
>
> This to me seems rather confusing since it's actually both the signal and
> track that seems the same, it's just the mo:trackNum(s) in the mo:Record
> that end up making this relationship unique. If they were two different
> recordings by the same name I would be pushed to represent them as the same
> Track but 2 different Signals, which seems to be the exact opposite of what
> I am now coming to think MO wants me to do. Either that or I've still got it
> wrong.
>
I think you're mixing the "song" (the actual work - mo:MusicalWork)
and a track. A track is something which is a part of a particular
album (e.g. track 1 of Nevermind). A song is a work (e.g. Smells like
Teen Spirit), which can be performed and recorded multiple times
(live, studio, covers, etc.), in a variety of settings. All these
recordings will end up producing different signals, which may be
released as part of more than one manifestation.
Cheers!
y