good point. i would say make co an attribute, and executive a
sub-type, as producers/co-producers is a similar hands-on role, but
executive producers can mean a more external influence.
mind you, is it that much of a problem that you can select an
impossible combination? people would only ever use it by accident, and
if they did it can always be edited :)
On 25/04/06, Simon Reinhardt <[EMAIL PROTECTED]> wrote:
> Cristov Russell wrote:
> > I agree that the layout should be the same and that the variations should
> > be attributes.
>
> There's a problem here: they cannot both be attributes of the same type
> because attributes cannot be counter-exclusive. Meaning: if
> ProducerRelationshipType has attributes {executive} and {co-} then you could
> do the following:
> Artist executive co-produced Release.
> Do we want that? If not then still one can be an attribute and the other a
> sub-type, or both sub-types. How should we proceed?
>
> Simon (Shepard)
> _______________________________________________
> Musicbrainz-style mailing list
> Musicbrainz-style@lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
>
_______________________________________________
Musicbrainz-style mailing list
Musicbrainz-style@lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
