- From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
- Date: Fri, 30 Nov 2007 18:10:12 +0100
- To: public-html@w3.org
Sam Ruby wrote: >For various reasons, many members of this working group (correctly, >IMHO) believe that XHTML is a non-starter for most people. .... >> Embedding SVG (and MathML for instance) in HTML is an area I and others >> have been looking into during the TPAC (and also on this mailing list, >> on weblogs, etc.), but we don't have a good enough proposal yet or >> implementation experience for that matter to show that it could actually >> work. >Some prior work in this area, some may be dead ends, others may pan out: .... Personally I had no problem to mix SVG, MathML and XHTML using the old doctype for this and testing it with the W3C-validator, I already used it with SVG inside XHTML and for XHTML inside SVG too and I personally have no problem with sending XHTML as application/xhtml+xml or mixtures as this type or as image/svg+xml for the other way round, but indeed this is not completely trivial for authors used to write faulty HTML-documents ;o) The problem is more a semantical one. In SVG one may use foreignObject, title or desc as containers for XHTML for different purposes, in XHTML currently there is only the unspecific div to do the job and I can identify for this and almost any other purpose ;o) And if script or img is not sufficient and canvas is required for scripted raster images, it looks a good idea to me to have a specific element for vector graphics too, just to hold the semantical ballance - well there is a lot more to do in HTML5 to get a semantical ballance between things, the authors of the draft obviously like and things they do not like/care or are not very familar with at least.
Received on Friday, 30 November 2007 17:13:18 UTC