On Monday, January 7, 2002, at 11:07 AM, Tom Bradford wrote:
You could always express the same hardwired linking format in your documents and use a stock XQuery script to expand them instead of having a custom DOM implementation do it behind your back.
Would that achieve the exact same thing though? My goal was to be able to prewire certain relationships so that queries could be simplified and maybe even be sped up by removing the join. It won't work for all applications, but for some if could be very handy. It also gets more mileage out of straight XPath queries.
What I ultimately really want is to have our DOM implementation function identically to any other DOM you could bootstrap using JAXP,
This sounds like a nice goal, but is it really necessary? What does it gain us and what do we lose? I'm just trying to understand the motivation.
and offload functionality like AutoLink into another layer, preferably into an XQuery engine, where the behavior is easily coded, instead of using Java to do it.
I think you need to explain more what you mean here. I'm not seeing the benefit of pushing it into the XQuery layer or even how it would work.
Personally, I don't like XQuery, and would prefer it we XUpdate and XSelect were the standards, but I'm not the one who influences the XML world :-)
Ugh, while XQuery isn't great I'd much rather have that then a cumbersome XML syntax language. XUpdate is nice but, I always find it very, very cumbersome to use. I want better interactive query and update facilities and I just don't see XUpdate and XSelect getting us there. XQuery may not be the right way either, but it is a lot closer.
-- Tom Bradford - http://www.tbradford.org Developer - Apache Xindice (Native XML Database) Creator - Project Labrador (XML Object Broker)
Kimbro Staken XML Database Software, Consulting and Writing http://www.xmldatabases.org/
