Hi,
we noticed you prepare release 8.5.4.
Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341
Thx
Jan
Hi Jan,
Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341
I can’t promise anything for now reg. this patch release, but we’ll do our best to release BaseX 8.6 pretty soon.
Cheers Christian
I'm also wondering about the issue https://github.com/BaseXdb/basex/issues/1220 which prevents using BaseXHttp for content negotiation. I realize that you have to prioritize what gets fixed in the releases. However, I probably should make a decision about whether to plan on using BaseXHttp to provide Linked Data content negotiation for our project and if that bug isn't likely to be fixed any time soon, we probably should start looking for a different solution.
Steve
Christian Grün wrote:
Hi Jan,
Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341
I can’t promise anything for now reg. this patch release, but we’ll do our best to release BaseX 8.6 pretty soon.
Cheers Christian
Yes, we definitely need to find more time for open source development again. Talking about 1220, I can’t promise anything for now. Unfortunately, the open source part is exactly that part of our work which isn’t financed by anybody, but which everybody asks for (unless we are talking about sponsored features)…
On Tue, Nov 22, 2016 at 7:19 PM, Steve Baskauf steve.baskauf@vanderbilt.edu wrote:
I'm also wondering about the issue https://github.com/BaseXdb/basex/issues/1220 which prevents using BaseXHttp for content negotiation. I realize that you have to prioritize what gets fixed in the releases. However, I probably should make a decision about whether to plan on using BaseXHttp to provide Linked Data content negotiation for our project and if that bug isn't likely to be fixed any time soon, we probably should start looking for a different solution.
Steve
Christian Grün wrote:
Hi Jan,
Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341
I can’t promise anything for now reg. this patch release, but we’ll do our best to release BaseX 8.6 pretty soon.
Cheers Christian
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
I read this issue but I'm not clear how it affects our use case. Attachments? * * *
Every communication from this account is off the record, unless explicitly put on the record.
From: Steve Baskauf steve.baskauf@vanderbilt.edu To: Christian Grün christian.gruen@gmail.com Cc: BaseX basex-talk@mailman.uni-konstanz.de Sent: Tuesday, November 22, 2016 1:19 PM Subject: Re: [basex-talk] Preparing BaseX 8.5.4 (please don't forget Issue #1341)
I'm also wondering about the issuehttps://github.com/BaseXdb/basex/issues/1220 which prevents usingBaseXHttp for content negotiation. I realize that you have toprioritize what gets fixed in the releases. However, I probably shouldmake a decision about whether to plan on using BaseXHttp to provideLinked Data content negotiation for our project and if that bug isn'tlikely to be fixed any time soon, we probably should start looking fora different solution.
Steve
Christian Grün wrote: Hi Jan,
Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341
I can’t promise anything for now reg. this patch release, but we’ll do our best to release BaseX 8.6 pretty soon.
Cheers Christian
Hi Steve,
A rather late reply to [1] (but maybe better than fully ignore it): We have fully revised our quality factor handling. The best RESTXQ function candidates will now be chosen in multiple steps, and your old use case (with wildcard content types) should now work as expected. If you still want to give a try, your feedback is welcome [2].
Best, Christian
[1] https://github.com/BaseXdb/basex/issues/1220 [2] http://files.basex.org/releases/latest/
On Tue, Nov 22, 2016 at 7:19 PM, Steve Baskauf steve.baskauf@vanderbilt.edu wrote:
I'm also wondering about the issue https://github.com/BaseXdb/basex/issues/1220 which prevents using BaseXHttp for content negotiation. I realize that you have to prioritize what gets fixed in the releases. However, I probably should make a decision about whether to plan on using BaseXHttp to provide Linked Data content negotiation for our project and if that bug isn't likely to be fixed any time soon, we probably should start looking for a different solution.
Steve
Christian Grün wrote:
Hi Jan,
Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341
I can’t promise anything for now reg. this patch release, but we’ll do our best to release BaseX 8.6 pretty soon.
Cheers Christian
-- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences
postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A.
delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235
office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Jan Dölle -
lambert strether -
Steve Baskauf