[Data-modeling] Proposed changes for music compositionand instrument modeling

Jerry Persons jpersons at stanford.edu
Sun Nov 9 15:46:57 UTC 2008


Chris,
 
Here are pointers to the "codes" that I noted yesterday.  The strictures of
their
use with bibliographic records created by libraries are numerous.  However,
there
is likely value in the work that was done to create relatively ordered lists
 
forms of composition
  via OCLC guides http://www.oclc.org/bibformats/en/0xx/047.shtm
  + synopsis of practice by the music library at Yale
 
http://www.library.yale.edu/cataloging/music/formcomp.htm
 
instruments and voices
  via OCLC http://www.oclc.org/bibformats/en/0xx/048.shtm
  via Yale   http://www.library.yale.edu/cataloging/music/marc048.htm
 
(OCLC is producer of worldcat behind which are services that enable
libraries
 to create and share bibliographic records ... many 10s of millions of
records
 in their stable of resources
http://www.worldcat.org/whatis/default.jsp )
 
Jerry

-------------------------------------
Chief Information Architect  Green Library  Stanford CA
     phone: 650.723.9724  fax: 745.3333      94305-6004    

 

  _____  

From: data-modeling-bounces at freebase.com
[mailto:data-modeling-bounces at freebase.com] On Behalf Of Ron Wiecki
Sent: Friday, November 07, 2008 12:32 PM
To: Freebase data modeling mailing list
Subject: Re: [Data-modeling] Proposed changes for music compositionand
instrument modeling


these changes sound good to me.
Ron

Christopher R. Maden wrote: 

A few changes have been proposed to modeling of musical compositions and 

musical instruments.  I think they're pretty good, but I'd like to get 

some wider feedback before implementing them.  For the most part, these 

are new types and properties, so nothing will break, but it would be 

nice to have some confidence that we got the model right before 

implementing it.



First, for compositions:



A new type is proposed, called something like "type of composition." 

Instances would be symphony, opera, string quartet, pop song. 

Compositions would connect to type of composition.



The types of compositions would be a phylogeny pattern; a string quartet 

is a kind of chamber music, a rock opera is a kind of opera and a kind 

of rock composition.



Types of compositions would have typical instrumentations, using a CVT 

to get a number and a performance role: a string quartet typically has 

two vioins, a viola, and a cello.  A brass quintet typically has two 

trumpets, a horn, a trombone, and a tuba.



Compositions would get a new property for instrumentation as well, using 

a similar CVT.



As for musical instruments:



We currently have a Musical Instrument Company with no properties.  We 

would change this to Musical Instrument Maker.  We would grab the 

current Guitar Maker property from the Guitar type and move it over to 

Musical Instrument, and reciprocate it from Musical Instrument Maker as 

Models Produced.  We would also add a property to Musical Instrument 

Maker for types of instruments made.  That would allow us to express 

that Steinway makes pianos, and also that Steinway makes the Steinway 

Model L.  Gibson makes acoustic guitars and electric guitars, and 

specifically makes the Gibson Les Paul and the Gibson SG.



Thoughts, comments?



~Chris

  


-- 

Ron Wiecki, PhD

Library Services Assistant-Advanced Lead

Charles H. Mills Music Library

University of Wisconsin-Madison

728 State St.

Madison, WI 53706

608 890-1312

rwiecki at library.wisc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20081109/64aa685e/attachment.htm 


More information about the Data-modeling mailing list