History:Object Model/Composition Object

From MusicBrainz Wiki
Revision as of 01:03, 18 November 2005 by DonRedman (talk | contribs) (god, will that work? (Imported from MoinMoin))
Jump to navigationJump to search

The Composition Object

This page describes the composition object and its role in the ObjectModel.

Definition

A Composition is the object below the ../SongObject.

Actually a composition is an object of national law. A composition is considered a "work" of art and is copyrightable. We could use that definition. However they differ slightly from nation to nation. For now we can define a composition as something that can be put down on a score.

Boundaries

Boundary to the SongObject

A song becomes factual when the artists start composing and writing lyrics. This is more "touchable" than the mere idea of the song, as you can see the lyrics and notes. Therefore as soon as the song becomes an object of the real world (not the world of ideas[1], it is a composition.

Boundary to the Arrangement Object

That is already slightly tricky. We must add this.

Relationships

Relationships to the SongObject

  • [exactly 1] For sake of simplicity we can say that a ../CompositionObject can only be based on one ../SongObject. Since the song is an abstract idea, we can say that a composition is based on exactly one song. There is an idea to every object of the real world[2].
  • Or should we allow a composition to be based on multiple songs? At this point the abstract idea of a song is becoming wobbly. We'd need some examples here.

{{Include|ObjectModel/SongObject||from="^=== Relationships to the CompositionObject ===$"| to="^[[Include"}}

Relationships to the ArrangementObject

  1. That is Plato
  2. That too. We really have 2400 years of philosophical backing for this ObjectModel :-)