Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
openrdf-sesame-2.6.3-sdk.zip | 2012-01-24 | 23.8 MB | |
openrdf-sesame-2.6.3-sdk.tar.gz | 2012-01-24 | 18.4 MB | |
openrdf-sesame-2.6.3-onejar.jar | 2012-01-24 | 2.1 MB | |
README.txt | 2012-01-24 | 1.9 kB | |
Totals: 4 Items | 44.3 MB | 0 |
Sesame 2.6.3 ============ Sesame 2.6.3 introduces support for the SPARQL 1.1 Graph Store HTTP Protocol. See the updated Sesame System documentation ( http://www.openrdf.org/doc/sesame2/system/ ) for details. In addition, this release fixes several important issues discovered in previous releases. See the Changelog below for a summary. More details can be found in the Sesame issue tracker at http://www.openrdf.org/issues/ . Changelog ========= Release Notes - Sesame - Version 2.6.3 ** New Feature * [SES-895] - SPARQL 1.1 Graph Store HTTP Protocol support ** Bug * [SES-278] - Date Time parsing bug * [SES-821] - Incorrect nested query behaviour * [SES-896] - Terminating semicolon in sequence of update operations produces parse error * [SES-897] - BINDINGS Clause Causes Extra Result Projections * [SES-898] - Iterator provided by GraphImpl.match() no longer supports remove() * [SES-901] - Removing statements from a named graph without naming that graph prevents existing prepared statements from inserting on that graph. * [SES-903] - Export function doesn't work under JBoss AS 7.1 * [SES-904] - SPARQL 1.1 HAVING Clause Must Accept Any FILTER Constraint * [SES-907] - HTTP Accept header resolution does not pick most-specific match * [SES-908] - Service.parseServiceExpression corrupts the serviceExpression * [SES-917] - Predicates having the word "database" cause an exception evaulating a query ** Improvement * [SES-835] - error reporting in queries with BIND clauses * [SES-902] - Enable bindable variables in insert/delete data queries * [SES-906] - Optimize order of SPARQLIntersections * [SES-916] - Service Evaluation: Hand over the CloseableIteration directly to the FederatedService instance * [SES-919] - Workbench should use binary RDF as preferred communication format