Well done!

On Wed, Feb 3, 2010 at 8:34 AM, <ep at ardec.com> wrote: > Congrats for your efforts and well done product. I've worked with Berkeley dbxml, eXist, and Mark Logic. So I really appreciate the clean api, speed!, and compactness. Keep up the great work! Do you have roadmap somewhere? I'd like to get an idea where you are headed with development and if you could use any assistance. > Best, > Erik Peterson

> A few questions for you about basex and plans... > 1) Can a database store files other than xml? xqy/xql, images, js, css, etc?

> 2) Any plans to add collections or may basex does and I've overlooked it?

> 3) ReST interface: There are two approaches, both have their benefits and I would like to see both available: > a) The rest interface allows manipulating db resources: dbs, collections, files, users, permissions, etc. (The eXist db does this.) > -The main advantage with this is an API easy to integrate into many environments > b) The rest interface allows requests to be rewritten to a delegate xquery file to handle processing the http methods. (Some other db's provide this.) > -This allows building complete applications within a database. > -Would like to see this as the base approach with (a) as an internal implementation of (b) > What are your thoughts?

> 4) Any plans for webdav? This makes moving files in and out of the db easy for non-technical users. I've briefly looked at doing this with milton, apache jackrabbit, and from scratch. > 5) What do you think about using OSGI to enable plugging in db services? Bundles would be something like dbServer (the core service), tcpServer, restAdminServer, restServer, webdavServer, webAdmin, cliAdmin, monitorServer clusterServer, etc. This keeps the dbServer core code clean and small, yet allows other services to be developed and evolve independently. It also allows spinning up multiple instances of a server. For example, I could spin up multiple restServers or tcpServers on different ports to segment applications, or multiple webdav servers to partition content management per user/group rights. > 6) What do you think about moving to github? Looking for ways to grow basex community more quickly.

> Hope you don't mind me jumping in. I see a great product whose continued and expanded development is important to this industry.

On Feb 4, 2010, at 9:46 AM, Christian Grün wrote: > Hi Erik, > > all of your suggestions are more than welcome – this is why I posted > your answer back to the mailing list. I invite all of you to give > personal feedback! > >> A few questions for you about basex and plans... >> 1) Can a database store files other than xml? xqy/xql, images, js, css, etc? > > Our storage is currently limited to well-formed XML documents.

> > >> 2) Any plans to add collections or may basex does and I've overlooked it? > > Yes, BaseX supports collections – as long as they are flat. Databases > can store multiple single documents, which can be accessed e.g. by the > XQuery collection() function. See also Section 4.4 in > http://basex.org/faq.

> > >> 3) ReST interface: There are two approaches, both have their benefits and I would like to see both available: >> a) The rest interface allows manipulating db resources: dbs, collections, files, users, permissions, etc. (The eXist db does this.) >> -The main advantage with this is an API easy to integrate into many environments >> b) The rest interface allows requests to be rewritten to a delegate xquery file to handle processing the http methods. (Some other db's provide this.) >> -This allows building complete applications within a database. >> -Would like to see this as the base approach with (a) as an internal implementation of (b) >> What are your thoughts? > > Interesting ideas.. Some of our current interface features are be > inspired by eXist. While GET and POST can be used to send > XQuery/Update requests, PUT and DELETE will allow to modify database > instances. Here is a simple example how a GET request could look like: > > http://localhost:8080/rest/db/factbook?query=//country > > Additionally, we will allow to send BaseX database commands via GET and POST.. > > http://localhost:8080/rest/db/factbook?command=optimize > > This way, user management can be handled via REST as well. I'm not > sure how users are modified in eXist via REST? Which other XML/REST > implementations have you worked with?

> > >> 4) Any plans for webdav? This makes moving files in and out of the db easy for non-technical users. I've briefly looked at doing this with milton, apache jackrabbit, and from scratch. > >> 5) What do you think about using OSGI to enable plugging in db services? Bundles would be something like dbServer (the core service), tcpServer, restAdminServer, restServer, webdavServer, webAdmin, cliAdmin, monitorServer clusterServer, etc. This keeps the dbServer core code clean and small, yet allows other services to be developed and evolve independently. It also allows spinning up multiple instances of a server. For example, I could spin up multiple restServers or tcpServers on different ports to segment applications, or multiple webdav servers to partition content management per user/group rights. > >> 6) What do you think about moving to github? Looking for ways to grow basex community more quickly. > > Good suggestions.. Let's see what everyone thinks about it! > > >> Hope you don't mind me jumping in. I see a great product whose continued and expanded development is important to this industry. > > You are welcome, > Christian > > ___________________________ > > Christian Gruen > Universitaet Konstanz > Department of Computer & Information Science > D-78457 Konstanz, Germany > Tel: +49 (0)7531/88-4449, Fax: +49 (0)7531/88-3577 > http://www.inf.uni-konstanz.de/~gruen

Am 09.02.2010 um 07:36 schrieb Erik Peterson: > Is xinclude supported? > Erik > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

>>> 2) Any plans to add collections or may basex does and I've overlooked it? >> [...] > Flat meaning one collection of multiple docs per database right?

>>> 3) ReST interface: There are two approaches, both have their benefits and I would like to see both available: >> [...]

> For example, how ReST purist should we be? GET methods don't modify resources for example. Do we enforce that in the BaseX rest API? How does an application respond with different content (xml, json, other)?

> First off, thanks for building and continuing to maintain what I think is one of the most underrated/undiscovered pieces of open source code out there. Now to my question...

> We've been using BaseX 5.7 with very heavy use of the backend for a while now (though we've tried hard not to actually change the BaseX code in our use). On 5.7 we use the "insert" methods of the org.basex.data.Data class to enable mutability (I.e., to add new attributes or elements at specific locations in the document). We prototyped our code from the "insert" proc file. I've noticed that both the insert methods we had been using and the whole "insert" proc command are gone in 6.0. Does 6.0 no longer support mutability? I do notice there are some other insert/update methods instead, but no good calls to them to try and understand how they work. What would be a good procedure for inserting new data given that we have both a Nod and Data reference?

On Feb 9, 2010, at 6:57 AM, Michael Seiferle wrote: > Hi Erik, > > IIRC correctly XInclude is not supported at the moment. > > While this is not be exactly what you are looking for, it might still be worth a try: > The DeepFS importer is already capable of importing XML and various other content formats in your database. > > Via: DeepFS > Create DeepFS Mapping > Metadata (Include metadata, include textual contents.) > > Regards > Michael > > > Am 09.02.2010 um 07:36 schrieb Erik Peterson: > >> Is xinclude supported? >> Erik >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk at mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >

> I've noticed that in the ACreate and CreateDB classes, indexes like the full text index are explicitly rebuilt when a new Data instance is created. If one were to directly create a new Data instance using a Builder, would those indexes need to be built after creation and parsing the way they are in the two mentioned classes?

> Secondly, I can't find code that updates the indexes on changes to the database. I would assume that performing updates (either through XQuery Update or directly) such as adding a new element should update the corresponding indexes. Where does this happen? Is it incremental (that is, only those parts of the index that need to be changed are modified) or full (all the indexes are totally rebuilt on every change)?