We need your feedback

Author: Anton Andreev

With the release of version 0.11.1 we now have a community channel.
This will be a great place for feedback from you - our users!

We are meditating whether we should put more effort in the following ideas:

1. Add support for more RDF stores
Probably next in the queue will be Talis platform and 5store. We will do that by using Rob Vesses's dotNetRDF lib. The thing is that after we started testing support for our first RDF database through dotNetRDF, I found a serious bug in the driver provided by this RDF store and used by dotNetRDF. So I believe that adding new RDF stores, that we can call "supported", won't be that easy.

2. Enhance addins support
You can now execute your own custom code on any SWC supported repository. You can even package a commercial addin. Next step could be to add hooks in the import/export operations, so that you be able to process every single triple before/after importing it (or exporting it).

3. Create a server application
SWC is a desktop tool. You can use SWC to load and test your database and once you are done you could close SWC and start an ordinary console application that exports your repository as a SPARQL endpoint. What do you think? Would you need this application? This application will be multi-threaded, written entirely in .NET and it won't use ASP.NET/IIS or a Java server container. Under Unix Mono's new generation GC will be important for this server application.

Stay tuned :)

-Anton

SWC 0.11 release

Author: Anton Andreev

SWC 0.11 comes with many new features:

* updated version of Ontotext's SwiftOWLIM build 3.4.3012
* support for more semantic databases thanks dotNetRDF library (using our own patched version)
    * currently we utilize the OpenLink's Virtuoso implementation, but dotNetRDF provides support for many more. This support should be considered experimental and should not be used for production purposes for now.
* support for Franz's AllegroGraph
* addin(aka plug-in) support - SWC is becoming a platform where you are able to extend the base functionality. Addins are provided in a separate download package.
    * an ASK evaluate addin is available
    * an addin that loads namespaces automatically and evaluates SELECT query is available
    * a stub addin implemented in F# is also available
* native Aduna repositories can now be loaded from disk
* you can now move you data dir (with all your repositories) to a new disk location (which is faster or has more space for example)
* you can now keep track of the files you import
* update form is now available
* bugs fixed

Additional notes and known issues:

* You need to extract addins (dlls) in the /addins folder. Your own addins must also be placed in this folder in order to be registered and loaded. New addins will appear in the SPARQL EVALUATE tab between the input and result textboxes.
* Tested with Virtuoso Open-Source edition 6.1.2 and currently it is using a hack so that we overcome a bug in Virtuoso .NET provider. OpenLink has assured us that it will be soon fixed. Thanks about that.
* Tested with AlegroGraph 3.3. Not tested with AlegroGraph 4.0.
* Native disk based support for Sesame will work with Sesame 2.3.2, not tested with older versions, but it should work.
* Keep in mind that Mono 2.6.x series are more stable than the 2.8.x series. Also the WebBrowser control in Mono used for the help section is not very stable and it crashes occasionally.

You can get it from here: http://sourceforge.net/projects/sesamewinclient/files/

-Anton