I have resources to dedicate to metadata, security and versioning, but I don't want to be blocked in the middle of a "XML:DB API" muds. This is my reasons for wrapping instead of patching.
Makes sense.
This said, I'm very willing to reconsider this ideas based on what this community finds appropriate... the only thing that is slowly killing the evolution of this project is an API that was created *before* the mile-long TODO design list was written. An API that not many seems to be endorsing.
Well... yes. At least looking at the traffic on Xapi-dev, this is the right conclusion. Yet I think there is room to revive the API, and this target might be left aside for a while, not forgotten.
My suggestion is: forget the API and concentrate on functionality. The API will follow.
But I'm pretty sure the xindice committers don't agree with my vision, or am I wrong?
IIRC this was already discussed and approved, so I don't see any problem in going this way. However, I'd also investigate if the extension mechanism contained in the API (the Service) can be exploited to extend Xindice with the functionality we all need. We have an XPathQueryService and an XUpdateQueryService, it might be easy to add a MetadataService, a VersioningService, and so on. If this is not enough, let's move on and not let the XML:DB API stop Xindice evolution.
How about it?
Ciao,
-- Gianugo Rabellino
