[
https://issues.apache.org/jira/browse/JENA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133083#comment-14133083
]
Bruno P. Kinoshita commented on JENA-699:
-----------------------------------------
Hi Andy, thanks for the quick reply and brief history background on this issue.
> The parser API should not be seen as fixed; it did it's job at the time but
> it's not really a public contract. The new jena-csv is better off with a
> solid parser.
While reading the mailing list before submitting the patch I found this project
within Jena's SVN repo \[1\]. Since if uses the CSVParser, I think no changes
will be necessary there, but let me know if anything related to this issue
needs to be ported to that project.
This was my first issue while learning about Jena project structure and code
base, but now I'll probably bother you guys in the mailing list to work on the
issue to generate JSON from SPARQL (JENA 632) :)
Thanks!
\[1\] http://svn.apache.org/repos/asf/jena/Experimental/jena-csv/
> Replace the CSV/TSV parsing with Apache Commons CSV
> ---------------------------------------------------
>
> Key: JENA-699
> URL: https://issues.apache.org/jira/browse/JENA-699
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
> Attachments: JENA-699.patch
>
>
> When Apache Commons CSV is released, use that and remove the current parsers
> in favour of a properly written and designed component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
