- From: Jon Ferraiolo <jon@ferraiolo.com>
- Date: Fri, 23 Aug 2002 06:58:06 -0700
- To: "'Tobias Reif'" <tobiasreif@pinkjuice.com>, <www-svg@w3.org>
Tobi, Here is a snippet from the SVG spec: --- Usually, a 'foreignObject' will be used in conjunction with the 'switch' element and the requiredExtensions attribute to provide proper checking for user agent support and provide an alternate rendering in case user agent support is not available. --- The model is that something other than native SVG is going to render onto a virtual rectangle on the SVG canvas. The conceptual model is that of an optional plugin, but actual implementations might indeed be monolithic. Jon > -----Original Message----- > From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] On Behalf Of > Tobias Reif > Sent: Friday, August 23, 2002 5:06 AM > To: www-svg@w3.org > Subject: Re: foreignObject > > > Jon Ferraiolo wrote: > > > In my thinking, a foreignObject element will have a requiredExtensions > > attribute which is a namespace URI which says which "plugin" to the SVG > > user agent will parse the contents of the foreignObject and produce a > > rendering based on those contents. If the plugin can deal with multiple > > children, then you can have multiple children within the foreignObject. > > > In the case of a native implementation like Mozilla (Croczilla), none of > SVG or XHTML implementation are pluigns. > I also don't think that any implementation specific information should > be required, or that any specific implementation should be required, and > AFAIK, this is the case; just namespace qualifications. > > Sigurd, you might want to check > http://www.w3.org/TR/XHTMLplusMathMLplusSVG/#howto-svg > , but I'm not sure if it answers your question about multiple children. > > Tobi > > -- > http://www.pinkjuice.com/ >
Received on Friday, 23 August 2002 09:59:25 UTC