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

Re: several messages about New Vocabularies in text/html

From: Sam Ruby <rubys@us.ibm.com>
Date: Thu, 3 Apr 2008 23:32:19 -0400
To: Ian Hickson <ian@hixie.ch>
Cc: Jeff Schiller <codedread@gmail.com>, Henri Sivonen <hsivonen@iki.fi>, HTML WG <public-html@w3.org>, Public MathML mailing list <www-math@w3.org>
Message-ID: <OFCC252D71.8B53B730-ON85257421.00122D64-85257421.0013706C@us.ibm.com>

Ian Hickson <ian@hixie.ch> wrote on 04/03/2008 05:20:55 PM:
> I now have some rough notes of what I think we can do to the parser to
> handle SVG and MathML here:
>    http://wiki.whatwg.org/wiki/New_Vocabularies_Solution

My quick read indicates that this suffers the same issue that you
previously referred to as 'fatal' when Henri suggested using <math> as a
trigger.  I think it could be improved by an additional check for an
attribute named xmlns; and furthermore wonder if that additional check were
in place would a check on the element name even be necessary.

I also don't see anything which would begin to address xlink.

This proposal makes references to "case fixups" and lists specific which
implies to me that it is tightly coupled to snapshot of these specific
vocabularies as they exist at the moment.  A consequence of that decision
is that this vocabulary may need to be updated every time those
vocabularies are revised.

As such, I don't believe that this meets the stated requirement of "Ability
for an author to unilaterally extend the language to address problems we
are currently unaware of and that therefore are not covered by existing
functionality".  Simply specing that this "in namespace" state is case
sensitive and triggering transitions based on an attribute named xmlns
would go a long way towards addressing this requirement.

- Sam Ruby
Received on Friday, 4 April 2008 03:33:15 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:32 UTC