[jira] [Resolved] (JENA-1584) Include a Javacc based Turtle parser in RIOT
[
https://issues.apache.org/jira/browse/JENA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1584.
-
Resolution: Fixed
> 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)
[jira] [Resolved] (JENA-1587) Generate TDB2 javadoc as the public API.
[ https://issues.apache.org/jira/browse/JENA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1587. - Resolution: Fixed > Generate TDB2 javadoc as the public API. > > > Key: JENA-1587 > URL: https://issues.apache.org/jira/browse/JENA-1587 > Project: Apache Jena > Issue Type: Improvement > Components: TDB2 >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > Produce the javadoc just for the package org.apache.jena.tdb2 (the API), and > not the subpackages (implementation). > c.f. TDB1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (JENA-1585) Reorganize the Fuseki codebase to split the server engine classes from the webapp classes
[ https://issues.apache.org/jira/browse/JENA-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1585. - Resolution: Done > Reorganize the Fuseki codebase to split the server engine classes from the > webapp classes > - > > Key: JENA-1585 > URL: https://issues.apache.org/jira/browse/JENA-1585 > Project: Apache Jena > Issue Type: Improvement > Components: Fuseki >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > This is a step towards separate packages for the fuseki server engine (the > servlets, request routing, some Jetty related support code) and the webapp > version of Fuseki that becomes the war and standalong jar in > jena-fuseki-server. > This first step is code reorganization with module jena-fuseki-core to put > the webapp java code it separate packages to the rest of the engine. > When split, the current jena-fuseki-core tests would go into > jena-fuseki-weabpp because they test the full server. The non-UI embeddable > server jena-fuseki-embedded and jena-fuseki-basic already gets test in the > integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1585) Reorganize the Fuseki codebase to split the server engine classes from the webapp classes
[ https://issues.apache.org/jira/browse/JENA-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571519#comment-16571519 ] ASF subversion and git services commented on JENA-1585: --- Commit 1d41d2ce4975ebc34e8a4dd4ff67cf1100421856 in jena's branch refs/heads/master from [~an...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=1d41d2c ] JENA-1585: Fuseki core reorg > Reorganize the Fuseki codebase to split the server engine classes from the > webapp classes > - > > Key: JENA-1585 > URL: https://issues.apache.org/jira/browse/JENA-1585 > Project: Apache Jena > Issue Type: Improvement > Components: Fuseki >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > This is a step towards separate packages for the fuseki server engine (the > servlets, request routing, some Jetty related support code) and the webapp > version of Fuseki that becomes the war and standalong jar in > jena-fuseki-server. > This first step is code reorganization with module jena-fuseki-core to put > the webapp java code it separate packages to the rest of the engine. > When split, the current jena-fuseki-core tests would go into > jena-fuseki-weabpp because they test the full server. The non-UI embeddable > server jena-fuseki-embedded and jena-fuseki-basic already gets test in the > integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1585) Reorganize the Fuseki codebase to split the server engine classes from the webapp classes
[ https://issues.apache.org/jira/browse/JENA-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571520#comment-16571520 ] ASF subversion and git services commented on JENA-1585: --- Commit 9dc0903475c92cd6155e8c0f5ddbf2a1ddaf5990 in jena's branch refs/heads/master from [~an...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=9dc0903 ] JENA-1585: Move resources, align web.xml, de-dup package-info.java > Reorganize the Fuseki codebase to split the server engine classes from the > webapp classes > - > > Key: JENA-1585 > URL: https://issues.apache.org/jira/browse/JENA-1585 > Project: Apache Jena > Issue Type: Improvement > Components: Fuseki >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > This is a step towards separate packages for the fuseki server engine (the > servlets, request routing, some Jetty related support code) and the webapp > version of Fuseki that becomes the war and standalong jar in > jena-fuseki-server. > This first step is code reorganization with module jena-fuseki-core to put > the webapp java code it separate packages to the rest of the engine. > When split, the current jena-fuseki-core tests would go into > jena-fuseki-weabpp because they test the full server. The non-UI embeddable > server jena-fuseki-embedded and jena-fuseki-basic already gets test in the > integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1585) Reorganize the Fuseki codebase to split the server engine classes from the webapp classes
[ https://issues.apache.org/jira/browse/JENA-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571531#comment-16571531 ] ASF GitHub Bot commented on JENA-1585: -- Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/456 > Reorganize the Fuseki codebase to split the server engine classes from the > webapp classes > - > > Key: JENA-1585 > URL: https://issues.apache.org/jira/browse/JENA-1585 > Project: Apache Jena > Issue Type: Improvement > Components: Fuseki >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > This is a step towards separate packages for the fuseki server engine (the > servlets, request routing, some Jetty related support code) and the webapp > version of Fuseki that becomes the war and standalong jar in > jena-fuseki-server. > This first step is code reorganization with module jena-fuseki-core to put > the webapp java code it separate packages to the rest of the engine. > When split, the current jena-fuseki-core tests would go into > jena-fuseki-weabpp because they test the full server. The non-UI embeddable > server jena-fuseki-embedded and jena-fuseki-basic already gets test in the > integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1587) Generate TDB2 javadoc as the public API.
[ https://issues.apache.org/jira/browse/JENA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571530#comment-16571530 ] ASF GitHub Bot commented on JENA-1587: -- Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/457 > Generate TDB2 javadoc as the public API. > > > Key: JENA-1587 > URL: https://issues.apache.org/jira/browse/JENA-1587 > Project: Apache Jena > Issue Type: Improvement > Components: TDB2 >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > Produce the javadoc just for the package org.apache.jena.tdb2 (the API), and > not the subpackages (implementation). > c.f. TDB1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1587) Generate TDB2 javadoc as the public API.
[ https://issues.apache.org/jira/browse/JENA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571525#comment-16571525 ] ASF subversion and git services commented on JENA-1587: --- Commit c82737b13131859fcb0426a6313d103a74b2f473 in jena's branch refs/heads/master from [~an...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=c82737b ] JENA-1587: TDB2 javadoc for the public API only > Generate TDB2 javadoc as the public API. > > > Key: JENA-1587 > URL: https://issues.apache.org/jira/browse/JENA-1587 > Project: Apache Jena > Issue Type: Improvement > Components: TDB2 >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > Produce the javadoc just for the package org.apache.jena.tdb2 (the API), and > not the subpackages (implementation). > c.f. TDB1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1584) Include a Javacc based Turtle parser in RIOT
[
https://issues.apache.org/jira/browse/JENA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571529#comment-16571529
]
ASF GitHub Bot commented on JENA-1584:
--
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/455
> 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)
[jira] [Commented] (JENA-1584) Include a Javacc based Turtle parser in RIOT
[
https://issues.apache.org/jira/browse/JENA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571528#comment-16571528
]
ASF subversion and git services commented on JENA-1584:
---
Commit 7b011c30b6bf54db44b5b14408f103009adbdd67 in jena's branch
refs/heads/master from [~an...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=7b011c3 ]
JENA-1584: Merge commit 'refs/pull/455/head' of https://github.com/apache/jena
This closes #455.
> 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)
[jira] [Commented] (JENA-1587) Generate TDB2 javadoc as the public API.
[ https://issues.apache.org/jira/browse/JENA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571526#comment-16571526 ] ASF subversion and git services commented on JENA-1587: --- Commit 02086d25c01d1ca34427c05bf5322a2273e7840e in jena's branch refs/heads/master from [~an...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=02086d2 ] JENA-1587: Merge commit 'refs/pull/457/head' of https://github.com/apache/jena This closes #457. > Generate TDB2 javadoc as the public API. > > > Key: JENA-1587 > URL: https://issues.apache.org/jira/browse/JENA-1587 > Project: Apache Jena > Issue Type: Improvement > Components: TDB2 >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > Produce the javadoc just for the package org.apache.jena.tdb2 (the API), and > not the subpackages (implementation). > c.f. TDB1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1584) Include a Javacc based Turtle parser in RIOT
[
https://issues.apache.org/jira/browse/JENA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571524#comment-16571524
]
ASF subversion and git services commented on JENA-1584:
---
Commit e2d8deed3bcf3ff11c22c2aba1f54bd88fa01929 in jena's branch
refs/heads/master from [~an...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=e2d8dee ]
JENA-1584: Add TurtleJavaccReaderRIOT.unregister
> 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)
[jira] [Commented] (JENA-1585) Reorganize the Fuseki codebase to split the server engine classes from the webapp classes
[ https://issues.apache.org/jira/browse/JENA-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571527#comment-16571527 ] ASF subversion and git services commented on JENA-1585: --- Commit 59b38995d2586c4248be05727c76b0f77b80a421 in jena's branch refs/heads/master from [~an...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=59b3899 ] JENA-1585: Merge commit 'refs/pull/456/head' of https://github.com/apache/jena This closes #456. > Reorganize the Fuseki codebase to split the server engine classes from the > webapp classes > - > > Key: JENA-1585 > URL: https://issues.apache.org/jira/browse/JENA-1585 > Project: Apache Jena > Issue Type: Improvement > Components: Fuseki >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > This is a step towards separate packages for the fuseki server engine (the > servlets, request routing, some Jetty related support code) and the webapp > version of Fuseki that becomes the war and standalong jar in > jena-fuseki-server. > This first step is code reorganization with module jena-fuseki-core to put > the webapp java code it separate packages to the rest of the engine. > When split, the current jena-fuseki-core tests would go into > jena-fuseki-weabpp because they test the full server. The non-UI embeddable > server jena-fuseki-embedded and jena-fuseki-basic already gets test in the > integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1584) Include a Javacc based Turtle parser in RIOT
[
https://issues.apache.org/jira/browse/JENA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571521#comment-16571521
]
ASF subversion and git services commented on JENA-1584:
---
Commit 31dc8138884d77dc8f8c881b54b21199278d4e40 in jena's branch
refs/heads/master from [~an...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=31dc813 ]
JENA-1584: A Javacc Turtle parser for reference.
> 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)
[jira] [Commented] (JENA-1585) Reorganize the Fuseki codebase to split the server engine classes from the webapp classes
[ https://issues.apache.org/jira/browse/JENA-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571523#comment-16571523 ] ASF subversion and git services commented on JENA-1585: --- Commit f926341f7de962602ee77596b7635a7c75a83386 in jena's branch refs/heads/master from [~an...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=f926341 ] JENA-1585: Comment for FusekiBuildLib; typo in FusekiServer > Reorganize the Fuseki codebase to split the server engine classes from the > webapp classes > - > > Key: JENA-1585 > URL: https://issues.apache.org/jira/browse/JENA-1585 > Project: Apache Jena > Issue Type: Improvement > Components: Fuseki >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.9.0 > > > This is a step towards separate packages for the fuseki server engine (the > servlets, request routing, some Jetty related support code) and the webapp > version of Fuseki that becomes the war and standalong jar in > jena-fuseki-server. > This first step is code reorganization with module jena-fuseki-core to put > the webapp java code it separate packages to the rest of the engine. > When split, the current jena-fuseki-core tests would go into > jena-fuseki-weabpp because they test the full server. The non-UI embeddable > server jena-fuseki-embedded and jena-fuseki-basic already gets test in the > integration tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] jena pull request #456: JENA-1585: Fuseki core reorg
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/456 ---
[GitHub] jena pull request #455: JENA-1584: A Javacc Turtle parser for reference.
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/455 ---
[GitHub] jena pull request #457: JENA-1587: TDB2 javadoc for the public API only
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/457 ---
