[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: An XML API using Java streams
As the expressiveness of XPath is excellent (and I think - not to be surpassed), any fresh attempt at a navigation model might profit from a comparison of its key principles with the key principles behind XPath. I would summarize the latter as follows: (1) Navigation is a sequence of steps. (2) A step is a mapping of current locations to next loations. (3) A step is either a standard step or a custom step. (4) A standard step has a direction (axis) and a simple standardized filter (node name or kind). (5) A step can be extended by custom filters. (6) The addition of step filters does not increase the complexity of the navigation. (7) Step semantics are self-contained and any step can be applied to any input Michael Kay <mike@saxonica.com> schrieb am 16:00 Donnerstag, 22.Juni 2017:
Excellent point. However, dropping into another language does have all sorts of disadvantages: apart from the learning issues, there's the lack of compile-time syntax checking and type checking, the cost of dynamic compilation/interpretation, etc. One thing to look at, perhaps, is how it translates into Scala, where you can define your own operators: A.flatMap(B) --> A/B A.attribute(B) --> A @ B etc; and then we start to have something very XPath-like, but with a syntax that's compiled and validated by the host language. Michael Kay Saxonica
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|