Re: [basex-talk] Optimizing Element Access By Attribute Value Matching

2015-04-21 Thread France Baril
Happy to know it can be done. I will definitely ping you when the project turns commercial.

Re: [basex-talk] Optimizing Element Access By Attribute Value Matching

2015-04-21 Thread Christian Grün
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]

Re: [basex-talk] Optimizing Element Access By Attribute Value Matching

2015-04-13 Thread Liam R. E. Quin
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

Re: [basex-talk] Optimizing Element Access By Attribute Value Matching

2015-04-13 Thread Christian Grün
Hi Eliot, I (am sorry to) agree there is no straightforward solution to speed up the lookup of single tokens in attributes. XQuery 3.1 provides a new string function contains-token [1]... //*[contains-token(@class, 'topic/topic')] ...but (up to now) it is not index-driven in BaseX. Some

[basex-talk] Optimizing Element Access By Attribute Value Matching

2015-04-13 Thread Eliot Kimber
DITA defines the notion of layered hierarchy of element types, where every DITA-defined element is either a base type or a specialized type derived from some base type. The type hierarchy of each element is specified by a @class attribute that lists the ancestry and leaf type of the element. For