[Data-modeling] keeping Freebase topics and Wikipedia pages in sync; uncertainty in who is the composer

[Jeff Prucher]

> In doing this upload of Bach cantata data into Freebase, I 
> ran into the issue of how to deal with work misattributed to 
> J.S. Bach.  According to
> http://en.wikipedia.org/wiki/BWV:  "The BWV catalogue is 
> occasionally updated, with newly discovered works added at 
> its end, though spurious works do not have their numbers 
> removed."  An example is BWV 15: 
> http://www.freebase.com/view/en/denn_du_wirst_meine_seele_nich
> t_in_der_holle_lassen
> -- "BWV 15, is a church cantata spuriously attributed to 
> Johann Sebastian Bach but most likely composed by Johann 
> Ludwig Bach."  What I did to model this is:
> 
> 1) still have /base/jsbach/bach_composition/bwv = 15 for 
> /en/denn_du_wirst_meine_seele_nicht_in_der_holle_lassen  -- 
> but not the type /base/jsbach/bach_composition
> 
> and
> 
> 2) go ahead with setting     /music/composition/composer  to   Johann 
> Ludwig Bach

Hmm. This is tricky. You (via MQL) assign any property to a topic without
adding the property's type, but the client might not display this
particularly well (if at all). It seems like the only purpose of the Bach
Composition type is to assign a BWV#; maybe the type should be renamed BWV
Composition to allow for the false attributions. Users wanting to find
compositions by Bach will still be able to do so by filtering by
/music/composition/composer = J. S. Bach, but we'd gain the ability to query
for all non-J.S. Bach-composed works in the BMV catalog.

Jeff