On Monday, July 16, 2001, at 12:23 AM, Jeremias Maerki wrote:
A couple points here. First the API is still evolving and in fact is really due for another revision so the docs are definitely not complete.
I agree. I get the impression that very few people are really participating in the defition of the API. I'd like to encourage implementors and users of the XML:DB API and other developers of XML databases who haven't started an implementation, yet, to bring in their experiences and suggestions.
Unfortunately, you're correct. Most of the input has come from the dbXML project which always makes me concerned that the design will be skewed in that direction. Per Nyfelt has also been working on an impl for Ozone and I believe he got it to level 0 but I haven't seen the code yet. The Reference Impl is also complete in regard to the current spec but is sitting in CVS waiting for me to get the time to polish it up and release it. The problem there is that I wrote both the dbXML impl and the reference impl along with all the docs for the API so I'm not a particularly good judge of the current state of the API.
My plan has been to do another update of the API incorporating all the feedback of the past couple months, updating the ref impl and the dbXML impl to comply and then issuing a call for implementations. I don't want to do this with the current API though because there are a few things that really need to be added.
Maybe it's necessary to go and knock on other XML database developer's doors to ask them to provide an implementation of XML:DB. It was quite impressive how little time it took me to create an XML:DB layer on top of JDBC.
Is the code/binary for this impl something you can make available? No big deal if not, but I know several people would be interested.
I think Ronald Bourret has a lot of influence in this regard. He could probably give XML:DB a little more importance in the next revisions of his site. If you agree, Ronald....
Another point is to get non-Java developers to create XML:DB implementations.
Yes this is very important. Uche Ogbuji was planning to do a Python impl for 4Server. We're also planning to do a Python impl for dbXML at some point but it is low priority.
That's what I'd like to see. And I'm sure that it doesn't confuse people if the behaviour is clearly documented. The only problem is that some implementations may not be able to provide that ID.
Are you able to provide this in your JDBC impl?
"Delete all documents created in a given date range."
Where the XML instances have the following sample structure: <doc created="2001-07-02"> <data>...</data> </doc>
One possibility is to extend the XPathQueryService to contain a method such as this:
public interface XPathQueryService extends Service { ResourceIterator query(String query) throws XMLDBException; void remove(String query) throws XMLDBException; }
Would you add this along with the setting of the ID? It seems the expected behavior here would be to remove the result node rather then the document.
Jeremias M�rki
mailto:[EMAIL PROTECTED]
OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029 Internet http://www.outline.ch
---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
Kimbro Staken The dbXML Project htttp://www.dbxml.org
---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
