You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to link a mm:CompositionPart to the corresponding segment of the score.
In MusicMeta there is the mm:CompositionPart class, but there is not an equivalent mm:ScorePart.
There is an mm:ScorePart, but that means something different: one ‘instrument’ part, i.e., a vertical division instead of a horizontal. The term 'part' is used with two different meanings.
This poses me problems. I have Stanzas, which are Segments of a Song, represented as mm:CompositionPart entities. But I cannot link them to the corresponding segment of the score.
This is what I would propose:
use 'part' for a score-part (i.e. an 'instrument' / 'vertical' divison)
use 'segment' for a 'horizontal' division like 'movement', 'stanza', etc.
Rename mm:CompositionPart to mm:CompositionSegment to prevent the confusion.
Add mm:ScoreSegment to the ontology with subclasses mm:ScoreMovement, mm:ScoreSection, and mm:Stanza.
Make a link between the CompositionSegment and the ScoreSegment, using mm:isRealisedIn.
The text was updated successfully, but these errors were encountered:
It would be useful to link a mm:CompositionPart to the corresponding segment of the score.
In MusicMeta there is the mm:CompositionPart class, but there is not an equivalent mm:ScorePart.
There is an mm:ScorePart, but that means something different: one ‘instrument’ part, i.e., a vertical division instead of a horizontal. The term 'part' is used with two different meanings.
This poses me problems. I have Stanzas, which are Segments of a Song, represented as mm:CompositionPart entities. But I cannot link them to the corresponding segment of the score.
This is what I would propose:
The text was updated successfully, but these errors were encountered: