W3C home > Mailing lists > Public > public-microxml@w3.org > February 2013

Re: Design goal regarding HTML5

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 18 Feb 2013 16:40:17 +0100
To: Uche Ogbuji <uche@ogbuji.net>
Cc: public-microxml (public-microxml@w3.org) <public-microxml@w3.org>
Message-ID: <20130218164017332704.e5c52118@xn--mlform-iua.no>
Uche Ogbuji, Mon, 18 Feb 2013 00:01:22 -0700:
> On Sun, Feb 17, 2013 at 12:09 AM, Leif Halvard Silli wrote:
> 
>> Hi James, I agree more with your original goals about HTML5
>> compatibility. Therefore I propose:
>> 
>> 1. DOCTYPE declaration: Why not allow doctype declaration, without DTD,
>> as a legacy feature, and require that it should match the root element?
> 
> Because the benefits in hack-for-hack compatibility with HTML5 do not
> outweigh the added syntactical complexity.

(I actually OK’ed some of James choices.)

>> It is not up to *this* community group - or to the XML working group -
>> to decide that it is not important whether a MicroXML document consumed
>> as HTML, causes quirks mode rendering.
> 
> I don't see why this is relevant.  We're designing a markup language here,
> not a Web browser.

Is MicroXML supposed to have its own MIME type?

>> 2. xlink:href. Question: Is it not meant to be poossible to embed
>> non-MicroXML documents, (e.g. XML 1.0 documents)  directly inline in a
>> MicroXML document?
> 
> No this is not a goal.  It's worth noting that this is not in general
> possible with XML 1.0, either.

Everything in XML must be XML, I guess.

>> I ask because, unlike what you said, xlink:href is
>> not an attribute in HTML5. It is an attribute in SVG (which HTML5
>> considers to be in another namespace, even in the text/html
>> serialization). It is thus, per HTML5’s own terminology, 'foreign'
>> content. If MicroXML does not allow this today, then I propose to do
>> allow embedding of 'forreign' XML 1.0 in MicroXML documents - this
>> would solve the xlink:href problem until SVG eventually is updated.
>> (Btw, MicroXML production [22] *does* seem to permit ':' in attribute
>> names
>> https://dvcs.w3.org/hg/microxml/raw-file/tip/spec/microxml.html#names )
> 
> This bit makes me think that you meant "elements" rather than "documents"
> in the above section.  Anyway no, MicroXML does not offer a means of
> embedding any character sequence that does not itself conform to MicroXML.

OK.


>> My perspective on this is as one who has backed Polyglot Markup in the
>> HTML working group, […]

> I do not think that anyone should be advocating MicroXML as a solution
> anywhere on the spectrum of HTML Polyglot Markup.  It sounds as if your
> proposed warning is appropriate.

Thanks. That is good to know.

> Historical note: It's true that thinking about HTML5 and JSON were the
> initial triggers for work on MicroXML, but over time, and with much careful
> discussion we worked out a difficult balance between these influences, and
> that of XML 1.0, to arrive at what you see in the current community draft.

Your presentation of MicroXML at ibm.com is then quite misleading. It 
shows MicroXML with @xmlns attributes[1] and DOCTYPE.[2]

[1] http://www.ibm.com/developerworks/library/x-microxml1/#list2

[2] http://www.ibm.com/developerworks/library/x-microxml1/#list3

-- 
leif halvard silli
Received on Monday, 18 February 2013 15:40:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 18 February 2013 15:40:53 GMT