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


From: Sigurd Lerstad <sigler@bredband.no>
Date: Sun, 26 Jan 2003 10:33:26 +0100
Message-ID: <01cc01c2c51d$fa6d0f50$591273d5@mmstudio>
To: <www-svg@w3.org>


Okay.. I should say my opinions for SVG 1.2 before it's too late.. I'm going
to be quick.


remove <image> and have a xlink:href on <foreignObject> that links to an
external resource, or

have <externalObject> in place of <image> and have <inlineObject> instead of

This way, you first of all get closer to XHTML with the removal of <img> and
that <object> is always used instead, and you get a much clearer link
between embedded/non-embedded objects, which should render the same way.


You simply MUST allow inline objects, foreign or not, to be flowed inside
text regions, so that one can for example embed xhtml tables within the flow
of the text, one could e.g allow the aforementioned elements inside
<flowDiv> and <flowParagraph>

3. (not really a feature request)

With the addition of the DOM method getImageDocument()

You must specify wether it's okay for a UA to keep one document for all
<image> elements referencing the same url or if each <image> loads it's own


Sigurd Lerstad
Received on Saturday, 25 January 2003 03:31:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:46:55 UTC