Re: Will MNX CG meet during TPAC?

Hi Andrew, and hello again Janina (wishing you a great TPAC)

The embedding topic sounds interesting and is something I experimented with
a while back. Eg

https://musicpracticetools.net/tunes/jazz-blues-in-bb/

To be honest I didn't concider a11y as it was an experiment.  Shame on me,
sorry Janina. :D

This used ABC notation software which to be honest while easy to hand write
is effectively a new text based language for notation. You end up
transcribing twice. It is popular in some circles though. MNX would be
preferable but for hand encoding is not so good, you need an interactive
tool to create.

I took a "widget" approach allowing interactive elements to be dropped into
markdown. I had to roll my own  but the 11ty famework dev since worked on
an "islands" architecture that sounded ideal. This approach is a bit above
the web platform and so "iframe on steroids" might work well.

I'd not heard of Verovio so will be sure to explore it. I'm currently
looking at voice control of music practice tools with Alexia :) And
procrastinating from my music practice lol.

Steve

On Tue, 29 Aug 2023, 08:32 Andrew Hankinson, <andrew.hankinson@gmail.com>
wrote:

> Hi Janina,
>
> You may be interested in the Verovio notation viewer, which is an
> open-source JavaScript component for displaying music notation in a web
> browser. (It also has library versions for Python and a command-line
> version). It's also being used in mobile apps. Since it's integrated into
> the JavaScript APIs it supports a kind of "interactive music notation"
> where users can manipulate the notation directly, so it sounds close to
> what you might be imagining!
>
> It supports the W3C group's MusicXML format, as well as a number of other
> notation standards, like abc, **kern, and MEI. It will likely support MNX
> once the spec is stable.
>
> https://www.verovio.org/index.xhtml
>
> If you want more information please feel free to reach out.
>
> Cheers,
> -Andrew
>
> On 28 Aug 2023, at 21:49, Janina Sajka <janina@rednote.net> wrote:
>
> Thanks, Adrian. Sorry to miss you at TPAC this year, but we will
> certainly keep MNX aprised of the direction we're going on embedded
> objects. Being APA, we're looking for a solution that can accomodate
> various types of specialized markup objects where the general browser
> may not always be the most functional tool--especially when it also
> needs to be an accessible tool.
>
> In short we're contemplating proposing a kind of iframes on steroids
> approach which hands off the interface to a special user agent, perhaps
> Muse Score in the case of scored music, and then returns to the browser
> when the object is exited. Anyway, that's a summation of our current
> thinking. We'll see how that goes over with other groups and especially
> the HTML and browser folks.
>
> Thanks again for the prompt response.
>
> Janina
>
> Adrian Holovaty writes:
>
> Hi Janina,
>
> Thanks for the message. Alas, we're not planning to meet during TPAC
> this year. Our last meeting was in June, and you can read the minutes
> here:
>
> https://www.w3.org/community/music-notation/2023/06/06/community-group-
> meeting-friday-2-june-2023/
>
> Regarding embedding MNX in larger objects: we haven't spent much time
> thinking about that particular use case yet, but in theory it should be
> straightforward. In lieu of an in-person meeting at TPAC, you're always
> welcome to open a GitHub discussion if you have ideas or questions:
>
> https://github.com/w3c/mnx/discussions/
>
> Adrian
>
> On August 28, 2023, Janina Sajka <janina@rednote.net> wrote:
>
> If "yes," Accessible Platform Architectures (APA Working Group would
> appreciate a joint meeting. Very probably 30 minutes would suffice.
>
> If the group isn't meeting, but key MNX participants will be at TPAC,
> perhaps there'd still be value in a quick discussion.
>
> Needless to say we're interested in accessibility, but specifically on
> how MusicXML, MNX, (etc) formats can effectively be embedded in larger
> objects, e.g. a harmony or composition textbook containing multiple
> notations, and perhaps even long excerpts of compositions.
>
> With apologies for this late inquiry,
>
> Janina
> On behalf of APA
>
>
> --
>
> Janina Sajka (she/her/hers)
> Accessibility Consultant https://linkedin.com/in/jsajka
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
>
> Linux Foundation Fellow
> https://www.linuxfoundation.org/board-of-directors-2/
>
>
>
>