- From: Wendy A Chisholm <wendy@w3.org>
- Date: Tue, 20 Jan 2004 14:42:26 -0500
- To: Joe Clark <joeclark@joeclark.org>, WAI-GL <w3c-wai-gl@w3.org>
At 04:37 PM 1/16/2004, Joe Clark wrote: >"Embedded" is a poor choice of words. The Working Group may not understand >that <embed> isn't an HTML element, and that elements like <object> and >attributes like longdesc call *other* files into being. This is to be >contrasted with alt text (always present in the source document) or the >possible case of enclosing alternatives inside nested <object> elements. > >Hence SVG and movie clips aren't "embedded" in Web pages at all. They are >separate files called by the source document. The term "embedded" was suggested because SVG 1.1, section 2.3 "Options for using SVG in Web pages" [1] says, "There are a variety of ways in which SVG content can be included within a Web page. Here are some of the options: - A stand-alone SVG Web page - Embedding by reference - Embedding inline - External link, using the HTML 'a' element - Referenced from a CSS2 or XSL property" Under "Embedding inline" it says, "In this case, SVG content is embedded inline directly within the parent Web page. An example is an XHTML Web page with an SVG document fragment textually included within the XHTML." [1] http://www.w3.org/TR/SVG11/concepts.html#UsageOptions -- wendy a chisholm world wide web consortium web accessibility initiative http://www.w3.org/WAI/ /--
Received on Tuesday, 20 January 2004 14:42:36 UTC