[Data-modeling] Proposed changes for music composition and instrument modeling

[ariel backenroth]

i'm responding to Jerry Persons post 11/9/08 regarding codes for  
composition type and orchestration.

orchestration:

the  OCLC guides http://www.oclc.org/bibformats/en/0xx/048.shtm are  
comprehensive and flexible.  i like that they also call out an  
instrument/voice role (solo, orchestra, accompaniment, narrator).  for  
modeling concertos this would provide users with the flexibility of  
simply describing the instrumentation 1 violin as solo, with 1  
orchestra accompaniment, or as a 1 violin solo and calling out each  
other instrument, count with a role of orchestra (if the orchestration  
is particularly interesting).  so this would imply that there'd be an  
instrumentation triple for:
- instrument
- their count,
- their role (solo | orchestra | accompaniment | narrator | chorus |  
offstage brass http://www.freebase.com/view/guid/9202a8c04000641f800000000942fafd)

another thing the OCLC codes capture is the relationship of the player  
to the instrument (whether an instrumentalist is doubling on another  
instrument).  i'm not sure this is as much of a concern since this can  
vary by performance and can be captured on the musical performance  
type for particular performances.

composition type:

i think OCLC guides http://www.oclc.org/bibformats/en/0xx/047.shtm do  
provide a comprehensive list of composition forms that could adopted  
(by pointing to the corresponding topic within freebase - there are  
likely topics for all of these).  it would also be helpful to have  
piano trio/string trio as values for this property, rather than just  
trio sonata.  this seems rather simple and straightforward.  perhaps  
having a typical instrumentation for some of these would be useful as  
well.

ariel


On Nov 9, 2008, at 5:26 PM, data-modeling-request at freebase.com wrote:

> Re: [Data-modeling] Proposed changes for music	compositionand
> 	instrument modeling