XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Re: XML5

On Fri, Dec 17, 2010 at 2:30 PM, Michael Kay <mike@saxonica.com> wrote:
> On 16/12/2010 21:24, Jirka Kosek wrote:
>>
>> Henri Sivonen wrote:
>>
>>> You get more proprietary extensibility with XML (which lets
>>> enterprise vendors say they do XML to appear to use a standard while
>>> they lock the customer in on the vocabulary level). However, people
>>> really shouldn't be sending content using proprietary vocabularies on
>>> the Web.
>
> So, let's say I want an application that plays music and shows it being
> played, synchronized with an animation of the musical score.
>
> I would have said the most appropriate architecture for that is for the
> server to serve MusicXML, and for a client-side application to do both the
> aural rendition and the animated display.
>
> You're saying I "really shouldn't" be doing that. I don't understand why.
> How would you do it?

I would use the MusicXML markup in my document, and use a XSLT stylesheet
to convert these tags at runtime into horrible code in Javascript.
Then I would check whether the XML markup is used or not, and if it is used,
then I would advocate for its native implementation in browsers.

Typically, XSLTForms follows this philosophy.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS