History:Object Model/Track Object: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(very important differentiation (Imported from MoinMoin))
 
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This page describes the track or title object and its role in the [[Object Model|ObjectModel]].
=The Track Object=

This page describes the track object and its role in the [[Object Model|ObjectModel]].


==Definition==
==Definition==


A track is the result of the whole music production process that started with the idea described in the [[Object Model/Song Object|../SongObject]]. The track is defined by a name and a position on a [[Object Model/Release Object|../ReleaseObject]] (e.g. a track number on a CD) on a release medium. The [[Object Model/Track Object|../TrackObject]] defines a single audible object on a ''specific'' [[Object Model/Release Object|../ReleaseObject]].
A track is the result of the whole music production process that started with the idea described in the [[Object Model/Song Object|../SongObject]]. The track is defined by a name and a position on a [[Object Model/Release Object|../ReleaseObject]] (e.g. a track number on a CD) on a [[Object Model/Medium Object|../MediumObject]]. The [[Object Model/Track Object|../TrackObject]] defines the smallest directly identifiable and unsharable object on exactly one [[Object Model/Release Object|../ReleaseObject]].


Note, that the track ''object'' itself does not contain any information about audible data. Instead the track object ''belongs to exactly one'' [[Object Model/Master Object|../MasterObject]], that encapsulate the related audio data.
The following is [[User:DonRedman|DonRedman]]'s point of view and not necessarily shared by others
<ul><li style="list-style-type:none">Note that the track ''object'' itself does not contain any information about audible data. Instead the track object ''belongs to exactly one'' [[Object Model/Master Object|../MasterObject]]. It is this master that defines the audio that is stored on the track. At the same time a track object ''belongs to exactly one'' [[Object Model/Release Object|../ReleaseObject]]. That means that with this model, we will never merge tracks (except when merging releases). We will only merge higher level objects like the [[Object Model/Master Object|../MasterObject]], the [[Object Model/Performance Object|../PerformanceObject]], or the [[Object Model/Composition Object|../CompositionObject]]. The ..[[Track Object|TrackObject]] itself just contains this info:
* The related (single) [[Object Model/Master Object|../MasterObject]]
* appears on (this [[Object Model/Disc Object|../DiscObject]] of) this related (single) [[Object Model/Release Object|../ReleaseObject]]
* at position [propperty]
* under the [[Track Title|TrackTitle]] [propoerty or relation to a [[Object Model/Track Title Object|../TrackTitleObject]]?]
* attributed to the artist of this (single) [[Object Model/Attributed Name|../AttributedName]].


Again: Each track is unique with respect to its [[Object Model/Master Object|../MasterObject]] '''and''' [[Object Model/Release Object|../ReleaseObject]]. That means there is only one instance of a track or in other terms: 2 tracks belong to the same [[Object Model/Track Object|../TrackObject]], if
</ul>
# They belong to the same [[Object Model/Medium Object|../MediumObject]].

# They belong to the same [[Object Model/Master Object|../MasterObject]].
[[User:Fuchs|Fuchs]], however wrote:
# They have the same attributes (track title, position on the medium, etc.)
<ul><li style="list-style-type:none">As long as the audio data '''and''' the title, artist, and other metadata of two tracks are 100% identical they belong to the same [[Object Model/Track Object|../TrackObject]].
</ul>

Which suggests that he has a different concept of a track.


==Boundaries==
==Boundaries==
Line 27: Line 16:
===Boundaries to the MasterObject===
===Boundaries to the MasterObject===


The master that isn't directly accessible by the public needs to be used to create the track on a release. When a piece of music can be baught and listened to, it is a track on a release.
The master that isn't directly accessible by the public needs to be used to create the track on a release. When a single identifiable piece of music can be listened to, it is a track on a release.


===Boundaries at the bottom===
===Boundaries at the bottom===
Line 49: Line 38:
</ul>
</ul>


===Relationships to the ArtistObject===
[[Category:To Be Reviewed]] [[Category:Development]]

There is no direct relationship of a [[Object Model/Track Object|../TrackObject]] to an [[Object Model/Artist Object|../ArtistObject]]. As a track described the representation on exactly one release and an artist identifies a person, we need to be able to relate the track to a textual representation of an artist, that might be different for different releases. Or simply, an artist can have different names on different releases and we want to relate the track to the exact name that was used for the release the track belongs to.

Instead of relationships to [[Object Model/Artist Object|../ArtistObject]]<code><nowiki></nowiki></code>s we use:

===Relationsships to the ReleaseArtistObject===

* '''A [[Object Model/Track Object|../TrackObject]] is related to ''1 to many'' [[Object Model/Release Artist Object|../ReleaseArtistObject]]<code><nowiki></nowiki></code>s'''
<ul><li style="list-style-type:none">[[Image:Attention.png]] 1 to many or exactly 1, this depends on the implementation of the release artist The release artist of a track is the representation of an artist in relation to the release the track belongs to. In other words, a track is related to an artist string, that is identical to what is "on the cover" of its release.
</ul>

[[Category:History]] [[Category:Development]]

Latest revision as of 20:07, 25 October 2011

This page describes the track or title object and its role in the ObjectModel.

Definition

A track is the result of the whole music production process that started with the idea described in the ../SongObject. The track is defined by a name and a position on a ../ReleaseObject (e.g. a track number on a CD) on a ../MediumObject. The ../TrackObject defines the smallest directly identifiable and unsharable object on exactly one ../ReleaseObject.

Note, that the track object itself does not contain any information about audible data. Instead the track object belongs to exactly one ../MasterObject, that encapsulate the related audio data.

Again: Each track is unique with respect to its ../MasterObject and ../ReleaseObject. That means there is only one instance of a track or in other terms: 2 tracks belong to the same ../TrackObject, if

  1. They belong to the same ../MediumObject.
  2. They belong to the same ../MasterObject.
  3. They have the same attributes (track title, position on the medium, etc.)

Boundaries

Boundaries to the MasterObject

The master that isn't directly accessible by the public needs to be used to create the track on a release. When a single identifiable piece of music can be listened to, it is a track on a release.

Boundaries at the bottom

There are no boundaries at the bottom. Each ../TrackObject is unique in audio and meta-data.

Relationships

Relationships to the MasterObject

  • The master represents the audio data that the track contains, so there can be only one master for each track.

Template:Include

Relationships to the ReleaseObject

  • The track is defined by its position on a unique release.

Relationships to the ArtistObject

There is no direct relationship of a ../TrackObject to an ../ArtistObject. As a track described the representation on exactly one release and an artist identifies a person, we need to be able to relate the track to a textual representation of an artist, that might be different for different releases. Or simply, an artist can have different names on different releases and we want to relate the track to the exact name that was used for the release the track belongs to.

Instead of relationships to ../ArtistObjects we use:

Relationsships to the ReleaseArtistObject

  • Attention.png 1 to many or exactly 1, this depends on the implementation of the release artist The release artist of a track is the representation of an artist in relation to the release the track belongs to. In other words, a track is related to an artist string, that is identical to what is "on the cover" of its release.