You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2014/09/04 11:18:52 UTC

[jira] [Updated] (JENA-657) Integrate result set parsing into RIOT properly

     [ https://issues.apache.org/jira/browse/JENA-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne updated JENA-657:
-------------------------------
    Fix Version/s: Jena 2.12.1

> 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
>             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)