A serious bug (CORE-160) has been reported with using AllegroGraph 4x - connecting to an existing store causes that store to be deleted and recreated. If you use AllegroGraph 4x we strongly recommend you build the latest source from SVN to get the fix for this issue.

This bug was caused by a poorly documented breaking behavioral change in AllegroGraph 4x vs AllegroGraph 3x - please note that 3x users are unaffected and may continue using AllegroGraph safely.

There are currently no Tags for this Content!

We've also today released the latest version of our Tools package which you can get by doing to Download dotNetRDF Toolkit for Windows

This is a major feature release and includes heavily rebuilt version of rdfEditor and Store Manager.

rdfEditor

We've now added mutli-document editing capability to rdfEditor so you can work with multiple documents at once in a single window.

See below for a screenshot of the new UI:

Pretty simple change from your perspective but a lot of work from ours, hope you enjoy the new feature.

Store Manager

Store Manager has had some major UI changes, the first thing you'll noticed is that we've simplified the file menu. It now looks like the following:

So you now just have New Connection option rather than the two options depending on whether you wanted a SQL/Generic store.

Also you now get a user friendly start page to get you started faster when you first start up:

You will also find that the New Connection dialogue has been made much more user friendly:

Finally you'll also have access to some brand new features when working with connections like the ability to drag graphs between stores to copy/move them and the ability to copy/rename graphs within a store.

Tags: rdfEditor, Releases, Store Manager, Tools

We've just released dotNetRDF 0.5.1 Beta, as always you can get the latest and greatest version by going to Download dotNetRDF

This is primarily a minor feature/bug fix release that fixes a number of issues discovered by ourselves and reported by the community. Thanks as always to everyone who reported bugs and submitted patches.

The release does add a few new features which I'll highlight for you:

Dydra Support

Stardog Reasoning Support

New SPARQL 1.1 Features

Tags: Dydra, Releases, Stardog

We've just made the first Alpha release of our Full Text SPARQL support, this uses Lucene.Net to provide full text SPARQL query functionality.

You can find the additional library and dependencies under Query/FullText in the standard distribution obtained by going to Download dotNetRDF. If using NuGet you will find a separate dotNetRDF.Query.FullText package is now available.

Please see Full Text Querying with SPARQL for documentation on using this functionality in your code.

You can test this out now against our new SPARQL Vocabulary endpoint using a query like the following:

# Get matches with scores
PREFIX pf: 

SELECT * WHERE { (?match ?score) pf:textMatch "text" . }

If you are familiar with LARQ then the full text query syntax should be familiar to you.

Tags: 0.5.0, Alpha, API, Beta, dotNetRDF, Downloads, Full Text, Lucene, Query, Releases, SPARQL

I'm giving a talk at the London Semantic Web Meetup next week titled dotNetRDF Everyday Tools for the Semantic Web Developer

In the talk I'll be covering a few of the Tools from our toolkit including:

• rdfEditor
• SparqlGUI
• Store Manager
• rdfConvert

Plus I'll be looking at a bunch of other tools from other open source projects including:

• Fuseki
• Sesame Windows Client
• Twinkle
• rapper
• riot
• rdfcopy

How much of this I get through will depend on how many questions people ask but I hope to at least cover these briefly and there will be one/two slides on each.

Tags: Fuseki, Meetup, Presentation, Presentations, rapper, rdfConvert, rdfcopy, rdfEditor, riot, Sesame Windows Client, SparqlGUI, Store Manager, Talk, Talks, Toolkit, Tools, Twinkle, Utilities

Some of our long term users will be aware that we have been working to replace our existing SQL backend referred to as the legacy store for some time now. The recent 0.5.0 release marks the introduction of our new SQL Backend referred to as the ADO Store. This new store is more performant, easier to maintain and provides better abstraction between our code and the underlying database schema.

We've now added documentation of the new rdfSqlStorage tool provided as part of our Tools package which can be used to migrate existing stores. Please see the migration section of the SQL Backend documentation for more details on how to go about migrating legacy stores.

Note that you cannot do an in-place migration, you must migrate from an existing database into a new database.

For those who are still using the legacy store we strongly encourage you to migrate them to the new format, please be aware that we will discontinue support for the legacy store from the 0.6.0 release onwards and we only intend to make one further release prior to that release.

Tags: ADO, ADO Store, Azure, Backend, Database, Deprecation, Migration, SQL, SQL Azure, SQL Server, Storage, Store, Triplestore, Upgrade

We've just released dotNetRDF 0.5.0 Beta - get it now by going to Download dotNetRDF or get the source code from Download dotNetRDF Source.

Please note that as detailed in a previous blog post some features - Virtuoso and SQL support - are now split into their own libraries. The distribution includes both of these libraries and should be self explanatory.

This release includes the following changes and improvements:

• Bug Fixes
  • Variety of bug fixes to 0.4.1 release including some major crash fixes for Silverlight and Windows Phone 7 builds
• Core API
  • Added .Net Serialization Support for some classes - INode, IGraph, SparqlResultSet and SparqlResult
  • Added callback delegates and asynchronous APIs for various features to improve Silverlight and Windows Phone 7 support
• Configuration API
  • Lots of new properties allowing for writer properties to be configured for HTTP Handlers
• Query
  • Added the ability to explain queries
  • Refactored LeviathanQueryProcessor to make it easier to extend our query engine
  • Added more algebra operators so strict algebra forms can now be generated
  • Added experimental parallel evaluation support for some algebra operations (disabled by default)
• Storage
  • Added revised SQL backend as new Data.Sql library

There are currently no Tags for this Content!

So I thought I'd take some time to outline some important upcoming changes in the dotNetRDF library structure. Currently we have a single library dotNetRDF.dll which you will often see referred to as the Core library. The problem we have is that as we've added more features to the library over time we're increasingly adding features that are of use to only a small section of the user base e.g. SQL backed stores but which come with dependency penalties. Therefore we have made an official decision to start reducing our dependency bloat and deliver new features and APIs that we don't consider to be Core functionality as separate libraries.

So what does this mean for you as a developer using dotNetRDF?

• You can pick and choose which added features you want, if you've never used SQL backed stores you won't have to care about that feature and you (eventually) won't need dependencies like MySql.Data
• From a code perspective very little changes, if you need the extra features you simply add an extra reference

This change will also have a number of benefits for us such as making it easier to port the core library onto different platforms - for example the next release 0.5.0 will have builds for .Net 3.5, .Net 3.5 Client Profile, Silverlight 4 and Windows Phone 7.

The next release (0.5.0) will consist of the following 3 libraries:

1. dotNetRDF.dll - This is the core library which contains the majority of the functionality and dependencies most users need.
2. dotNetRDF.Data.Sql.dll - This is a new library which provides a completely new SQL based store which we've been working on for a while, see dotNetRDF Store for some more details on this.
3. dotNetRDF.Data.Virtuoso.dll - This is a new library that splits the Virtuoso support out from the core library since the support comprises a minimal number of classes but requires a whole dependency in the core library.

Our release process is also adding NuGet packages so all of these will be available directly via NuGet for VS2010 users!

If you have any questions on this upcoming changes you can always get in touch via the Support page.

Tags: Changes, Core Library, Dependencies, Libraries, Library, Releases, SQL, Virtuoso

dotNetRDF is now available via NuGet - find it in the gallery at http://nuget.org/List/Packages/dotNetRDF

Currently the NuGet package only includes the stable .Net 3.5 build, future versions of the package will incorporate other builds of the library e.g. Silverlight into them but as those builds are less stable we have not done so for the current release.

There are currently no Tags for this Content!

We have launched a new web based Issue Tracker for reporting issues, requesting new features and our own management of the project.

You can now use the Issue Tracker instead of mailing the email lists. All support mechanisms are detailed on the Support page.

There are currently no Tags for this Content!