xml: prefix in MicroXML Re: [xml-dev] MicroXPath proposal

[Stephen Green <stephengreenubl@gmail.com>]

I notice the only prefix allowed in James' revised MicroXML is the
prefix "xml:".

I see the significance of this prefix is tied up with the Namespaces
spec so I guess in this sense MicroXML implements (compatibly?)
XML Namespaces. It reads:

"The prefix xml is by definition bound to the namespace name
http://www.w3.org/XML/1998/namespace. It MAY, but need not, be
declared, and MUST NOT be bound to any other namespace name. Other
prefixes MUST NOT be bound to this namespace name, and it MUST NOT be
declared as the default namespace."

So it doesn't need a prefix/namespace declaration (so that
answers my previous concern).

What does it give you?

If there were sufficient need could the number of xml: uses be
extended?

Is there an xml:type?

----
Stephen D Green



On 14 January 2011 09:14, Stephen Green <stephengreenubl@gmail.com> wrote:
> So apparently the revision allowing prefixes on attributes decreases
> the compatibility of MicroXML with full XML if it breaks Namespaces
> compatibility. Just thought it worth flagging up the cost of that step,
> if MicroXML without prefixes in attributes is indeed compatible with
> XML Namespaces (by virtue of the inclusion of the 'xmlns' attribute).
> ----
> Stephen D Green
>
>
>
> On 13 January 2011 17:52, John Cowan <cowan@ccil.org> wrote:
>> mozer scripsit:
>>
>>> [quoting James Clark]
>>> Data model.  The MicroXML specification should define a single,
>>> normative data model for MicroXML documents. It should be as simple
>>> possible:
>>
>> [snip]
>>
>>> * A name is a string. It can be split into two parts: a prefix, which
>>> is either empty or ends in a colon, and local name.
>>
>> James's current version does not allow QNames as element names,
>> and allows only the fixed prefix "xml:" in attribute names.
>> I have extended it to allow general QNames in attribute names.
>> See http://blog.jclark.com/2010/12/more-on-microxml.html  .
>>
>>> * An element probably also needs to have a flag saying whether it's an
>>> empty element.
>>
>> The problematic HTML5 elements can be special-cased.
>>
>>> It means you have also attribute and text nodes
>>
>> Not necessarily, any more than the fact that elements have names requires
>> the model to provide "name nodes".  Note that James says the attributes
>> are a map rather than a list of attribute nodes, so attributes need not
>> be reified.
>>
>> --
>> There is / One art                      John Cowan <cowan@ccil.org>
>> No more / No less                       http://www.ccil.org/~cowan
>> To do / All things
>> With art- / Lessness                     --Piet Hein
>>
>> _______________________________________________________________________
>>
>> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>> to support XML implementation and development. To minimize
>> spam in the archives, you must subscribe before posting.
>>
>> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
>> subscribe: xml-dev-subscribe@lists.xml.org
>> List archive: http://lists.xml.org/archives/xml-dev/
>> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>>
>>
>