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 dotnetrdf.org
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
dotNetRDF produces two main products:
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
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:
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.
Bugs and feature requests are tracked at http://dotnetrdf.org/tracker/Default.aspx
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.
You can find our old source code in our SVN repository at
http://svn.code.sf.net/p/dotnetrdf/svn/
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.