Re: FW: Dictionaries, practical question

Like Martin, I'm an eXist user who once in a while finds himself looking 
over the fence to check how green the grass is at e.g. the BaseX side. 
Yet, I haven't been convinced either; one show-stopper to me was the 
restriction that BaseX does not support index-based searches over mixed 
content (http://docs.basex.org/wiki/Full-Text#Mixed_Content), while this 
is fully supported in eXist.

I really like eXist as well. While the official release pace is quite 
slow, there's continuous development, with plenty of room for (friendly, 
indeed) user-developer interaction. Even if I've grown used to bumping 
into small eXist quirks and bugs when developing webapps, I've come to 
appreciate the multi-level development nature of open source software as 
well. Without having any usable Java programming skills myself, I'm more 
than happy to contribute bug reports or start discussions on the mailing 
list that often lead to bug fixes (or better understanding on my part).

Best,

Ron


On 16/01/2017 14:39, Wolfgang Meier wrote:
>> Also note there is no open bugfixing after a major release. You have to pay enterprise support prices for that.
> I have to correct this: eXist is completely open source and paying customers don’t get any fixes you cannot also get from the public repository. The open source code is always first!
>
> The reason why we introduced a paid LTS version for customers was to get them to use a defined version we have checked and approved. But I can safely state that the income generated by LTS (not to be confused with enterprise support) is not covering the costs involved for back porting fixes and producing a release, so we’re currently rethinking this concept. For sure the best and preferred solution would be to get more help from the community in this area. People often think you need to be a code hacker to contribute to open source, but that’s not true. Keeping an eye on issues, testing things, writing documentation, making sure the next release is finally getting out, is more important from my perspective than contributing another nifty feature XY.
>
> Wolfgang



On 16/01/2017 0:17, Martin Holmes wrote:
> I use eXist almost exclusively, but once in a while I go and look 
> longingly at BaseX, impressed by how well-managed its codebase and 
> release process seems to be. But I always find that eXist's indexing 
> system is much more sophisticated, for instance in allowing individual 
> tags to be specified as token-internal, and other tags to be ignored 
> when indexing:
>
> "BaseX does not support the ignore option (without content) of the W3C 
> XQuery Full Text 1.0 Recommendation. If you want to ignore descendant 
> element content, such as footnotes or other material that does not 
> belong to the same logical text flow, you can build a second database 
> from and exclude all information you do not want to search for."
> <http://docs.basex.org/wiki/Full-Text>
>
> All of my projects use such indexing features, and building multiple 
> versions of the entire database to get them seems like an excessive 
> workaround.
>
> Other things I like about eXist are the responsive and friendly 
> developer community and the very rich range of features and deployable 
> apps.
>
> Hope this helps,
> Martin
>
>
>
> On 2017-01-15 01:15 PM, Daniel STOEKL BEN EZRA wrote:
>> Dear colleagues
>> May I ask those who have tried BaseX AND eXist what are the advantages
>> of using eXist compared to BaseX or, vice versa, the advantages of BaseX
>> compared to eXist? What can you do in eXist which you cannot do in BaseX
>> or the other way round?
>> Many thanks
>> Daniel