Re: Netscape Support for XSL - client vs server rant

Ok...
However, you are referring to Cocoon 1.x which is proof-of-concept and many
things has been discovered in the process, incl. your objection below.

In fact, W3C has got it wrong. It is absolutely clear to everyone who has been
working with context separation that <?xsl-stylesheet> DOES NOT belong in the XML
document at all. You are introducing styling information into content, which is
wrong.
Likewise, the PI in Cocoon for selection of process pipeline (so called reactor)
is also wrong.

These things belong at the administration level, and has been heavily addressed
in the upcoming Cocoon 2, which has little resemblance with Cocoon 1.x. In fact,
it is a complete re-write.
(I also believe that the write-up about Cocoon 2 on the web site is a bit
outdated.)

I encourage you to forward your thoughts and ideas to the Cocoon-dev mailing list
(has not seen you there).

Thanks for your clarification
Niclas

P.S  Time to watch F1 qualifications... Anyone?

Matt Sergeant wrote:

> (where it says "these browsers" it actually means "these media types").
>
> I realise you can reconfigure this, which is why I said it's broken by
> default. The W3C technical recommendation specifically links to the HTML4
> spec to define how the <?xml-stylesheet?> processing instruction should be
> interpreted (even though it may have nothing to do with HTML). The HTML4
> spec *ONLY* defines and allows browsers to support the following media
> types:
>
>   screen, tty, tv, projection, handheld, print, braille and aural.
>
> The spec explicitly states:
>
>   "Future versions of HTML may introduce new values and may allow
> parameterized values".
>
> But Cocoon adding new values is akin to adding new tags to HTML - that's
> something that should be standardised by the W3C so that interoperability
> is guaranteed.
>
> So, come the day when client side XSLT is well supported, all your cocoon
> XML files containing <?xml-stylesheet ... media="explorer"?> will simply
> not work, because a HTML4 supporting browser may remove non-matching media
> types, and since the above media types aren't W3C ratified (and I doubt
> they ever will be), it's very unlikely that browsers will support them.
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list