- From: Uche Ogbuji <uche@ogbuji.net>
- Date: Thu, 6 Sep 2012 07:17:53 -0600
- To: public-microxml@w3.org
- Message-ID: <CAPJCua192s4AzHH3Sct3Bop-bUHercYzzbrc+GQj9r8rouLHEw@mail.gmail.com>
On Thu, Sep 6, 2012 at 2:16 AM, James Clark <jjc@jclark.com> wrote: > If the goal is to be able view MicroXML documents that happen to use the > right element/attribute names "casually in a browser", then does it matter > that the browser will use quirks mode (if we don't allow DOCTYPE)? > Agreed quirks mode is not the end of the world, except for some oler browser versions which will soon fade away into obscurity. > For robust, standards-compliant delivery of HTML5, my current inclination > is to use an MicroXML->HTML5 serializer that does the right thing with > empty elements, and adds a DOCTYPE declaration. We should at least have a > standard way of representing an HTML5 DOM (at least any HTML5 DOM > representable in the HTML syntax) in MicroXML, which means we need some > convention for dealing with xlink:href. > > So my current position is: > > - no bare DOCTYPE > - no to the additional HTML5 restriction on XML comments > +1 As for xlink:href, since the user will be in a restricted vocabulary if they want straightforward serialization to HTML5, the convention for such could simply be "xlinkhref" without fear of a vocab clash. We could put that and the few other conventions for HTML5-convertible MicroXML into a non-normative annex. -- Uche Ogbuji http://uche.ogbuji.net Founding Partner, Zepheira http://zepheira.com http://wearekin.org http://www.thenervousbreakdown.com/author/uogbuji/ http://copia.ogbuji.net http://www.linkedin.com/in/ucheogbuji http://twitter.com/uogbuji
Received on Thursday, 6 September 2012 13:18:34 UTC