All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning and Keep a CHANGELOG.
This version upgrades to RDF.ex v2.0.
Elixir versions < 1.13 and OTP version < 23 are no longer supported
- support for dataset parameters
:using_graph
and:using_named_graph
on update operations :prefixes
option used bySPARQL.Client.insert_data/3
andSPARQL.Client.delete_data/3
to specify custom prefixes to be used when rendering the update
- graph names on dataset parameters can be provided as RDF namespace terms
SPARQL.Client.insert_data/3
andSPARQL.Client.delete_data/3
withRDF.Dataset
s where the graphs had different prefixes associated, resulted in invalid queries since not all prefixes were included in the update prologue
- support for nimble_options 1.0
- The
:update_request_method
was not correctly fetched from the application config.
This version is just upgraded to RDF.ex 1.0.
Elixir versions < 1.11 are no longer supported
With the latest SPARQL.ex version 0.3.7, RDF-star and SPARQL-star results can be handled now.
Elixir versions < 1.10 are no longer supported
- general
:logger
option on allSPARQL.Client
functions (instrumenting theTesla.Middleware.Logger
)
- In consistency with the change in RDF.ex 0.10 to no longer support automatic
merges of
RDF.Dataset
s, the:merge_graphs
option is no longer supported on theSPARQL.Client.insert_data/3
andSPARQL.Client.delete_data/3
functions.
- support for RDF-XML for graph results
Elixir versions < 1.9 are no longer supported
- raw-mode with the
:raw_mode
option, which allows disabling of the processing of query strings, passing them through as-is to the SPARQL endpoint - support for
INSERT DATA
andDELETE DATA
updates withSPARQL.Client.insert_data/3
andSPARQL.Client.delete_data/3
which are able to handle all types RDF.ex datastructures (RDF.Description
,RDF.Graph
,RDF.Dataset
) directly - support for
LOAD
updates withSPARQL.Client.load/2
- support for
CLEAR
updates withSPARQL.Client.clear/2
- support for all graph management operations with
SPARQL.Client.create/2
SPARQL.Client.drop/2
SPARQL.Client.copy/2
SPARQL.Client.move/2
SPARQL.Client.add/2
- the defaults for several options can now be configured globally via the application
environment; please refer to theSPARQL.Client
documentation for more information
- the default request method for queries when using SPARQL protocol version 1.1 is now
:get
- improved error handling
- the default HTTP
Accept
header used when no:result_form
was provided onSPARQL.Client.query/3
contained a typo
- the
request_opts
options toSPARQL.Client.query/3
which will be passed as theopts
option value to theTesla.request/2
function
- Update to SPARQL.ex 0.2.1 whose Hex package no longer contains Erlang output files of Leex and Yecc, which caused issues using the SPARQL.ex Hex package on OTP < 21 (because the package was released with OTP 21)
- adapt to new query result representation in SPARQL.ex 0.2
- Elixir versions < 1.6 are no longer supported (as a consequence of upgrading to the latest versions of RDF.ex and SPARQL.ex)
- Upgrade to Tesla 1.1
Initial release