[JENA-657] Integrate result set parsing into RIOT properly

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: Jena 2.11.1
• Fix Version/s: Jena 2.12.1
• Component/s: ARQ, RIOT
• Assignee: Andy Seaborne
• Reporter: Rob Vesse
• Created: 18/Mar/14 13:08
• Updated: 10/Sep/14 10:45
• Resolved: 10/Sep/14 10:45

Description

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.

Issue Links

• relates to: JENA-656 Doesn't send all accepted mime types in header