W3C home > Mailing lists > Public > public-html-xml@w3.org > January 2011

Re: The interpretation of script

From: Robin Berjon <robin@berjon.com>
Date: Wed, 19 Jan 2011 19:24:50 +0100
Cc: Henri Sivonen <hsivonen@iki.fi>, public-html-xml@w3.org
Message-Id: <059BD6F3-2255-42AC-ABCC-7E8D755F233F@berjon.com>
To: Michael Kay <mike@saxonica.com>
On Jan 19, 2011, at 16:49 , Michael Kay wrote:
>> I'm not familiar with the specification, but my first instinct would be to see if document.createElementNS(MUSICXML_NS, "whatever-the-root-element-is") returns MusicXMLFooElement. Then again, I haven't read the spec (I wanted to give it a cursory overview, but it's in a zip so I gave up).
>> 
> You probably don't need to know any more than you can find in
> 
> http://www.recordare.com/musicxml/tutorial/hello-world

Thanks, that makes sense. But looking around this does seem to be missing something that the implementer you described in your original post would probably want to know: how is this expected to integrate into an HTML DOM? Adding a <score-partwise> element now would produce an HTMLUnknownElement node in the DOM. What you'd want would probably be for it to generate a MusicXMLScorePartElement, or if the language doesn't justify specialised interfaces per element type at least MusicXMLElement.

I wonder if this would be a useful thing to work on: a checklist of what one needs to do to integrate one's language into HTML. Sort of CDF but without the endless moaning over media types and namespaces, in a two-page read-on-the-bus format.

-- 
Robin Berjon - http://berjon.com/
Received on Wednesday, 19 January 2011 18:25:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 19 January 2011 18:25:24 GMT