Tree [24f93f] default tip /

File Date Author Commit
Build 2015-07-24 rvesse rvesse [e7970f] Prepare for 1.0.9 release
Libraries 2015-07-24 rvesse rvesse [178b30] Fix bad reference
Samples 2014-11-07 rvesse rvesse [79cd40] Remove MSBuild-integrated NuGet package restore
Testing 2015-07-10 rvesse rvesse [462fef] Minor improvements
Utilities 2015-07-24 rvesse rvesse [e7970f] Prepare for 1.0.9 release
.hgignore 2015-04-30 tpluscode tpluscode [e81ce8] Merge with default
.hgtags 2015-07-24 rvesse rvesse [24f93f] Added tag 1.0.9, 109 for changeset 178b30711565
Acknowledgments.txt 2014-05-23 rvesse rvesse [e561b1] Update documentation files in preparation for a...
License.txt 2015-05-29 rvesse rvesse [72bf9f] Updated license headers to current Copyright Ye... 2015-04-30 magicmoux magicmoux [b9947c] Reverting
Todo.txt 2011-09-08 rvesse rvesse [747cf1] Some additions to rdfWebDeploy to allow inclusi...
doap.ttl 2013-08-19 rvesse rvesse [9c8098] Add base declaration to DOAP file
dotNetRDF.Core.sln 2014-11-07 rvesse rvesse [79cd40] Remove MSBuild-integrated NuGet package restore
dotNetRDF.Core.sln.DotSettings 2013-04-16 tpluscode tpluscode [ae2abd] resharper inspection settings
dotNetRDF.sln 2015-04-21 magicmoux magicmoux [60db75] Refactor the TransactionLog into a StorageRunti...
dotNetRDF.sln.DotSettings 2013-05-09 tpluscode tpluscode [8b39e6] Merge with default
dotNetRDF.vsmdi 2012-10-22 rvesse rvesse [18aa0d] Add missing vsmdi file required to have good te...

Read Me


dotNetRDF is a powerful and flexible API for working with RDF and SPARQL in .Net environments, for
details and documentation on the project please see our website at

To get started with using dotNetRDF you may want to check out the following resources:


dotNetRDF is licensed under the MIT License, see the LICENSE.txt file in this repository

Obtaining dotNetRDF

dotNetRDF produces two main products:

  • A Programmers API for working with RDF and SPARQL in code using .Net
  • A Toolkit which provides an assortment of GUI and command line tools for working with RDF and SPARQL on Windows platforms

The Programmers API requires .Net 3.5 or higher (builds are provided for a variety of different framework versions and profiles) and can be obtained as either a Binary Download or a Source Download. The Source Download represents the source for the current Binary Download, if you want the latest source obtain it from our Mercurial repositories which you are viewing now or can be found listed further down this file.

The Toolkit requires .Net 4.0 Full and can be obtained either as a ZIP Download or as a Windows Installer Download

dotNetRDF on NuGet

If you are a developer who uses NuGet you can also obtain dotNetRDF via NuGet, simply search for dotNetRDF in the NuGet Package Gallery to see the available packages.


dotNetRDF is developed by the following people:

  • Rob Vesse
  • Ron Michael Zettlemoyer
  • Khalil Ahmed
  • Graham Moore
  • Tomasz Pluskiewicz

For more information on our developers see the Developers page. dotNetRDF also benefits from many community contributors who contribute in the form of bug reports, patches, suggestions and other feedback, please see the Acknowledgements file for a full list.

Reporting bugs and feature requests

Bugs and feature requests are tracked at

Source Code

The dotNetRDF Project uses Mercurial as our VCS.

Currently we our maintaining the following repositories as our official repositories. We use BitBucket
for our day to day development and periodically push changes to the repositories at SourceForge which
we use as a central repository of our project releases and source code.




Note that our developers may be maintaining their own additional public/private repositories in order
to work on new features.

Old Subversion

You can find our old source code in our SVN repository at

Note that the majority of the commit history should be present in our Mercurial repositories as we did a conversion
of our SVN repository when we moved to Mercurial. Some commits pre 2010 are missing because our SVN layout
was not consistent with the standard SVN layout prior to that.