On Wed, Apr 7, 2010 at 1:15 PM, jacobbrett <[email protected]> wrote:
> > This is RFC-43. It will expire 2010-04-14. > > Following previous discussion[1], I have refined and lessened the scope of > this style guideline. > > 1. The defining sentence of a release has been changed from "A Release > Event > is the event when a Release is first sold on a market." to "A Release Event > refers to the initial availability of a unique Release.". > 2. The field definitions have been refined to describe how the user will > interface with the NGS editor (as this is a work in progress, it may not be > completely accurate). > 3. In addition to above, I've tried to avoid (re)defining what each of > these > fields represent in MusicBrainz, instead focussing on what they are in the > context of packaging. > 4. Information on locating release details has been moved to How to > Identify > Release Details[2] (in development). > 5. 'Details of the Release Country' has also been moved to How to Identify > Release Details[2]. > > Please see the note at the bottom of this guideline regarding alternate > titles[3]. > > Thank you > > [1] http://n4.nabble.com/RFC-Release-Event-Style-td1637725.html > [2] > http://wiki.musicbrainz.org/User:Jacobbrett/How_to_Identify_Release_Details > [3] http://wiki.musicbrainz.org/User:Jacobbrett/Release_Event_Style I apologize if this sounds harsh, but I find it quite frustrating that your first line starts off stating that "A Release Event refers to the initial availability of a unique Release". Like I mentioned in [1], "release events" as you're referring to them simply don't exist. The closest thing to a "release event" in NGS is a release, and a release is usually released on a specific date, there is no "initial availability" of a release. I'd like to point you to a specific section in that previous email of mine [1]: > The data being covered on the page could be referred to by many different > names (information, properties, attributes, etc.) but I don't think the page > title needs to include that term in it. > > The way I see it we have two options, either we drastically change the new UI > to replace all instances of the term "release" with "release event" and then > title this page "Release Event Style", or we keep the new UI the way it is > and we title the page "Release Style" (because that is what it's describing - > the entire release). > > I strongly suggest the latter :) > > First, just to clear something up, I was joking when I said that there are two options. A terminology change such as replacing "release" with "release event" would be much like replacing "release group" with "release ensemble", it's not going to happen. Second, I'm not sure why I proposed such a ridiculous name such as "Release Style", the page that you're creating (after all necessary corrections) would just replace the Release page in the wiki. Putting the rest of the content aside (Brian's done a very extensive job there) and just looking at your introduction it seems to me that you still don't need understand what a release is, and/or what specifically a user needs to understand about a release. I've been creating more accurate descriptions for all the entity pages, and while they are still a WIP (like works :( ), I'm quite happy with how the release group and release descriptions have turned out so far. Since you're rewriting the release page I thought I should share them with you. [2] I strongly suggest you start your release page with the description I've written and go from there. [1] http://lists.musicbrainz.org/pipermail/musicbrainz-style/2010-March/009092.html [2] http://wiki.musicbrainz.org/User:PavanChander/Database_Overview Pavan Chander
_______________________________________________ Musicbrainz-style mailing list [email protected] http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
