symphonick wrote
2013/8/18 lixobix lt;
arjtaplin@
gt;
symphonick wrote
The language parts still need some work. I'm not a fan of English for
everyone, and I'm not a fan of consistency either; I prefer that we
simply store the original title in the title field. Actually, I don't
2013/8/18 Lemire, Sebastien m...@benji99.ca
Hi, just finally had a chance to look at the proposal. Very good work!
A few points,
It's unclear to me, what language should untitled works be in. My opinion
and I've mentioned this before is that it should in most cases, for
constituency's
2013/8/18 lixobix arjtap...@aol.com
symphonick wrote
The language parts still need some work. I'm not a fan of English for
everyone, and I'm not a fan of consistency either; I prefer that we
simply store the original title in the title field. Actually, I don't
understand why you'd want
Updated http://wiki.musicbrainz.org/User:Symphonick/CSG_Work_Titles
I tried to add a summary, I hope it works.
2013/8/14 lixobix arjtap...@aol.com
symphonick wrote
2013/8/14 lixobix lt;
arjtaplin@
gt;
lixobix wrote
Here are some particular issues:
symphonick wrote
The work
symphonick wrote
Updated http://wiki.musicbrainz.org/User:Symphonick/CSG_Work_Titles
I tried to add a summary, I hope it works.
Thanks, this version is much clearer :)
I've a couple of minor points, but lets wait for others to respond.
--
View this message in context:
Hi, just finally had a chance to look at the proposal. Very good work!
A few points,
It's unclear to me, what language should untitled works be in. My opinion
and I've mentioned this before is that it should in most cases, for
constituency's sake, be in English first with the other languages as
2013/8/14 lixobix arjtap...@aol.com
symphonick wrote
Regarding structure, I've just done a major rewrite of the proposal, so
I'm
going to stick with this for a while. I don't understand the 7 paragraphs
bit?
The 7 paragraphs are: Title, Sources, Archaic titles, Language, Translated
2013/8/13 lixobix arjtap...@aol.com
AFIK work data is not accessible through Picard. Are we also talking
about recording titles?
Maybe not currently accessible, but I don't see why technically it wouldn't
be implemented one day. Actually, I always think as if one day all MB data
will be
2013/8/14 lixobix arjtap...@aol.com
Here are some particular issues:
symphonick wrote
The work title field in MusicBrainz should only contain the title given
by
the composer, sometimes along with a catalogue number.
contradicts
symphonick wrote
If the original title by the composer
2013/8/14 Tom Crocker tomcrockerm...@gmail.com
On 13 August 2013 22:07, symphonick symphon...@gmail.com wrote:
AFAIK artist intent pre-dates NGS (there were only tracks). Maybe
something for the documentation review team to look into?
It would be weird if you could completely replace the
2013/8/14 Tom Crocker tomcrockerm...@gmail.com
On 13 August 2013 22:07, symphonick symphon...@gmail.com wrote:
AFAIK artist intent pre-dates NGS (there were only tracks). Maybe
something for the documentation review team to look into?
It would be weird if you could completely replace the
So then it becomes a question of how much meaning the artist puts on their
work being labelled a particular way - maybe they care and maybe they
don't. If we can prove they care, we'd use their name... ?
On 14 August 2013 09:46, symphonick symphon...@gmail.com wrote:
2013/8/14 Tom Crocker
On 14 August 2013 09:48, Frederic Da Vitoria davito...@gmail.com wrote:
2013/8/14 Tom Crocker tomcrockerm...@gmail.com
On 13 August 2013 22:07, symphonick symphon...@gmail.com wrote:
AFAIK artist intent pre-dates NGS (there were only tracks). Maybe
something for the documentation review
2013/8/14 lixobix arjtap...@aol.com
Here are some particular issues:
symphonick wrote
The work title field in MusicBrainz should only contain the title given
by
the composer, sometimes along with a catalogue number.
contradicts
??
symphonick wrote
If the original title by the
2013/8/14 Tom Crocker tomcrockerm...@gmail.com
So then it becomes a question of how much meaning the artist puts on their
work being labelled a particular way - maybe they care and maybe they
don't. If we can prove they care, we'd use their name... ?
No, that wouldn't work. We have to assume
symphonick wrote
Nicknames (such as Moonlight Sonata) are not by the composer.
But how do I identify a nickname?
Moonlight Sonata is an example of a nickname.
I imagine the question there is how are we supposed to know whether the
composer actually called his sonata Named Sonata or not,
2013/8/14 Nicolás Tamargo de Eguren reosare...@gmail.com
symphonick wrote
Nicknames (such as Moonlight Sonata) are not by the composer.
But how do I identify a nickname?
Moonlight Sonata is an example of a nickname.
I imagine the question there is how are we supposed to know whether
On Wed, Aug 14, 2013 at 12:30 PM, symphonick symphon...@gmail.com wrote:
2013/8/14 Nicolás Tamargo de Eguren reosare...@gmail.com
symphonick wrote
Nicknames (such as Moonlight Sonata) are not by the composer.
But how do I identify a nickname?
Moonlight Sonata is an example of a
I've updated the nicknames section. Better?
2013/8/14 Nicolás Tamargo de Eguren reosare...@gmail.com
On Wed, Aug 14, 2013 at 12:30 PM, symphonick symphon...@gmail.com wrote:
2013/8/14 Nicolás Tamargo de Eguren reosare...@gmail.com
symphonick wrote
Nicknames (such as Moonlight
symphonick wrote
2013/8/14 lixobix lt;
arjtaplin@
gt;
lixobix wrote
Here are some particular issues:
symphonick wrote
The work title field in MusicBrainz should only contain the title given
by the composer, sometimes along with a catalogue number.
contradicts
symphonick wrote
If the
symphonick wrote
2013/8/14 lixobix lt;
arjtaplin@
gt;
lixobix wrote
Here are some particular issues:
symphonick wrote
The work title field in MusicBrainz should only contain the title given
by the composer, sometimes along with a catalogue number.
contradicts
symphonick wrote
If the
2013/8/12 lixobix arjtap...@aol.com
Archaic titles/Nicknames: Why use the disambiguation field? Surly the
modern
title/nicknames should be in brackets after the main title, in the title
field. I consider the disambiguation field should be used only when two
different entities would be easily
2013/8/12 lixobix arjtap...@aol.com
symphonick wrote
2013/8/12 lixobix lt;
arjtaplin@
gt;
symphonick wrote
Update: I've moved the untitled stuff to a separate section.
On 08/09/2013 02:12 PM, symphonick wrote:
Now that you mention artist intent, my advice about
Ah, I got it: because the sonata was originally titled in Italian. But
still, the nickname was given by a German poet, so should the nickname be
in the language of the composition or in the language it was first given in?
2013/8/13 Frederic Da Vitoria davito...@gmail.com
2013/8/12 lixobix
2013/8/13 Frederic Da Vitoria davito...@gmail.com
Ah, I got it: because the sonata was originally titled in Italian. But
still, the nickname was given by a German poet, so should the nickname be
in the language of the composition or in the language it was first given in?
If we're talking
symphonick wrote
2013/8/13 Frederic Da Vitoria lt;
davitofrg@
gt;
Ah, I got it: because the sonata was originally titled in Italian. But
still, the nickname was given by a German poet, so should the nickname be
in the language of the composition or in the language it was first given
in?
So, having re-read the style principles, I'm not sure that the title the
composer gave to the work is what's being referred to in artist intent.
http://wiki.musicbrainz.org/Style/Principle/Artist_intent#Artist_Intent
It seems like a narrower concept about special stylising - generally
spelling and
AFAIK artist intent pre-dates NGS (there were only tracks). Maybe
something for the documentation review team to look into?
It would be weird if you could completely replace the title, but not
variations in spelling...
Regarding structure, I've just done a major rewrite of the proposal, so I'm
symphonick wrote
Regarding structure, I've just done a major rewrite of the proposal, so
I'm
going to stick with this for a while. I don't understand the 7 paragraphs
bit?
The 7 paragraphs are: Title, Sources, Archaic titles, Language, Translated
titles, Nicknames, Subtitle.
I find having 7
Here are some particular issues:
symphonick wrote
The work title field in MusicBrainz should only contain the title given by
the composer, sometimes along with a catalogue number.
contradicts
symphonick wrote
If the original title by the composer is rarely used, put the modern
title in
Here's a rough version of how I would rearrange:
lixobix wrote*
Title
*
The work title field in MusicBrainz should contain the title given by the
composer, in the language of the composition. If the language of the
composition is unknown, use the language of the first performance, or
On Aug 10, 2013 9:58 AM, symphonick symphon...@gmail.com wrote:
2013/8/9 symphonick symphon...@gmail.com
2013/8/9 Alex Mauer ha...@hawkesnest.net
On 08/09/2013 02:12 PM, symphonick wrote:
Now that you mention artist intent, my advice about original titles
looks problematic too. If
2013/8/9 symphonick symphon...@gmail.com
2013/8/9 Alex Mauer ha...@hawkesnest.net
On 08/09/2013 02:12 PM, symphonick wrote:
Now that you mention artist intent, my advice about original titles
looks problematic too. If artist intent overrides, we can't change the
title given by the
updated
2013/8/9 Tom Crocker tomcrockerm...@gmail.com
As someone who knows pretty much nothing about classical, a link to
Wikipedia for urtext would be handy. Or a brief definition in brackets. The
same probably goes for quite a few of these terms. Obviously I'm unlikely
to be doing heavy
On 08/09/2013 10:46 AM, symphonick wrote:
updated
Much better!
General comments:
I think “secondary alias” is confusing (there is no mention of
“secondary” in the interface. I would use “non-primary alias” instead,
or “search hint alias” if applicable.)
There are a few places where you say
2013/8/9 Alex Mauer ha...@hawkesnest.net
On 08/09/2013 10:46 AM, symphonick wrote:
updated
Much better!
General comments:
I think “secondary alias” is confusing (there is no mention of
“secondary” in the interface. I would use “non-primary alias” instead,
or “search hint alias” if
On 08/09/2013 02:12 PM, symphonick wrote:
Now that you mention artist intent, my advice about original titles
looks problematic too. If artist intent overrides, we can't change the
title given by the composer?
Good question. We do need the title to be recognizable in the search
results.
This
2013/8/9 Alex Mauer ha...@hawkesnest.net
On 08/09/2013 02:12 PM, symphonick wrote:
Now that you mention artist intent, my advice about original titles
looks problematic too. If artist intent overrides, we can't change the
title given by the composer?
Good question. We do need the title
On 08/08/2013 05:14 AM, symphonick wrote:
OK, you asked for it ;-)
http://tickets.musicbrainz.org/browse/STYLE-232
http://wiki.musicbrainz.org/User:Symphonick/CSG_Work_Titles
Not quite finished, needs more examples. But I'm sure there will be lots
to discuss anyway.
Aside from the
On 08/08/2013 11:39 AM, Alex Mauer wrote:
On 08/08/2013 05:14 AM, symphonick wrote:
OK, you asked for it ;-)
http://tickets.musicbrainz.org/browse/STYLE-232
http://wiki.musicbrainz.org/User:Symphonick/CSG_Work_Titles
Not quite finished, needs more examples. But I'm sure there will be lots
2013/8/8 Alex Mauer ha...@hawkesnest.net
On 08/08/2013 05:14 AM, symphonick wrote:
OK, you asked for it ;-)
It also doesn’t describe how to handle work-parts with no title
(including no tempo marking).
http://tickets.musicbrainz.org/browse/STYLE-232
On 08/08/2013 01:30 PM, symphonick wrote:
I can move the non-existent fields to notes, like this is a
temporary solution, keys will eventually have their own fields.
I would actually suggest simply documenting how it should be handled
*now*. Leave the 'own fields' stuff for when we actually
As someone who knows pretty much nothing about classical, a link to
Wikipedia for urtext would be handy. Or a brief definition in brackets. The
same probably goes for quite a few of these terms. Obviously I'm unlikely
to be doing heavy editing in this area but I think we need to assume people
like
43 matches
Mail list logo
