- From: Adam van den Hoven <adsmart@gmail.com>
- Date: Tue, 11 Mar 2008 08:48:35 -0700
- To: Jeff Schiller <codedread@gmail.com>
- Cc: "Henri Sivonen" <hsivonen@iki.fi>, "Julian Reschke" <julian.reschke@gmx.de>, "HTMLWG Tracking WG" <public-html@w3.org>
> On 11-Mar-08, at 8:37 AM, Jeff Schiller wrote: > > > The way I understand the problem is that the HTML5 parser would > require too many "special cases" to handle XML 'islands' like this. Really? Is it not simply a matter of: Do I recoginize the namespace that is declared? If -Yes- then parse that using my known code If -No- then ignore it It strikes me as the only way to handle the situation with anything like scalability. Every time (and only when) the parser encounters the foreignObject, it looks for the declared namespace (or what ever else) and delegates parsing to the relevant specialized code. Only one special case which makes it no particularly special. > Regards, > Jeff > > On 3/11/08, Adam van den Hoven <adsmart@gmail.com> wrote: >> Hey guys, >> >> It seems that there is no easy way to include other vocabularies into >> text/html assuming that: >> 1) You want the resulting docs to conforming >> 2) You want the resulting docs to be testable for conformance (using >> code, not manually) >> 3) You want to be able to support emerging technologies >> Henri's point that we've only seen two additional element >> sets is not >> entirely useful. In the broader web, I agree that new languages are >> likely to be infrequent. However in corporate settings, where all the >> browsers are controlled, other technologies could very well become >> common. >> >> In SVG, you have the foreignObject. Why not introduce something >> similar here? Would this not provide adequate isolation to allow >> validation code to work? >> >> Just $0.02 from a lurker >> >> Adam
Received on Wednesday, 12 March 2008 04:13:26 UTC