- From: Norman Walsh <ndw@nwalsh.com>
- Date: Wed, 20 Apr 2011 18:03:48 -0500
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <m2r58wcyp7.fsf@nwalsh.com>
Alex Milowski <alex@milowski.org> writes: > efficiently. At the same time you've just turned off external subsets > for all XML documents. Right. And I assert that they will not fix that. Period. Henri's decision to close WONTFIX your bug on this issue is the clinching proof, I believe. > Similarly, xml:id process becomes a pain in languages like XHTML where > you already have an ID type attribute (i.e. "id") but that becomes > solvable even if the processing is a bit hairy. Maybe we should drop that from the recommended profile as well, then. >> I have an inflamatory proposal. >> >> Rename the "recommended" profile to "comprehensive" >> Rename the "basic" profile to "recommended". >> Drop the "modest" profile into the bit bucket. > > I don't think of this as inflammatory but I do think there is still a > problem. I think we still want XIncude in the "recommended profile > for browsers". We don't have a profile that turns off external > subsets and includes XInclude processing. Yes. I'm throwing the XInclude baby out with the external subset bath water. I don't think the browsers are going to implement XInclude either. They're allergic to "X" words, it's never going to be part of HTML, and it's a little tricky to get all the fallback stuff right. Be seeing you, norm -- Norman Walsh Lead Engineer MarkLogic Corporation www.marklogic.com
Received on Wednesday, 20 April 2011 23:04:20 UTC