Hi France,
I guess we won't be able to spend time for this unless we don't have a commercial project within sight. However, I have created a new DITA wish list [1] to collect features that DITA users miss most in BaseX. All your feedback is welcome!
Christian
[1] https://github.com/BaseXdb/basex/issues/1130
On Tue, Apr 21, 2015 at 4:00 PM, France Baril france.baril@architextus.com wrote:
Chirstian,
I'm also starting to a few DITA projects with BaseX that use attributes for matches. Other projects were DITA-like and did not need to match attribute tokens in @class. There is a big and growing DITA community out there who need native XML database support, I think it might be interesting to include indexing attribute tokens in the roadmap at some point, even if only as a longer term items.
This is a very important aspect of the DITA standard. HTML classes also use tokens more and more. So that's not just relevant to the DITA community.
Regards,
France
On Mon, Apr 13, 2015 at 2:50 PM, Liam R. E. Quin liam@w3.org wrote:
On Mon, 2015-04-13 at 12:38 -0500, Eliot Kimber wrote:
For large repositories an XQuery like "//*[contains(@class, ' topic/topic ')]" is going to be quite slow
I took this use case to the XQuery & XSLT Working Groups a year or two ago (Jirka added the DITA case - I was thinking of (X)HTML) and the result was contains-token() which might be easier for the database to optimize.
Judging by comments submitted against my awful tests for it :) I think BaseX may well support it already.
Liam
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com