Here are the items that we're looking at right now. These are brief summaries that should be drilled down on.
- Updating XPathQueryService to support XML namespaces.
- Looking at adding more flexible result types from XPathQueryService. The only result type currently is a ResourceIterator which can be limiting.
- Determining the behavior for the ID on a resource that is returned from a query.
- Adding a CollectionManager service to allow simple management of collections.
- Adding a XUpdate service so that XUpdate queries can be executed against a collection.
- Collection should have an isOpen method to determine if the collection is still open.
- Collection methods should throw an exception if the collection is closed.
- ResourceType as passed to create resource is passed as a string. This should be a constant value somewhere in the API.
- Checking for optional API features should probably be reexamined. currently only conformance level can be used to test this.
What am I missing?
Along with these changes the reference impl needs to be updated and actually made available outside of CVS.
After this update I also want to make the existence of the API more widely known and issue a call for implementations.
Kimbro Staken The XML:DB Initiative htttp://www.xmldb.org ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
