Unfortunately XMLObject or something like that which would somehow obfuscate XQuery/XPath beneath it isn't really possible. The XPath is always going to be necessary, though having a layer in between that could translate some XPath parts to use extensions for optimization that are in the various XML db's would be awesome.
I think Amara is a great starting point, with some minor extensions to query a doc going through the XMLObject interface to have XPath's translated to use the best extensions for whichever database is being used. Having looked over Amara, I don't see much use for a "XML Model" like Sean proposed, since Amara makes it so Pythonic to make, parse, and manipulate XML nodes. Cheers, Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
