W3C home > Mailing lists > Public > public-html@w3.org > April 2008

Re: Supporting MathML and SVG in text/html, and related topics

From: Chris Chiasson <chris@chiasson.name>
Date: Wed, 16 Apr 2008 12:39:31 -0500
Message-ID: <acbec1a40804161039s6dd98f52waf51ca7958f37d8d@mail.gmail.com>
To: "Paul Libbrecht" <paul@activemath.org>
Cc: "David Carlisle" <davidc@nag.co.uk>, jirka@kosek.cz, whatwg@whatwg.org, public-html@w3.org, www-math@w3.org, www-svg@w3.org

I know this will get me labeled, but the real reason why xhtml,
mathml, and svg "failed" has nothing to do with their technical design
and everything to do with Microsoft resting on their laurels after
using anti-competitive tactics to eliminate competition in the browser
market.

That is why I feel good about the situation going forward - no matter
what happens with the standards - because Microsoft is increasingly
not in a position to dictate terms.

On 4/16/08, Paul Libbrecht <paul@activemath.org> wrote:
>
> Le 15 avr. 08 à 16:51, David Carlisle a écrit :
> > However if HTML5 is standardised in its current form then there is no
> > chance of a general move to XML on the web ever happening. People,
> > authoring tools, web browsers, will all typically use text/html with the
> > more forgiving parsing that implies. This isn't necessarily a bad thing,
> > but it's definitely not the original vision at the time xml, xhtml,
> > mathml were conceived.
> >
>
>
> I would like to put a grain of salt here and would love HTML5 passionates to
> answer:
>
>  why is the whole HTML5 effort not a movement towards a really enhanced
> parser instead of trying to redefine fully HTML successors?
>
> Being an enhanced parser (that would use a lot of context info to be really
> hand-author supportive) it would define how to parse better an XHTML 3 page,
> but also MathML and SVG as it does currently... It has the ability to
> specify very readable encodings of these pages.
>
> It could serve as a model for many other situations where XML parsing is
> useful but its  strictness bytes some.
>
> Currently HTML5 defines at the same time parsing and the model and this is
> what can cause us to expect that XML is getting weaker. I believe that the
> whole model-definition work of XML is rich, has many libraries, has
> empowered a lot of great developments and it is a bad idea to drop it
> instead of enriching it.
>
> paul
>


-- 
http://chris.chiasson.name/
Received on Wednesday, 16 April 2008 17:40:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:14 GMT