- From: Robert Patterson <robert@robertgpatterson.com>
- Date: Thu, 10 Apr 2025 16:51:13 -0500
- To: public-music-notation@w3.org
- Message-ID: <CAACncevymvDnHd5dRTW785FqN3XW1a7cfsc3JxQs55PGd5jMYw@mail.gmail.com>
I think these changes are terrific. Thank you for taking the time to consider and decide about them. I notice that all the changes have been applied to the schema except the optional `type` value for events. Will that be coming soon? I am nearing a release, and I was waiting for these changes. If the optional type will be coming soon, I'll wait for it. Thanks again, Robert On Thu, Apr 10, 2025 at 2:02 PM W3C Community Development Team < team-community-process@w3.org> wrote: > MNX > > > > The slur object no longer has a location key. Adrian deleted an example > that contained an incomplete slur since it should be reworked into a > laissez vibrer tie example in future. The target object is now required for > slurs. We have also defined some initial values for line type, which is > used by slurs. Together, this addresses discussion #402. > > > > Octave lines are now encoded in an array, like clefs, rather than being > embedded in the sequence. The example document has been updated. It is also > now possible to specify that the octave line applied only to a single > voice, by specifying the voice ID. This closes issue #413. We also elected > to specify that octave lines can shift by 1, 2, or 3 octaves; previously > this was limited to 2 octaves up or down. > > > > Adrian also made corresponding changes for dynamics, so they are also now > stored in an array in the part measure object instead of being embedded in > the sequence. This closes issue #408. Adrian has added an example document > for dynamics to illustrate this change. > > > > sequence now contains only a handful of object types, which feels good. We > agreed that type should be made optional for objects in sequence, > defaulting to event, so that we do not need to redundantly encode the type > for events, which make up the vast majority of objects in sequences. We > also discussed issue #391, and agreed that a new sequence content object > should be exposed to provide a common way of describing the content of > sequence and tuplet. > > > > Adrian has also changed the duration key within the space object to use a > fractional rather than integral value, which makes it more expressive and > allows it to specify any valid musical duration. This addresses issue #400. > > > > We talked for a while about grace index, sparked by a discussion about how > to differentiate between an octave line that ends before the grace notes > before a primary note versus how to include the primary note and all its > grace notes. We are leaning towards making the implicit default value of > grace index null, which would replace the current default value of > undefined. > > > > Next meeting > > > > The next co-chairs meeting is scheduled for Thursday 24 April 2025. > > > > ---------- > > This post sent on Music Notation Community Group > > > > 'Co-chair meeting minutes: April 10, 2025' > > > https://www.w3.org/community/music-notation/2025/04/10/co-chair-meeting-minutes-april-10-2025/ > > > > Learn more about the Music Notation Community Group: > > https://www.w3.org/community/music-notation > > >
Received on Thursday, 10 April 2025 21:51:29 UTC