[
https://issues.apache.org/jira/browse/JENA-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-657.
------------------------------
Resolution: Done
Assignee: Andy Seaborne
> Integrate result set parsing into RIOT properly
> -----------------------------------------------
>
> Key: JENA-657
> URL: https://issues.apache.org/jira/browse/JENA-657
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ, RIOT
> Affects Versions: Jena 2.11.1
> Reporter: Rob Vesse
> Assignee: Andy Seaborne
> Fix For: Jena 2.12.1
>
>
> Currently the result set parsing and writing APIs are somewhat messy and
> arbitrary. They don't follow a consistent interface or share any common
> implementation and there is very limited registry support.
> For example wherever we decide how to parse SPARQL results we typically end
> up writing complex {{if(contentType.equals(CONSTANT))}} type statements.
> It would be better if there was a consistent interface for results parser and
> a proper registry a la {{RDFLanguages}} so we can more easily work with
> results.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
