JPA implementation for RDF
Java
Clone or download
Permalink
Failed to load latest commit information.
core test for #115 Sep 19, 2016
docs some formatting tweaks to the docs i noticed while moving some of the… Feb 26, 2010
examples Remove some old build artifacts Nov 6, 2015
gradle/wrapper * Open sourced stardog bindings Feb 23, 2015
jena Remove obsolete imports, fix lang usage Nov 17, 2015
reflections * Open sourced stardog bindings Feb 23, 2015
sesame Update Sesame module Nov 17, 2015
stardog
.gitignore * Gradleized project Feb 23, 2015
ACKNOWLEDGEMENTS.txt * Gradleized project Feb 23, 2015
CHANGES.txt re-throw lifecycle exceptions from callbacks instead of only logging … Nov 13, 2015
COPYING updating license file to include apache 2 license and adding the test… Jan 7, 2010
build.gradle
gradle.properties.example * Open sourced stardog bindings Feb 23, 2015
gradlew * Gradleized project Feb 23, 2015
gradlew.bat * Gradleized project Feb 23, 2015
readme.markdown bumping rev for new dev, small readme update, updating acks Nov 18, 2011
settings.gradle * Open sourced stardog bindings Feb 23, 2015

readme.markdown

Empire: RDF for JPA

Empire provides a standard JPA style interface to RDF databases using SPARQL.

Our immediate need for Empire was to be able to build RDF-backed web apps, including Pelorus, while being compatible with JPA/Hibernate-style interfaces to RDBMS.

The primary design goal of Empire is to implement as much of the JPA API as possible so that it can drop into existing applications, providing a simple ORM layer for RDF.

Resources

The docs directory contains some information on Empire including some usage examples and a short roadmap of what we have planned for future versions.

Please also refer to the mailing list for help with Empire.

Licensing

Empire is available under the Apache 2.0 License.