Re: [xml-dev] MicroXPath proposal

[Stephen Green <stephengreenubl@gmail.com>]

> And most of
> them aren't subsets - few can resist adding something,

Maybe this is a firm reason NOT to push a MicroXML and
related Micro-culture since as soon as you prune a plant
or a technology it tends to put all its resources into a
smaller growth region and produce more vigorous new
growth. Pruning XML like this is bound to give people
more time and remove barriers to entry for them to think
up new extensions. This might then introduce divergences
with XML-proper, unless some special provision is made
for either feeding extra resources into the main XML work
so it can keep up with the extensions and for ensuring
extensiosn can be easily fed into that main XML work from
these MicroXML adopters.

Or maybe that is exactly what XML/society needs.

----
Stephen D Green



On 13 January 2011 09:22, Michael Kay <mike@saxonica.com> wrote:
> Oh dear, yet another XPath subset. And they're all different. And most of
> them aren't subsets - few can resist adding something, though most people
> have the decency to do it by adding functions rather than new syntax.
>
> Please, why is this needed? And what were your criteria for deciding, say,
> that "|" or ">" aren't needed?
>
> Michael Kay
> Saxonica
>
> On 13/01/2011 06:12, John Cowan wrote:
>>
>> I've been thinking a lot about MicroXML, MicroXSD, MicroRNG, etc., and
>> I thought I'd take a stab at a MicroXPath.  This is intended to be,
>> like the others, the simplest thing that could possibly work.
>> However, I'm not a frequent XPath user, so I may have put together
>> something that is *too* simple to work.  So I'm posting here for
>> comments.  (I'm using this address because xml-dev drops posting from
>> my permanent cowan@ccil.org address on the floor, for some reason).
>>
>> One principle is that since elements are the only kind of node in the
>> MicroXPath data model, XPath expressions return only lists of
>> elements.  Another is that 100% compatibility with XPath 1.0 isn't
>> essential, since most XPath expressions are fairly transient compared
>> to XML documents or schemas.
>>
>> So here's what I've got.  The only kind of expression is a location
>> path.  Location paths can be absolute or relative, and their steps can
>> be separated by either / or //.  A path step is an element name, star,
>> dot, or dot-dot.
>>
>> Only one predicate is allowed per step, and it has to take one of
>> these eight forms:
>>
>> 1)      a literal number
>>
>> 2)      last()
>>
>> 3)      location-path="string"
>>
>> 4)      @name="string"
>>
>> 5)      location-path/@name="string"
>>
>> 6)      @@name="string"
>>
>> 7)      location-path/@@name="string"
>>
>> 8)      function(.)
>>
>> @@ means "inheritable attribute", and is provided for brevity and
>> convenience.  In form 8, the function name is provided externally to
>> XPath (there are no built-in functions except last()), and accepts the
>> current element node and returns a boolean value.  This is the
>> programmatic escape from MicroXPath that allows complex predicates.
>>
>> What's missing?  What can I take out?  Comments solicited.
>>
>> --
>> John Cowan       http://www.ccil.org/~cowan<cowan@ccil.org>
>>        You tollerday donsk?  N.  You tolkatiff scowegian?  Nn.
>>        You spigotty anglease?  Nnn.  You phonio saxo?  Nnnn.
>>                Clear all so!  `Tis a Jute.... (Finnegans Wake 16.5)
>>
>> _______________________________________________________________________
>>
>> 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
>>
>>
>
>
> _______________________________________________________________________
>
> 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
>
>