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