W3C home > Mailing lists > Public > www-svg@w3.org > January 2003

Re: High-Quality Dynamic SVG Viewer

From: Jim Ley <jim@jibbering.com>
Date: Mon, 20 Jan 2003 11:09:00 -0000
Message-ID: <010401c2c074$55e3ffa0$d9969dc3@Moomin>
To: "Tobias Reif" <tobiasreif@pinkjuice.com>, <www-svg@w3.org>

www-qa removed.
"Tobias Reif" <tobiasreif@pinkjuice.com>
> Jim Ley wrote:
> >>- [...] The answer is to create a temporary well-formed
> >>  version of the partial download (close all open tags, etc) and
> >>  then render. [...]
>
> > This is a sensible approach, and I fully support it.
>
>
> How should the app do "close all open tags, etc" for the following?
> (Real question :)


I think, thinking in the XML space obscures the issue, we're rendering SVG
elements, as soon as we have enough information on something to render, we
can do that, since we alway layer content on top, consider:

<svg>
 <g>
  <g>
   <g>
   <rect x="10" y="10" width="10" height="10"/>

Without the closing tags of the svg, or g, we have enough information to
draw the rectangle, however because we don't know at this stage if the
document is well-formed, we cannot render anything according to the current
spec.  (this wouldn't be a problem of course if we built on SGML, rather
than XML, then we could've had closing tags as optional...)

How I take Dean's suggestion (which isn't in spec speak yet) is that the
parser is allowed to work on the assumption that every open element is
actually closed some time later in the stream, this will allow it to render
the rectangle in the above example - note the rectangle is well formed, so
it's not rendering anything that isn't well-formed because of this
assumption, it's simply allowing it to render elements which are parts of
fragments.  I don't think what I agreed it to is any different to your
DocumentFragment wording.

Jim.
Received on Monday, 20 January 2003 06:13:34 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:24 GMT