[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Browser support of XML standards (WAS: RE:Slightly off, but... was: XUL

  • To: "J. David Eisenberg" <catcode@c...>,"Sebastian Schnitzenbaumer" <schnitz@m...>,"Stefano Debenedetti" <sdebenedetti@e...>
  • Subject: Browser support of XML standards (WAS: RE:Slightly off, but... was: XUL appears to...)
  • From: "Manos Batsis" <m.batsis@b...>
  • Date: Wed, 10 Jul 2002 10:13:29 +0300
  • Cc: <xml-dev@l...>
  • Thread-index: AcInppXRirHLuKBiSjqObqZUnfNajwAN/Zjg
  • Thread-topic: Browser support of XML standards (WAS: RE:Slightly off, but... was: XUL appears to...)

vml browser support

> From: J. David Eisenberg [mailto:catcode@c...] 

> Rather
> than compile in support for such things as MathML or need Microsoft's
> weird "binary behaviors" to put SVG into an XHTML page,

About behaviors, that's not SVG; that's the predecessor named VML
(vector markup language ;-)

> I propose
> "namespace plug-ins".
> Consider: a browser now gets some MIME type that isn't 
> text/html, so it
> looks up the MIME type in a list of plug-ins and throws the 
> data to the
> appropriate plug-in, which returns some sort of result 
> through the plug-in
> API.

At first glance it's not a bad idea for pushing browsers a little
further but essentially you are actually talking about object tags
(without the object tag...). Native support is much better than this
approach; having different handlers for each subdocument has certain
disadvantages. Here's some:

* The plug-ins have to be specific for each browser (for example activeX
controls in IE). This is the main reason I dislike IE's XML support;
it's not actually in the browser but on a separate dll used as activeX
* You will never be certain on the level of communication between all
those different plug-ins.
* You will have to use DOM extensions for all the above.

> Why not have some API such that, when the browser hits markup with a
> namespace whose URI it's not equipped to handle, it throws 
> the data to a
> plug-in which returns a "box" with the appropriate display 
> (which might be
> a graphic for SVG, text and graphics for MathML, or an audio 
> control panel
> in the case of VoiceML) to the browser. All of this would be 
> done through
> some publicly-advertised API.

If that API is a standard instead of browser specific technology, sure.




Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.