W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > February 2007

Re: Load Component

From: Alex Milowski <alex@milowski.org>
Date: Thu, 1 Feb 2007 07:55:34 -0800
Message-ID: <28d56ece0702010755h33a298a2s716aa3a2218d2c58@mail.gmail.com>
To: public-xml-processing-model-wg@w3.org
On 2/1/07, Norman Walsh <Norman.Walsh@sun.com> wrote:
>
> / Alessandro Vernet <avernet@orbeon.com> was heard to say:
> | On 1/31/07, Innovimax SARL <innovimax@gmail.com> wrote:
> |> that's interesting, on which signal, you would detect that it is *not*
> |> an XML document ?
> |
> | With HTTP for instance, you get a content type. If it is not
> | application/xml or similar, the component could attempt to convert it
> | to XML. Say it is text/html: the component can run something like HTML
> | Tidy so you get XML. This is what we do (if you choose to do so) in
>
> 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.

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).





-- 
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered."

Bertrand Russell in a footnote of Principles of Mathematics
Received on Thursday, 1 February 2007 15:55:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:49 GMT