[mb-style] RFC: Works lists (and other related changes then implied)

[Chad Wilson]

Brian Schweitzer wrote:
> Summary:
> Proposal: Add pre-NGS works lists, change the intent of CSG, modify
> the "version of " AR into an 'instance of' AR, and change the
> suggested target point for the "cover of", "parody of", "version of",
> and composition-related ARs.
>
> Developer impact: According to Robert, minimal and pretty easy,
> basically reuses code already written
>
> Benefits: Both "sides" of CSG get what they want, and the database in
> general gains the ability to begin this type of work long before it's
> eventual "true" implementation under NGS.  It also solves some of the
> AR issues we have generally, not just in classical, by providing a
> true "generic instance".
>   
Depending on the implementation, this sounds like it could become a very 
unmaintainable and regrettable hack to me if not thought through very 
clearly. Works lists for all artists in big unmaintainable lists? We 
currently can't merge, move or work with NATs at all; will the same 
apply to these works lists if they're tacked on without the concept of a 
song/work/movement actually being added?

Will taggers be disabled from tagging against them somehow? How will we 
vote on their addition/removal?

Are we proposing to write/invent all the generalised style guidelines 
that will go into defining what is a unique work and how it should be 
managed within the hack?

Most scary is that this proposal still sounds like a CSG proposal (in 
which case I wouldn't care less), yet its scope appears to be much much 
wider.

Chad / voiceinsideyou