- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Thu, 01 Feb 2007 08:00:24 -0800
- To: public-xml-processing-model-wg@w3.org
Received on Thursday, 1 February 2007 16:00:45 UTC
/ Alex Milowski <alex@milowski.org> was heard to say: |> I would have expected "tidy" to be its own component. | | The problem is that if you give a URI to the load component that is an | HTML document, then you need to run "tidy" to parse the resource. Ah. Yes. D'oh! | An implementation can look at the mime type (or assumed mime type) | and decide whether they want to do that. The question is whether this | is an extension to our component or a built-in feature (even if optional). I don't see a convenient way to make it standard because there's no standard "tidy" algorithm to point to. I'd rather not have it optional, either. Hmm... Be seeing you, norm -- Norman Walsh XML Standards Architect Sun Microsystems, Inc.
Received on Thursday, 1 February 2007 16:00:45 UTC