[
https://issues.apache.org/jira/browse/JENA-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955678#comment-15955678
]
ASF subversion and git services commented on JENA-1306:
-------------------------------------------------------
Commit ecf579ae056abfd51117ea79883281d4545d52d6 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=ecf579a ]
JENA-1306: Canonical Literals. Less use of ParserProfile.
> Provide detailed setup for RIOT parsing with a parser builder.
> --------------------------------------------------------------
>
> Key: JENA-1306
> URL: https://issues.apache.org/jira/browse/JENA-1306
> Project: Apache Jena
> Issue Type: New Feature
> Components: RIOT
> Affects Versions: Jena 3.2.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Fix For: Jena 3.3.0
>
>
> Provide a parser builder for detailed setup of RDFParser.
> This is a new low level interface to the parsing process. It replaces and
> extends the machinery hidden inside {{RDFDataMgr}} ({{process}} and
> {{getReader}}) and {{RDFParserRegistry.ReaderRIOTLang}}.
> It aligns with the changes to {{HttpOp}} to have a specific optional
> {{HttpClient}} (JENA-576 and related work) and so allows applications to
> control the HTTP setup without resorting to direct use of {{HttpOp}}.
> More detailed control can be exposed, including language specific and
> specialized needs, for example [PR#211 "preserve id of blanknodes in
> JSON-LD"|https://github.com/apache/jena/pull/211].
> {{RDFDataMgr}} functions involving a Context can be can be deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
