Re: Some possible MicroXML design goals

Subset of XML 1.0. XML Namespaces is a separate spec.

On Jul 24, 2012, at 9:06 PM, "Rushforth, Peter"
<Peter.Rushforth@nrcan-rncan.gc.ca> wrote:

> Then cut and paste from micro xml into xml tools won't work because the namespaces prefixes
> will not be declared?  That's not a subset of XML, right?
>
> Peter
>
>> -----Original Message-----
>> From: James Clark [mailto:jjc@jclark.com]
>> Sent: July 24, 2012 09:58
>> To: Rushforth, Peter
>> Cc: public-microxml@w3.org
>> Subject: Re: Some possible MicroXML design goals
>>
>> 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 14:08:41 UTC