RE: [svg-developers] Distribute SVGViewer und PDFViewer in one single Plugin
- View SourceSorry, but you are totally missing the point of multiple namespaces in one
XML document. Each namespace does what it does best, SVG for 2D graphics,
XHTML for simple Hyper Text, SMIL for Animation and Mulitmedia
presentations, MathML for mathematical and scientific content, etc. SVG
will never replace HTML. It can't be, and will never be, all things to all
people, but extending it with all the other namespaces, will make it a
If you need to see an example of what I�m talking about, check out my Bar
Graph page, at www.yettieplanet.com/BarGraph.asp. You will need IE 5.5,
because it�s the only browser that I know of the handles custom namespaces.
The code to produce the bar graph is hidden from the XHTML developer, so
they don�t need to learn SVG to produce decent bar graphs. All they need to
know is my simple namespace, and they can generate nice looking bar graphs.
The code interprets the elements of the namespace in the �HTML page� and
then generates the bar graph in its place. Right now the page only has my
custom namespace and SVG�s, but I�m going to add SMIL (to animate the
building of the bars).
As for bundling the SVG Viewer in Adobe, nice idea, but a better one is
getting rid of the viewer all together, and make it what Microsoft calls a
�binary behavior�. Basically it�s a namespace consumer. It understands one
namespace (like SVG) and transforms it to a graphical format to be displayed
in the browser. The main problem with this concept is that the W3C hasn�t
developed a standard API for browsers to follow, so that a �binary behavior�
can be reused between browsers. Think of it as a standard why to implement
plugins. When the browser encounters a namespace like
It determines if a binary behavior exists on the machine (just like a
plugin) and if it doesn�t it can download it (just like a plugin). The
difference is that namespaces can interact we each other (which doesn�t
happen with plugins). The �standard� namespaces would be distributed with
the browser. MS already does this, which is why it is so big. The
�standard� namespaces to MS are HTML, XHTML, VML, SMIL, and the MSOffice
namespace (which is why MS Office documents saved as HTML look just like
their binary counterparts in IE).
----Original Message Follows----
From: "Steve White" <steve@...>
Subject: RE: [svg-developers] Distribute SVGViewer und PDFViewer in one
Date: Thu, 1 Feb 2001 20:43:43 -0500
I must admit the more I get into this and the more I think about it the more
I tend to agree Chris. The only thing that IE or Netscape add is their
popularity. Not that that should be discounted, but one has to wonder where
the technology is really based. SVG provides a rich graphics format that the
Browsers do not. The most valuable aspect of the browsers is that the search
engines will pick up and catalogue HTML meta tags.
So why do we need a Browser to view SVG content? My guess is for purely
strategic marketing reasons. When will the Adobe viewer display an SVG file
without a Browser? I'll bet it can do it right now if Adobe wants to install
it that way.
Get your FREE download of MSN Explorer at http://explorer.msn.com