0.12.2

Release 0.12.2

0.11.7

Fixes just one issue:

• #120 BREAKING CHANGE Explicitly support xsd:date and xsd:dateTime. NOTE the resolution here is a breaking change for those who previously used a java.util.Date to serialise as an xsd:dateTime. Now xsd:dateTime's are represented by java.sql.Time objects and xsd:date's are java.util.Date objects. This should primarily effect pipeline writers. e.g. setting a triple like [some-uri dcterms:modified (java.util.Date.)] previously would serialise an xsd:dateTime, now serialises as just an xsd:date. Changing the above to be a java.sql.Time object will restore previous behaviour.

0.11.6

BROKEN RELEASE USE 0.11.7

0.11.5

• Add a missing coercion from RDF4j bool to java bool type

0.11.4

• Fix for -INF and +INF when handling Floats and Doubles

0.11.2

• Improvements to VALUES clause bindings and using UNDEF via :grafter.rdf.sparql/undef

0.11.0

This release rolls back changes in 0.10.x, these weren't ready for primetime and will be scheduled for release in 0.12.x.

It is effectively the same as the 0.9.0 release (except now using clojure 1.9.0-RC1.

0.10.1

WARNING Do not use this release. It was problematic because of the migration to RDF4j from sesame and has been reverted. Please use 0.11.0, which reverts these changes. If you wish to track changes made in this release, they will be available on the currently unstable 0.12.x-SNAPSHOT branch.

This is a major update to Grafter which updates it to use RDF4j instead of the legacy sesame 2.8. RDF4j is the continuation of the sesame project.

This update follows the library update model presented by Rich Hickey in his speculation talk however as the majority of the breakage is confined to the change of transitive dependency from sesame to RDF4j users who only use grafter the API and don't depend directly on sesame shouldn't need to make any breaking changes.

If you do depend directly on sesame however, then you should follow the upgrade advice provided by the RDF4j project.

Additionally we have taken the opportunity to flag the grafter.rdf.io namespace as deprecated, and instead recommend the use of grafter.rdf4j.io, which has had some functions renamed. grafter.rdf.io has been left in place however and should still work though it will now return RDF4j types instead of sesame ones. These types however are almost identical except they were repackaged, so breakage should be minimal, and only occur if you directly depend on grafter returning sesame types rather than the grafter abstractions.

The functions that were renamed are:

• grafter.rdf.io/rdf-serializer renamed to grafter.rdf4j.io/rdf-writer
• grafter.rdf.io/IStatement->sesame-statement renamed to grafter.rdf4j.io/quad->backend-quad
• grafter.rdf.io/literal-datatype->type renamed to grafter.rdf4j.io/backend-literal->grafter-type
• grafter.rdf.io/->sesame-rdf-type renamed to grafter.rdf4j.io/->backend-type
• grafter.rdf.io/sesame-rdf-type->type renamed to grafter.rdf.protocols/->grafter-type

0.10.0

Broken release attempt due to a bad merge.

Use 0.10.1.

0.9.0

Changes:

• Split tabular code out into a deprecated grafter.tabular project.

Upgrade Notes

If you depend on grafter.tabular and wish to upgrade make sure you also add the grafter.tabular dependency vector to your project.clj.

[grafter/grafter.tabular "0.9.0"]