Release 1.1.2.

* distinct should work with the \"*\" select form @dannybtran
* Adding support for property paths @dannybtran
* Make SPARQL::Client::Repository writable @curoverse
Added :endpoint option for #update method to specify an alternative update endpoint
Merge pull request #50 from bencpeters/update-url

Added :endpoint option for #update method to specify an alternative update endpoint
Be more descriminating on Accept headers sent based on different queries. Queries build using the DSL use either RDF content types, or SPARQL Results content types, not both.

Those using RDF content types:

 * CONSTRUCT, DESCRIBE, DELETE DATA, LOAD, CREATE

Those using SPARQL Results content types:

  * ASK, SELECT, INSERT DATA, CLEAR, DROP

Hopefully, this makes issues such as come up in #51 less likely to happen.
Ensured that SPARQL 1.1 JSON typed literals are parsed correctly.

The parsing code now supports both SPARQL 1.0 and 1.1 JSON results:

    {"type": "literal", "value": "S", "datatype": "D"}        # SPARQL 1.1 JSON
    {"type": "typed-literal", "value": "S", "datatype": "D"}  # SPARQL 1.0 JSON

See: http://www.w3.org/TR/sparql11-results-json/#select-encode-terms
See: http://www.w3.org/TR/rdf-sparql-json-res/#variable-binding-results
Update code setting appropriate Accept header, and also add */*;q=0.1 to every request as a fallback.
Only use DELETE DATA for #delete_statements if the statement is both constant, and contains no BNodes, otherwise, it falls back to DELETE/INSERT.
Check error response outputs query.
When doing updates, change BNodes to Variables.
Add around block with response delegation to capture query and report on queries run in this example if the example fails. (Not perfect, but still useful).
Remove debug point.
Be more descriminating on Accept headers sent based on different queries. Queries build using the DSL use either RDF content types, or SPARQL Results content types, not both. This includes adding */*;q=0.1 to all requests.

Those using RDF content types:

 * CONSTRUCT, DESCRIBE, DELETE DATA, LOAD, CREATE

Those using SPARQL Results content types:

  * ASK, SELECT, INSERT DATA, CLEAR, DROP

Hopefully, this makes issues such as come up in #51 less likely to happen.

Only use DELETE DATA for #delete_statements if the statement is both constant, and contains no BNodes, otherwise, it falls back to DELETE/INSERT.

Check error response includes query in exception.
When doing updates, change BNodes to Variables.
Version 1.1.3.
Release 1.1.3.

Be more descriminating on Accept headers sent based on different queries. Queries build using the DSL use either RDF content types, or SPARQL Results content types, not both. This includes adding */*;q=0.1 to all requests.
Those using RDF content types:

 * CONSTRUCT, DESCRIBE, DELETE DATA, LOAD, CREATE

Those using SPARQL Results content types:

  * ASK, SELECT, INSERT DATA, CLEAR, DROP

Hopefully, this makes issues such as come up in #51 less likely to happen.

Only use DELETE DATA for #delete_statements if the statement is both constant, and contains no BNodes, otherwise, it falls back to DELETE/INSERT.

Check error response includes query in exception.
When doing updates, change BNodes to Variables.