[ 
https://issues.apache.org/jira/browse/JENA-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897085#comment-15897085
 ] 

ASF GitHub Bot commented on JENA-1306:
--------------------------------------

Github user afs commented on the issue:

    https://github.com/apache/jena/pull/222
  
    This PR is fully integrated into Jena though there is further internal 
cleaning up possible. 
    
    Some old features that have leaked out (like `ParserProfile` - it is 
supposed to be internal) could be changed/renamed/removed to be a better 
implementation and easier to maintain. As the next Jena release is an x.y.0, 
these changes should be made as soon as possible.



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

Reply via email to