|
We're pleased to announce the release of dotNetRDF 0.7.0 - you can get it now by going to Download dotNetRDF or get the full source by going to Download dotNetRDF Source
This is a major release which includes some important enhancements and breaking changes in the library. Please read on for a summary of the changes....
Obsolete API Removal
We've removed a couple of obsolete APIs in the 0.7.0 release, namely the long superceded ISelector API and the rarely used Node Collection API. Also as previously publicized we are now officially marking the Data.Sql library as deprecated since we do not intend to continue supporting it past the 0.7.x releases.
Storage API Refactor
We've made major changes to the Storage API, as well as introducing all new APIs for asynchronous storage (IAsyncStorageProvider, IAsyncQueryableStorage and IAsyncUpdateableStorage) we've also renamed the existing APIs to align with these names. The name changes are summarized as follows:
We hope you'll appreciate the more descriptive names and we've also made sure that existing code won't immediately break since the old names are preserved as marker interfaces extended their new equivalents. We have marked the old names as obsolete so you will start seeing compiler warnings reminding you to upgrade your code to the new APIs.
We think you'll find the new asynchronous storage API very useful and this will allow you to use many of the supported stores on platforms like Windows Phone 7 where they were previously unavailable.
SPARQL 1.1
We've updated our SPARQL 1.1 support to be as close to the latest editors draft as possible but please note as stated in the Known Issues there are still some grey areas and a lack of official tests for some new features so we are not guaranteeing full SPARQL compliance in this release.
SPARQL Default Graph Behaviour
We've changed our default behaviour around SPARQL queries so that the default graph is not automatically the union graph when no default is explicitly set. This may have an impact on the results of your SPARQL query so if you were relying on this feature either instantiate your ISparqlDataset instances such that you specify union default graph as true or refactor your queries so they explicitly specify the graphs to query over.
IStoreReader/IStoreWriter API refactor
The IStoreWriter and IStoreReader APIs have been refactored to align with the IRdfReader and IRdfWriter interfaces. You no longer need to work with IStorageParams instances in order to use these interfaces which makes them much more user friendly. 04/07/2012 23:30:55 by Rob Vesse in English
312690 Views
There are currently no Tags for this Content!
|