- From: John Cowan <cowan@mercury.ccil.org>
- Date: Tue, 18 Jan 2011 13:40:38 -0500
- To: Michael Kay <mike@saxonica.com>
- Cc: Kurt Cagle <kurt.cagle@gmail.com>, Anne van Kesteren <annevk@opera.com>, Norman Walsh <ndw@nwalsh.com>, public-html-xml@w3.org
Michael Kay scripsit:
> 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?
Either the shim or the server or both then need some mechanism to decide
whether native mode is available, and disable the shim if so. This is
no different in principle from the need to decide whether JavaScript is
available and deliver down-level pages if not, only it's much simpler
and easier.
The alternative is to decide that people without native MusicXML aren't
your target market for the page, and just omit the shim altogether.
Again, this is paralleled by people whose pages just don't work if you
don't have JavaScript turned on, or who only give you the choice of
throwing a manual switch (as GMail does).
--
Do I contradict myself? John Cowan
Very well then, I contradict myself. cowan@ccil.org
I am large, I contain multitudes. http://www.ccil.org/~cowan
--Walt Whitman, Leaves of Grass
Received on Tuesday, 18 January 2011 18:41:14 UTC