- From: James Clark <jjc@jclark.com>
- Date: Tue, 24 Jul 2012 20:57:40 +0700
- To: "Rushforth, Peter" <Peter.Rushforth@nrcan-rncan.gc.ca>
- Cc: "public-microxml@w3.org" <public-microxml@w3.org>
On Jul 24, 2012, at 8:48 PM, "Rushforth, Peter" <Peter.Rushforth@nrcan-rncan.gc.ca> wrote: >> >> This isn't quite right. MicroXML would still need to allow at >> least some prefixes on attributes (xml:, xlink: and xmlns:) >> so as to be able to represent the namespaced attributes that >> occur in the HTML syntax of HTML5. > > Why would you want to include xlink in MicroXML? I want to be able to represent any HTML5 document in MicroXML, and HTML5 allows certain prefixed attribute names include certain names starting with "xlink:". IIRC this is because SVG uses XLink. This is not quite the same as including xlink. > It is not fit for the > web, and will drag in namespaces with it. Not quite. HTML5 doesn't care about namespace declarations. In HTML5, the "xlink:" prefix is built-in just like the "xml:" one is. All it drags in is the requirement to allow attribute names to have a colon in them. James
Received on Tuesday, 24 July 2012 13:57:24 UTC