While the idea of work inheriting seems pretty reasonable, I wonder how it would work for stuff like song-cycles, where each song is actually a piece in its own right. Or to things like "2 piano sonatas, Op. whatever". Would we store the information at the "group" level, or at each work? Does this only count for movements?
Also, in general, this shouldn't be made a guideline until a proper way of handling works is developed. Although I understand the interest on removing what is seen as data duplication, right now the machine has no clear way of knowing it *is* data duplication and won't be able to inherit the info for things like composer tags (or for display in the page for that matter). On Fri, Oct 28, 2011 at 3:30 PM, Rupert Swarbrick <[email protected]> wrote: > Jim DeLaHunt <[email protected]> writes: >> Summary: >> >> I propose defining an inheritance of relationships between any two Works >> joined by a Parts Relationship Type. This makes explicit the logical >> consequence of the Parts Relationship Type's meaning: that one Work entity >> is a part of another Work entity. Any Relationship which in any of the >> Work-relatedRelationship Family has its meaning inherited (except Parts >> Relationship Type, that would be too recursive). >> >> This proposal is implemented by three changes: >> >> 1. Adding a new page Style/Work/Partial Works Relationship Inheritance, with >> the text below >> 2. Adding a stub entry (below) to Style/Work (presently empty) to point to >> Style/Work/Partial Works Relationship Inheritance >> 3. Adding text (below) to Parts Relationship Type, summarising and referring >> to Style/Work/Partial Works Relationship Inheritance > > This is a great idea! Indeed, it would be even better if the MB software > had some support for showing this eg. a slightly differently formatted > copy of the inherited AR or something. > > About your question of whether all artist-work relationships should be > inherited: I think so, given the current list, and I can't think of any > plausible new artist-work relationships that would break this... > > Definitely a +1 from me. > > > Rupert > > _______________________________________________ > MusicBrainz-style mailing list > [email protected] > http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style > -- Nicolás Tamargo de Eguren _______________________________________________ MusicBrainz-style mailing list [email protected] http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
