- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Wed, 19 Jan 2011 05:21:40 -0800 (PST)
- To: public-html-xml@w3.org
Robin Berjon: > On Jan 18, 2011, at 18:18 , Michael Kay wrote: > > At that point anyone delivering MusicXML content is going to have to > > worry about delivering it to two kinds of browser, those with native > > MusicXML support, and those that handle it via a shim. How do we see > > this being done? Or are we simply going to say "this is more than 12 > > months away, we'll sort something out when the time comes?" > > That's no different from shipping content with SVG today, knowing that > some browsers support it and some don't. You test for support (I'm > guessing here you'd have Modernizr.musicXML) and if absent throw in > the shim. Actually, it is different. If there are no natively supporting UAs when authors start deploying JS shims, you can be pretty sure that when the legacy has accumulated for a couple of years, there are sites that fail to check for native support. If you were to check for native support of MusicXML in application/xhtml+xml today, what would you check? It's hard enough to check for MathML support. -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
Received on Wednesday, 19 January 2011 13:22:44 UTC