Wikidata:Property proposal/motif (music)
motif
[edit]Originally proposed at Wikidata:Property proposal/Creative work
Description | short recurring melodic or rhythmic musical phrase in this musical work, in LilyPond syntax |
---|---|
Represents | motif (Q908349) |
Data type | Musical Notation |
Domain | musical work (Q2188189) |
Example 1 | Symphony No. 5 (Q188709) → |
Example 2 | String Quartet (Q1635257) → |
Motivation
[edit]Most musical motifs are not already notable on their own, so it may be appropriate to simply add them directly to the items for the compositions which contain them. LilyPond is not a canonical format for musical notation by any means, but neither is MathML for mathematical notation, so I think solely using LilyPond to represent motifs would be appropriate.
I don't know what conventions would be appropriate for this property, so I've just copied and pasted the LilyPond code from w:en:Symphony No. 5 (Beethoven) as a rough example. If playback is enabled then rough tempo markings might also be appropriate for pieces that don't have BPM measurements.
The only LilyPond properties that presently exist are the sandbox property and the generic property. (The datatype was only enabled on Thursday.) I'm not sure if this property should also encompass other related concepts such as figures, ostinati and riffs.
I don't think there would be any significant issues with using this for copyrighted works, since the property would only indicate short excerpts.
It could be possible to create new items for all musical motifs and use a generic property to indicate their notation. However, it's probably extremely rare for two otherwise unrelated works to coincidentally share a motif (I could be wrong), so there are probably few advantages to be gained from linking compositions through their use of the same motif. Jc86035 (talk) 10:57, 17 March 2019 (UTC)
Discussion
[edit]- Support David (talk) 06:55, 18 March 2019 (UTC)
- Support No need for items for the motifs themselves I would think. ArthurPSmith (talk) 14:37, 18 March 2019 (UTC)
- Support --Tinker Bell ★ ♥ 17:37, 18 March 2019 (UTC)
- @ديفيد عادل وهبة خليل 2, ArthurPSmith, Tinker Bell: I thought a bit about this, and I think the proposed property's scope is too narrow and would result in too many properties being created for similar purposes. Do you think a "quotation or excerpt (music)" property would be better? A required object of statement has role (P3831)/has characteristic (P1552) constraint (values e.g. motif (Q908349), melody (Q170412)) could be applied to this property. This would also have the advantage of allowing multiple role qualifiers for each statement. Jc86035 (talk) 13:59, 19 March 2019 (UTC)
- A separate proposal for a musical quotation/excerpt I think would be ok, but it seems to me "motif" is a pretty specific use that deserves its own property. ArthurPSmith (talk) 14:21, 19 March 2019 (UTC)
- @Jc86035: Same situation, could you give more examples so I can create the property? Ederporto (talk) 02:34, 11 April 2019 (UTC)
- @Ederporto: I've added one more. (Only the content between the
<score>...</score>
tags should be used in the statements.) Jc86035 (talk) 10:33, 11 April 2019 (UTC)- @Jc86035, ديفيد عادل وهبة خليل 2, ArthurPSmith, Tinker Bell: Property musical motif (P6686) Done. Good contributions, Ederporto (talk) 16:15, 13 April 2019 (UTC)
- @Ederporto: I've added one more. (Only the content between the