XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] MicroXPath proposal

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS