[jira] [Updated] (JENA-1584) Include a Javacc based Turtle parser in RIOT

["Andy Seaborne (JIRA)" <ji...@apache.org>]

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

Andy Seaborne updated JENA-1584:
--------------------------------
    Description: 
Turtle is the basis for some additional languages (RDF*, SHACL and ShEX compact forms).

The main RIOT Turtle parser is written for speed, with the tuned tokenizer and directly written java grammar parser. This makes it harder to reuse and extend.

This ticket proposes including another RDF 1.1 compliant Turtle parser based on JavaCC to provide an easier route for additional languages by providing all the details of Turtle such as the tokens and prefix name handling, in a form more suitable as a base for the new language. It will still be by being a copy of the parser, system, not class inheritance.)

RDF 1.1 Turtle and SPARQL 1.1 were aligned by the working groups and share tokens and several grammar rules.

This would not be active by default (i.e. not a registered {{Lang}} and it's parser factory but registered by automatic initialization). It's test suite would be run in the build and pass the RDF 1.1 Turtle test suite.
 

There is non-RDF1.1 Javacc Turtle parser in jena-core is based on the pre-RDF1.1 state of Turtle. It is sufficient for the assembler tests that read turtle files. It could be moved into the test area except there appear to be some legacy applications that only use jena-core.

 

  was:
Turtle is the basis for some additional languages (RDF*, SHACL and ShEX compact forms).

The main RIOT Turtle parser is written for speed, with the tuned tokenizer and directly written java grammar parser. This makes it harder to reuse and extend.

This ticket proposes including another RDF 1.1 compliant Turtle parser based on JavaCC to provide an easier route for additional languages by providing all the details of Turtle such as the tokens and prefix name handling, in a form more suitable as a base for the new language. It will still be by being a copy of the parser, system, not class inheritance.)

RDF 1.1 Turtle and SPARQL 1.1 were aligned by the working groups and share tokens and several grammar rules.

 

There is non-RDF1.1 Javacc Turtle parser in jena-core is based on the pre-RDF1.1 state of Turtle. It is sufficient for the assembler tests that read turtle files. It could be moved into the test area except there appear to be some legacy applications that only use jena-core.

 


> Include a Javacc based Turtle parser in RIOT
> --------------------------------------------
>
>                 Key: JENA-1584
>                 URL: https://issues.apache.org/jira/browse/JENA-1584
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: RIOT
>    Affects Versions: Jena 3.8.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>             Fix For: Jena 3.9.0
>
>
> Turtle is the basis for some additional languages (RDF*, SHACL and ShEX compact forms).
> The main RIOT Turtle parser is written for speed, with the tuned tokenizer and directly written java grammar parser. This makes it harder to reuse and extend.
> This ticket proposes including another RDF 1.1 compliant Turtle parser based on JavaCC to provide an easier route for additional languages by providing all the details of Turtle such as the tokens and prefix name handling, in a form more suitable as a base for the new language. It will still be by being a copy of the parser, system, not class inheritance.)
> RDF 1.1 Turtle and SPARQL 1.1 were aligned by the working groups and share tokens and several grammar rules.
> This would not be active by default (i.e. not a registered {{Lang}} and it's parser factory but registered by automatic initialization). It's test suite would be run in the build and pass the RDF 1.1 Turtle test suite.
>  
> There is non-RDF1.1 Javacc Turtle parser in jena-core is based on the pre-RDF1.1 state of Turtle. It is sufficient for the assembler tests that read turtle files. It could be moved into the test area except there appear to be some legacy applications that only use jena-core.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)