Brian Schweitzer | 3 Jun 2010 22:04
Picon

Aliases and performance names

Before I RFC to simply remove the section, I figure it's better to see if anyone knows any good rationale for keeping it.  :)

http://wiki.musicbrainz.org/Artist_Alias#When_NOT_to_use_aliases recently came up in an edit I'd voted on.  I have to admit, I don't think I've ever actually noticed that bit before.  It appears to have come in from Schika back in Feb of 2006, but I'm not aware of any discussion which led to the wiki change.

My question is, why should performance names not be aliases, if they're beneficial?  Aliases may have other uses, but I think they mostly end up used for providing the search server with "hints".  If there's a performance name or legal name that keeps being incorrectly used (where the name on the other side of the performance name AR should have been used instead), why not put that "correct" name in as an alias, so that artist comes up when people do an artist lookup?  Is there any harm to allowing performance name aliases? 

Also, left unaddressed, but how it came up in that edit - if we don't want performance names as aliases (on any other performance names, or on the legal name), do we also then not want the legal name as an alias on the performance names (again, if it is beneficial)?  The guideline is silent on that direction, only talking about the performance name end of the AR.

Brian

_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Brian Schweitzer | 3 Jun 2010 22:17
Picon

A few abandoned proposals needing champions

Checking with current champions to see how they're coming on their proposals, I've been given a heads up that the following three have been abandoned.  Is there anyone who has any interest in adopting any of these, before they're closed as abandoned?

RFC-6: Artist Type Project
RFC-87: Add 'is a project of' AR
RFC-111: Writer Relationship Type

Thanks,
Brian

PS: We still have 64 of the minor guidelines waiting at http://wiki.musicbrainz.org/Proposals#Pre-Reserved_RFCs_for_cleaning_up_documentation_and_guidelines for someone to adopt them, if anyone has some spare time.

_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Andrew John Hughes | 3 Jun 2010 23:28
Picon
Gravatar

Re: A few abandoned proposals needing champions

On 3 June 2010 21:17, Brian Schweitzer <brian.brianschweitzer <at> gmail.com> wrote:
> Checking with current champions to see how they're coming on their
> proposals, I've been given a heads up that the following three have been
> abandoned.  Is there anyone who has any interest in adopting any of these,
> before they're closed as abandoned?
>
> RFC-6: Artist Type Project

Don't really understand this one personally.

> RFC-87: Add 'is a project of' AR

There doesn't seem to be a description of this one on the proposal
page.  Is it just the AR for 6?

> RFC-111: Writer Relationship Type

This one interests me as I've run into many cases where I've had to
convert 'Written by' in liner notes into a composed AR, and wondered
if this is the right thing to do.  But I'm not sure that adding
another AR is the right solution as this could cause confusion.
Certainly, I don't see a case for having music/lyrics options on such
an AR as we already have specific ARs (composed/wrote the lyrics for)
in those cases.  A written by AR would seem to fit better as a
super-AR to these two, in the same way that 'performed' is a general
version of performed instrument and performed vocal.

>
> Thanks,
> Brian
>
> PS: We still have 64 of the minor guidelines waiting at
> http://wiki.musicbrainz.org/Proposals#Pre-Reserved_RFCs_for_cleaning_up_documentation_and_guidelines
> for someone to adopt them, if anyone has some spare time.
>
> _______________________________________________
> MusicBrainz-style mailing list
> MusicBrainz-style <at> lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
>

--
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style <at> lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
SwissChris | 3 Jun 2010 23:39
Picon

Re: Aliases and performance names

Brian, I don't see your problem. The guideline spells, slightly reformulated to make my point:: "When an individual or group have multiple "projects" under whose different names they release different musical works, you should not use aliases for (such) Performance Names. Instead, these should be added as separate artists, and linked together using Performance Name Relationship Type. Note that this is not like what Discogs does!" What's wrong with this? That's how it's done and how it should be done. Same for legal names: We add them as separate artist entries, not as aliases. Can you specify cases where you see "beneficial" use of adding such aliases?

Chris


On Thu, Jun 3, 2010 at 10:04 PM, Brian Schweitzer <brian.brianschweitzer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Before I RFC to simply remove the section, I figure it's better to see if anyone knows any good rationale for keeping it.  :)

http://wiki.musicbrainz.org/Artist_Alias#When_NOT_to_use_aliases recently came up in an edit I'd voted on.  I have to admit, I don't think I've ever actually noticed that bit before.  It appears to have come in from Schika back in Feb of 2006, but I'm not aware of any discussion which led to the wiki change.

My question is, why should performance names not be aliases, if they're beneficial?  Aliases may have other uses, but I think they mostly end up used for providing the search server with "hints".  If there's a performance name or legal name that keeps being incorrectly used (where the name on the other side of the performance name AR should have been used instead), why not put that "correct" name in as an alias, so that artist comes up when people do an artist lookup?  Is there any harm to allowing performance name aliases? 

Also, left unaddressed, but how it came up in that edit - if we don't want performance names as aliases (on any other performance names, or on the legal name), do we also then not want the legal name as an alias on the performance names (again, if it is beneficial)?  The guideline is silent on that direction, only talking about the performance name end of the AR.

Brian

_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style <at> lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style

_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Andrew John Hughes | 3 Jun 2010 23:47
Picon
Gravatar

RFC: Add microblog AR

Expected expiration date: 11th of June, 2010

This proposal concerns the addition of a new artist<-->URL and
label<-->URL AR type which allows an artist or label to be associated
with a microblogging identity such as those provided by Twitter and
identi.ca.

The proposal's wikipage can be found at:
http://wiki.musicbrainz.org/Proposal:Add_Microblog_AR
--

-- 
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8
Andrew John Hughes | 3 Jun 2010 23:54
Picon
Gravatar

Re: Aliases and performance names

On 3 June 2010 22:39, SwissChris <swisschris <at> gmail.com> wrote:
> Brian, I don't see your problem. The guideline spells, slightly reformulated
> to make my point:: "When an individual or group have multiple "projects"
> under whose different names they release different musical works, you
> should not use aliases for (such) Performance Names. Instead, these should
> be added as separate artists, and linked together using Performance Name
> Relationship Type. Note that this is not like what Discogs does!" What's
> wrong with this? That's how it's done and how it should be done. Same for
> legal names: We add them as separate artist entries, not as aliases. Can you
> specify cases where you see "beneficial" use of adding such aliases?
> Chris
>
> On Thu, Jun 3, 2010 at 10:04 PM, Brian Schweitzer
> <brian.brianschweitzer <at> gmail.com> wrote:
>>
>> Before I RFC to simply remove the section, I figure it's better to see if
>> anyone knows any good rationale for keeping it.  :)
>>
>> http://wiki.musicbrainz.org/Artist_Alias#When_NOT_to_use_aliases recently
>> came up in an edit I'd voted on.  I have to admit, I don't think I've ever
>> actually noticed that bit before.  It appears to have come in from Schika
>> back in Feb of 2006, but I'm not aware of any discussion which led to the
>> wiki change.
>>
>> My question is, why should performance names not be aliases, if they're
>> beneficial?  Aliases may have other uses, but I think they mostly end up
>> used for providing the search server with "hints".  If there's a performance
>> name or legal name that keeps being incorrectly used (where the name on the
>> other side of the performance name AR should have been used instead), why
>> not put that "correct" name in as an alias, so that artist comes up when
>> people do an artist lookup?  Is there any harm to allowing performance name
>> aliases?
>>
>> Also, left unaddressed, but how it came up in that edit - if we don't want
>> performance names as aliases (on any other performance names, or on the
>> legal name), do we also then not want the legal name as an alias on the
>> performance names (again, if it is beneficial)?  The guideline is silent on
>> that direction, only talking about the performance name end of the AR.
>>
>> Brian
>>
>> _______________________________________________
>> MusicBrainz-style mailing list
>> MusicBrainz-style <at> lists.musicbrainz.org
>> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
>
>
> _______________________________________________
> MusicBrainz-style mailing list
> MusicBrainz-style <at> lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
>

I'd go more for changing it to denote a preference for artist creation
over alias creation, without forbidding the creation of aliases.
Primarily, we want the artist's real name or commonly used performance
name to be fully present in the DB as an artist ID, but there are also
benefits to having it as an alias as well, so that it comes up in a
search.  I don't think it's a case of either/or, but that we accept
both, with a preference for artists rather than aliases.
--

-- 
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style <at> lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Paul C. Bryan | 4 Jun 2010 00:04
Gravatar

Re: RFC: Add microblog AR

+1

On Thu, 2010-06-03 at 22:47 +0100, Andrew John Hughes wrote:
> Expected expiration date: 11th of June, 2010
> 
> This proposal concerns the addition of a new artist<-->URL and
> label<-->URL AR type which allows an artist or label to be associated
> with a microblogging identity such as those provided by Twitter and
> identi.ca.
> 
> The proposal's wikipage can be found at:
> http://wiki.musicbrainz.org/Proposal:Add_Microblog_AR
Paul C. Bryan | 4 Jun 2010 00:35
Gravatar

Re: RFC: Musical Soundtrack Style: Well-known collaborations exception

Brian: Sorry it took a while to respond.

1. The "notability" criteria
I've pondered the issue of notability you raised. I'm not suggesting
that Gilbert was a "notable" lyricist and therefore somehow deserving of
credit where others are not. I'm not even trying to give him credit per
se. What I am doing is striving for the MB database to correctly reflect
names and relationships that are widely recognized worldwide. Therefore,
I deny that notability has any relevance.

2. Composers-only as a means to an end
I submit that the objectives of maintaining such specific collaborations
outweigh the objectives that the composer-only rule serves. I propose
our primary objective should be to accurately model all knowledge about
musical recordings. Managing the logistics of maintaining this knowledge
should a be secondary goal. If it is harder to maintain releases under
these duos, I believe it's worth the price.

3. Next-generation schema
With NGS, we will be able to credit multiple artists, in a specific
order. I think this will be fine for Gilbert & Sullivan and the others.
Therefore, I retract my statement about "special group". I agree, there
is not and never was a "group" called Gilbert & Sullivan. When NGS
comes, we need not have an artificial group when we can link them
individually as artists.

Given this, do you have any remaining objections?

Paul

-----Original Message-----
From: Brian Schweitzer <brian.brianschweitzer@...>
Reply-to: MusicBrainz Style Discussion
<musicbrainz-style@...>
To: MusicBrainz Style Discussion
<musicbrainz-style@...>
Subject: Re: [mb-style] RFC: Musical Soundtrack Style: Well-known
collaborations exception
Date: Sun, 30 May 2010 20:21:44 -0400

2. I am intentionally treating collaboration as artists unto themselves
        and not workarounds. The collaboration *is* the artist the work
        is
        well-known to be "by". For all intents and purposes "Gilbert &
        Sullivan"
        is a group.

        3. I disagree there's a slippery slope. My language should
        clearly
        indicate these are specific exceptions. I do not mean "some of
        which
        are". I mean specific, well-known collaborations.

I guess my biggest problem with this concept is that which the above two
express.  To my eyes, we don't make value judgements, so long as there
actually is a release.  There used to be a criterium in the guidelines
that a release had to be "worthy" of listing - I mentioned, as far as I
can recall, an example of a low-quantity release of 50 copies perhaps
not being worth entering into the database.  Again, as far as I recall,
that language has been long since removed.

We list releases some (or many) might find objectionable such as "white
pride" releases.  We list low-quantity releases with only 50, 500, or
1000 copies ever released.  We list performers who did only a single
musical thing ever in their lives.  To me, the breadth of our coverage,
and specifically our lack of a "noteable" criteria (ala Wikipedia), is
our biggest strength.

This proposal changes that, if only in what some might view as a small
way.  We'd now be specifically saying that certain composer+lyricist
collaborations are so worthy, aka "noteable", that they deserve some
kind of special treatment.

I see no need for this; we credit composer as artist simply as a means
to an end.  The "artist" field is entirely meaningless, yet all
important, as it is how we display releases.  The real "value" comes in
the ARs - and there we have both composer and lyricist ARs already.  So
I see no reason to make the simple (list under composer) confusing (list
under composer unless they're special in our eyes, in that they're on
this list). 

 
        4. To make the rationale of this proposal clear: the intent is
        for the
        MB database to reflect well-known artist attributions of work,
        and not
        create our own interpretation of artists just to satisfy some
        aesthetic,
        semantic or database normalization principle.

I don't disagree with the desire, only the result.  I'd also point out
that the majority of musical theater edits which people who don't know
the guidelines attempt are to change to various performer collabs and
such.  They rarely are attempting to move anything out of Rogers into
Rogers & Hammerstein, or Sullivan into G&S.  As I somewhat mentioned in
the edit, at least once every two months, I find a new variation on
D'Oyly being created, rather than the release going into G&S.  To wit,
we're already making a decision on how to list soundtracks of any type,
let alone just musical theater releases.  If you look at new editors
entering them, they put them in all sorts of places (frequently just
making new "Cast of Foo" artists.)  If you look on torrent sites, you
typically find all musicals dumped into VA.  If you look in stores,
they're either under VA, or in a soundtracks area sorted by title, not
composer.  So I don't see that there is some universal view on any of
these that we're counteracting...  we're simply being consistent with
the more useful of the two main "artist styles" MB in general uses - ie,
composer as artist.

        5. I am not proposing any change to opera, classical or other
        types of
        soundtracks. My proposed change is strictly limited to musical
        soundtracks.

        6. I fail to see how much uglier compilations would get. If it's
        Gilbert
        & Sullivan instead of just Sullivan as artist, and there's full
        ARs in
        place, which is composer and which is lyricist will be patently
        obvious.

Well, there never was a group named "Gilbert & Sullivan".  There was a
pair of composers named Sir Arthur Sullivan and Sir William Gilbert.
Same for Rodgers & Hammerstein.  At least our naming of the latter pair
respects this, even if it does have composer&lyricist attribution.  (The
one artist is named "Gilbert & Sullivan", rather than "Sir Arthur
Sullivan & Sir William Gilbert".  The other is already named "Richard
Rodgers & Oscar Hammerstein II").  Under NGS, this becomes especially
important, as you're proposing in your reply that we ought to not be
listing these under each person as converted & workaround artists, but
rather under "Gilbert & Sullivan" as a special entity, regardless of the
fact that there was never any such "official" entity as a group.

        7. I'm not sure how you can argue that using Gilbert & Sullivan
        as
        artist rather than just Sullivan would fragment the artist field
        further. The intent of the generic artist field is to provide
        the
        attribution that is most commonly given to a particular work. In
        the
        case of Gilbert & Sullivan, virtually all of their work is
        credited to
        the duo. To do otherwise would distort the view of who their
        works are
        actually by.

I don't know that we ever actually define artist specifically, though
I'd not really agree with that definition.
( http://wiki.musicbrainz.org/Artist doesn't actually define the
field...)

        8. The existing proposal has been open since March, if I recall
        correctly. To my knowledge It has not been accepted by the style
        council. Should my RFC proposal be accepted, I would like it to
        become
        an official guideline. If that is not acceptable, I would like
        to
        propose my text amend your proposal and be considered together
        by the
        style council.

The existing proposal has been around (in this incarnation) since Sept
of 2007, and before that was part of the soundtrack style proposal; I
only adopted it in March.  However, I don't think the proposal itself is
yet ready for proposal; as the current champion of that proposal, I'd
rather not yet propose it in an unready form...

Brian

_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Brian Schweitzer | 4 Jun 2010 00:40
Picon

Re: RFC: Add microblog AR

+1 from me as well.  :)  Thanks for finishing this one up gnu_andrew; hopefully we see something w/the Social Networking (aka Facebook) proposal soon too!  :)

For the record, this is RFC 88, and having received a second, will be able to move to RFV on 2010-06-10.

Brian

On Thu, Jun 3, 2010 at 6:04 PM, Paul C. Bryan <email-Xf9ZKMLjR+qsTnJN9+BGXg@public.gmane.org> wrote:
+1

On Thu, 2010-06-03 at 22:47 +0100, Andrew John Hughes wrote:
> Expected expiration date: 11th of June, 2010
>
> This proposal concerns the addition of a new artist<-->URL and
> label<-->URL AR type which allows an artist or label to be associated
> with a microblogging identity such as those provided by Twitter and
> identi.ca.
>
> The proposal's wikipage can be found at:
> http://wiki.musicbrainz.org/Proposal:Add_Microblog_AR



_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style <at> lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style

_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Brian Schweitzer | 4 Jun 2010 00:44
Picon

Re: A few abandoned proposals needing champions



On Thu, Jun 3, 2010 at 5:28 PM, Andrew John Hughes <gnu_andrew-IGUgQLVVQiRCV4ILt04nZQ@public.gmane.org> wrote:
On 3 June 2010 21:17, Brian Schweitzer <brian.brianschweitzer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Checking with current champions to see how they're coming on their
> proposals, I've been given a heads up that the following three have been
> abandoned.  Is there anyone who has any interest in adopting any of these,
> before they're closed as abandoned?
>
> RFC-6: Artist Type Project

Don't really understand this one personally.

> RFC-87: Add 'is a project of' AR

There doesn't seem to be a description of this one on the proposal
page.  Is it just the AR for 6?

I think so, but I'm not really clear on the "project" concept either, or if it's even still valid post-NGS-artists...
 

> RFC-111: Writer Relationship Type

This one interests me as I've run into many cases where I've had to
convert 'Written by' in liner notes into a composed AR, and wondered
if this is the right thing to do.  But I'm not sure that adding
another AR is the right solution as this could cause confusion.
Certainly, I don't see a case for having music/lyrics options on such
an AR as we already have specific ARs (composed/wrote the lyrics for)
in those cases.  A written by AR would seem to fit better as a
super-AR to these two, in the same way that 'performed' is a general
version of performed instrument and performed vocal.


Personally, I'd agree; I've never quite liked the ASIN AR, for how it really takes (at least) two other ARs and just combines them (can be purchased, cover art), making it incorrect to use them for that specific site, and makes the AR still valid even when one of those 2 isn't present (can still buy it even when there's no art...).  But if someone thinks there's merit - maybe esp if they see a way to do it where it doesn't just become a "shortcut" AR for the other 2 ARs - it's there to be adopted.

Brian
_______________________________________________
MusicBrainz-style mailing list
MusicBrainz-style@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style

Gmane