Re: [xml-dev] XPath and a continuous, uniform information space

Intriguing, Uche! You write:

"My own idea is to expand beyond that to support callback-type processing within the XML parse phase, triggered according to node patterns, which could support actions such as retrieving resources from the Web to produce additional or modified nodes. I prefer that separation, and I can also imagine other uses for such a system, including additional and more efficient schema and transform mechanisms."

So you speak of "node patterns", "processing" and "actions". Do you think of associating nodes with something dynamical, something reminding of functions - the definition of a processing, to be triggered by the XML parser coming along? And I wonder if such associations could be regarded as resources themselves (or part of the resources), so that the result would resemble an object in the OO sense - data plus behaviour. Or perhaps I misunderstood? ...

Cheers,
Hans

Von: Uche Ogbuji <uche@ogbuji.net>
An: "Costello, Roger L." <costello@mitre.org>
CC: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
Gesendet: 18:03 Samstag, 17.August 2013
Betreff: Re: [xml-dev] XPath and a continuous, uniform information space

On Fri, Aug 16, 2013 at 5:13 PM, Costello, Roger L. <costello@mitre.org>, quoting Hans-Juergen Rennau:

My conception of [an InfoSpace] is perhaps differs from yours. Here is mine: The info space is a forest of nodes within which XPath can move freely. It is the possibility of unobstructed and very efficient movement, what transforms a heap of nodes into a space of nodes.

This is also useful clarification re my subthread with David. I don't think it's useful to try to conceive an "InfoSpace" for a given XML process or process pipeline which encompasses the entire Web. My thinking is simply, as above, that node navigation mechanisms are opened up a bit more to resources which at present would be considered external to the document being processed. I think Michael Kay's key idea was in allowing the XML parser itself to address such resources in a dynamic, late-binding way, more so than the current system of entities and such, and which then opens things up to e.g. XPath largely as it is. My own idea is to expand beyond that to support callback-type processing within the XML parse phase, triggered according to node patterns, which could support actions such as retrieving resources from the Web to produce additional or modified nodes. I prefer that separation, and I can also imagine other uses for such a system, including additional and more efficient schema and transform mechanisms.