|
Pie in the Sky! |
|
This page describes (or contains discussions about) major new evolutions that will likely require dramatic changes to the server codebase (what we usually refer to as NGS), or an important additional quantity of development work. It's unlikely that these new features will make it before a couple more server releases. While you're definitely encouraged to participate and help in enhancing these propositions, this document is probably not meant for complete newcomers, and definitely can't serve as any kind of end-user documentation for the currently running system. |
Description
A MusicalWork means a musical composition, that is, the instructions to performers about what sounds and silences to perform on what instruments.
It does not refer to the act of performing music. It does not refer to the sounds of the music — that is a MusicalPerformance. It does not refer to the recorded signal fixing the performance in a persistent medium. That is a TrackMaster or a Track.
The concept of MusicalWork is important in ClassicalMusic, because in many cases there are multiple recordings of the same MusicalWork. The ClassicalStyleGuide specifies that ReleaseTitles and TrackTitles identify the MusicalWork.
As of January 2008, the MusicBrainzDatabase didn't have any entities to represent a MusicalWork directly. However, the NextGenerationSchema is planned to do so.
See also:
![[WWW]](/-/musicbrainz/img/moin-www.png){kind=small}
http://en.wikipedia.org/wiki/Musical_workDiscussion
Jim, while I quite understand your notes here, I think this definition is a bit on the vague side. It would be quite useful to identify exactly which object(s) within the ObjectModel (as revised by MusicBrainzSummit8 in the finalized NextGenerationSchema) this refers to. -- BrianSchweitzer 2008-02-07 16:55:00