Re: MusicXML 3.1 Community Group Report available for review

Thank you for making this report. I think this is an extremely useful
document, and something that should be included with every release.

I have one minor suggestion:

Link to related Github issues. This will help track changes, as well as
link to source code, discussion, and other relevant information. This way
we can have both linking to technical discussion as well as user-friendly
descriptions. Re-reading Peter's email, he felt that linking to Github was
insufficient, and I agree. However, I think it would be helpful to have
both.


On Tue, Dec 5, 2017 at 1:41 PM, Michael Good <mgood@makemusic.com> wrote:

> Hello all,
>
> A new version of the MusicXML 3.1 Community Group Report incorporating
> Peter Deutsch’s request for a full change list is now available for review
> at https://w3c.github.io/musicxml/.
>
> Any further reviews this week would be most appreciated. The current plan
> is to create the v3.1 tag in GitHub later today so the schema link starts
> working, and then publish the report early next week.
>
> Best regards,
>
> Michael Good
> VP of MusicXML Technologies
> MakeMusic, Inc.
>
> On Nov 20, 2017, at 8:50 AM, Michael Good <mgood@makemusic.com> wrote:
>
> Hello all,
>
> The last part of completing the release of MusicXML 3.1 is creating a
> Community Group Report document. MusicXML 3.1 does not have a specification
> document separate from the schemas. However, we need to have an HTML
> document in order to publish MusicXML 3.1 as an official W3C Community
> Group Report.
>
> A first version of this report is available for your review at
> https://w3c.github.io/musicxml/. This was produced using ReSpec and the
> source is at https://w3c.github.io/musicxml/respec.html.
>
> This brief document mainly contains links to the locations for the
> MusicXML 3.1 schemas, GitHub repository, and the Music Notation Community
> Group.
>
> The main schema link points to a v3.1 tag in the GitHub repository that
> doesn’t exist yet. I will create that once this document is approved by the
> group, after whatever revisions are necessary. Following that link will
> currently result in a 404 error. To see what this link will look like, use
> the v3.0 tag instead: https://github.com/w3c/musicxml/releases/tag/v3.0.
>
> Please let us know any suggestions for improving this report. We would
> like to publish this report in two weeks.
>
> Best regards,
>
> Michael Good
> VP of MusicXML Technologies
> MakeMusic, Inc.
>
>
>