- From: Jeremy Sawruk <jeremy.sawruk@gmail.com>
- Date: Wed, 23 Aug 2017 11:59:02 -0400
- To: Michael Good <mgood@makemusic.com>
- Cc: public-music-notation-contrib@w3.org
- Message-ID: <CANRG7pQrxwEGn64U2ZdR=HvrvR53kNMxh13ErXkH0wnL+Rsq7A@mail.gmail.com>
I have no objection to a MusicXML 3.1 release. On Wed, Aug 23, 2017 at 11:11 AM, Michael Good <mgood@makemusic.com> wrote: > Hello all, > > MusicXML 3.1 has been in beta test for nearly 4 months. During that time > we have found and resolved 7 issues, the most recent of which was closed 3 > weeks ago. Issue #210 has also been found but not fully resolved, due to > conflicting needs for different applications and use cases. > > The only issue still outstanding in the V3.1 milestone is the conversion > to the W3C Community Final Specification Agreement (FSA) license. We would > like to keep to our current schedule of completing MusicXML 3.1 by the end > of September, and earlier if possible. > > Who has been implementing MusicXML 3.1 in their products? What have your > experience been? Do you believe that MusicXML 3.1 is ready for release? Or > is your product waiting until MusicXML 3.1 is released before beginning > development? > > Please share your experiences here. If there are no objections, the > current plan would be to finalize MusicXML 3.1 at the beginning of > September. But we do not want to do that if there are still outstanding > issues that we want to fix. > > Best regards, > > Michael Good > VP of MusicXML Technologies > MakeMusic, Inc. > >
Received on Wednesday, 23 August 2017 15:59:27 UTC