Skip to content
This repository

JPA implementation for RDF

branch: master
Octocat-spinner-32 core Inherit @Namespaces February 25, 2014
Octocat-spinner-32 docs some formatting tweaks to the docs i noticed while moving some of the… February 26, 2010
Octocat-spinner-32 examples * ivy buildout for managing project June 24, 2013
Octocat-spinner-32 jena Update Sesame to 2.7.10 and cp-openrdf-utils to 2.0.2. Bumped rev to … February 25, 2014
Octocat-spinner-32 reflections updating empire versioning in the POM files and correcting a couple d… November 22, 2011
Octocat-spinner-32 sdb * ivy buildout for managing project June 24, 2013
Octocat-spinner-32 sesame Update Sesame to 2.7.10 and cp-openrdf-utils to 2.0.2. Bumped rev to … February 25, 2014
Octocat-spinner-32 settings Update Sesame to 2.7.10 and cp-openrdf-utils to 2.0.2. Bumped rev to … February 25, 2014
Octocat-spinner-32 .gitignore adding missing settings stuff due to unforunate .gitignore setup October 17, 2013
Octocat-spinner-32 ACKNOWLEDGEMENTS.txt * updating changes file, build rev, acks November 16, 2012
Octocat-spinner-32 CHANGES.txt updating changes November 08, 2013
Octocat-spinner-32 COPYING updating license file to include apache 2 license and adding the test… January 07, 2010
Octocat-spinner-32 build.xml * removing rev's in the ivy files, not needed June 24, 2013
Octocat-spinner-32 ivy.build.xml * ivy buildout for managing project June 24, 2013
Octocat-spinner-32 master.build.xml Changes to generate pom.xml files and include them in jars. January 15, 2014
Octocat-spinner-32 pom.xml deprecating specific 4store support. im not maintaining that lib anym… November 16, 2012
Octocat-spinner-32 project.properties Update Sesame to 2.7.10 and cp-openrdf-utils to 2.0.2. Bumped rev to … February 25, 2014
Octocat-spinner-32 readme.markdown bumping rev for new dev, small readme update, updating acks November 18, 2011
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.

Something went wrong with that request. Please try again.