Open main menu

Wikidata:Property proposal/LilyPond notation

LilyPond notationEdit

Originally proposed at Wikidata:Property proposal/Creative work

   Done: no label (P5482) (Talk and documentation)
Descriptionmusical notation in LilyPond syntax
RepresentsLilyPond (Q195946)
Data typeString
Domainitems related in some way to music (Q638)
Allowed valuesLilyPond is too complicated for a regex-based constraint
Example 1C major scale (Q20640627)\relative c' {c d e f g a b c}
Example 2(C melodic minor scale) → \relative c' {c d ees f g a b c | c bes aes g f ees d c} (could be split as below w/ascending and descending scales)
Example 3Hindol (Q46425)\relative c' {c e fis a b a c} (applies to part (P518) Arohana (Q2011823))
Example 4Hindol (Q46425)\relative c' {c' b a fis e c} (applies to part (P518) Avarohana (Q13583589))
Example 5Hindol (Q46425)\relative c' {c e fis a b a fis e c} (applies to part (P518) pakad (Q7125406))
Example 6Tintal (Q2541238)\drums {cb hh hh cb cb hh hh cb cb hc hc sn sn hh hh cb} (subject to change)
See alsoParsons code (P1236), IMSLP ID (P839), sheet music (P3030)

Motivation

Per Mahir256's comments on Wikidata:Project chat#Proposal for a musical notation datatype for properties; see phab:T198233 (basically, Parsons code (P1236) is too limiting for most musical scales and many simple musical works). This would ideally require the creation of a new data type which renders values using the Score extension, and this would probably be the sort of mechanism for finding constraint errors. Jc86035 (talk) 05:05, 30 June 2018 (UTC)

Discussion

  • @Jc86035: Please provide an example David (talk) 09:26, 30 June 2018 (UTC)
    @ديفيد عادل وهبة خليل 2: I've added one. Mahir256 provided some other examples in the linked discussion but I don't know how they would be structured. Jc86035 (talk) 14:31, 30 June 2018 (UTC)
  •   Comment  Support Although I was proposing an entire datatype, not a specific property, for musical notation purposes., I won't oppose this proposed property, however, if its creation leads to the future creation of specific properties for specific types of snippets. Mahir256 (talk) 22:09, 1 July 2018 (UTC)
    @Mahir256: I'm aware of that, but it seemed to me that it would take much longer to create the datatype because it would require a technical change, whereas properties can be created out of thin air with consensus. Jc86035 (talk) 07:13, 2 July 2018 (UTC)
    @Mahir256: Would it be fine to have a time signature and bar lines for scales? I can't figure out how to turn them off. Jc86035 (talk) 03:16, 3 July 2018 (UTC)
    @Jc86035: I don't think it matters; the point is to show each of the scale degrees on a staff in either ascending or descending order, so as long as that's done any time signature or bar lines should be okay. Mahir256 (talk) 03:21, 3 July 2018 (UTC)
    @Jc86035: For future reference, \omit Score.BarLine will remove all barlines and \omit Staff.TimeSignature will remove the time signatures. Ebe123 (talk | contributions) 22:03, 19 July 2018 (UTC)
  •   Support I think this is reasonable, given the constraint on length and the potential for a future datatype supporting it it would probably be useful to have some examples ready to use. ArthurPSmith (talk) 17:28, 2 July 2018 (UTC)

@ديفيد عادل وهبة خليل 2, ArthurPSmith, Jc86035, Mahir256:   Done: P5482 (P5482). − Pintoch (talk) 07:56, 19 July 2018 (UTC)

Little clarification needed: This property would only include the musical notation information, assuming <score raw=False> (a default LY template to add music inside), and not requiring a full LY file to be constructed manually (which would increase the length a bit). Ebe123 (talk | contributions) 22:03, 19 July 2018 (UTC)

@Ebe123: Could you add this as a Wikidata usage instructions (P2559) statement at Property:P5482? I'm not sure how this would be phrased so I haven't added it myself. Jc86035 (talk) 13:04, 20 July 2018 (UTC)