Dear all,
Version 11.2 of VocBench and 2.2 of ShowVoc have been released today, and are available at the following pages:
VocBench: http://vocbench.uniroma2.it/downloads/
ShowVoc: http://showvoc.uniroma2.it/downloads/
These versions have been developed in the context of the BE-LISA project, funded by the LifeWatch ERIC e-Science infrastructure for Biodiversity and Ecosystem Research
GraphDB and RDF4J compliancy:
You can still use the same versions adopted with VocBench/ShowVoc: 11.2/2.2
GraphDB compliancy is the same as for VB 11.1/SV 2.1, with the caveat of not moving to the most recent GDB 10.x
So, we provide a link to 9.8.1 (the last one not requiring the separated indexing plugin) in our installation docs: http://vocbench.uniroma2.it/doc/sys/#separate_triple_store
If you have a more recent version (still in the 9.x range, so < 10.0), after version 9.8.1 of GDB, the indexing system adopted by VocBench is no more embedded into GDB, it needs to be deployed manually into the plugins directory of the triple store.
This is available by download here:
https://bitbucket.org/art-uniroma2/semantic-turkey/downloads/lucene-fts-plugin.zip
Release notes
Release notes are reported below for the two applications and for their common service backend.
SemanticTurkey 11.2
* improved the OntoPortal connector to consider the frontend base URL and retrieve missing settings from /site_config
* improved the OntoPortal deployer to identify violations of constraints on data structure and then try to propose fixes
* added a Deployer targeting ShowVoc
* added an exporter for a selected scheme
* added support for HTTP resolution and Content negotiation
* fixed a bug related to an exception about the use of abstract datasets erroneously raised in assisted search when
selecting a local project
* fixed a bug related to transaction management preventing the execution of assisted search on local projects
* updated dependency on Sheet2RDF 5.0.3
VocBench Web App 11.2
ShowVoc Web App 2.2
Migration from a previous version of the system
As usual, for people migrating from a previous version of VocBench 3 / ShowVoc, it suffices to:
For developers willing to recompile the project:
all of the dependencies of VocBench based on other software written by us:
have already been committed to Maven Central, so they may choose what to re-build and what to take as-is from the dependencies
Cheers,
The VocBench/ShowVoc team
P.S. there’s an annoying bug at startup:
After the first installation and run, the system might log some errors on the console. These errors are non-deterministic (they depend on non-synchronic factors, which vary from machine to machine) but are usually related to installation of bundles/web bundles. Examples are:
Failed to install artifact: C:\Users\Tiziano\Desktop\TEMP\semanticturkey-6.0\deploy\vocbench3-6.0.0.war
java.lang.IllegalStateException: Unknown protocol: webbundle
at org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:482)
at org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:474)
at java.net.URL.toExternalForm(URL.java:929)
at java.net.URL.toString(URL.java:915)
….
OR
18:57:40.185 ERROR [fileinstall-C:\TEMP\semanticturkey-6.0/deploy] Registration exception. Skipping.
org.osgi.service.http.NamespaceException: alias: '/vocbench3' is already in use in this or another context
at org.ops4j.pax.web.service.spi.model.ServerModel.addServletModel(ServerModel.java:124)
at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerServlet(HttpServiceStarted.java:243)
at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerResources(HttpServiceStarted.java:307)
at org.ops4j.pax.web.service.internal.HttpServiceProxy.registerResources(HttpServiceProxy.java:76)
In that case, ignore the error, wait for the various procedures to complete and when they are finished, close the system and restart. Since the second time the system is started, they do not usually appear anymore, because the bundles have been installed and they are all available at system start.
We will fix this annoyance with a major revision of the architecture in the next releases.