Re: Load Component

On 2/1/07, Norman Walsh <Norman.Walsh@sun.com> wrote:
>
> / 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...



Suppose an implementation  does something like this?  Is it an extension or
a violation of the spec?   Should it use a different component name to "play
nicely".


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