[jira] [Commented] (JENA-2021) Alt Turtle parser does not log some errors.

2021-01-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2021:
---

Commit b960181a211d58a5729fe6cacf07d156a0cb0c29 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=b960181 ]

JENA-2021: Remove unused import


> Alt Turtle parser does not log some errors.
> ---
>
> Key: JENA-2021
> URL: https://issues.apache.org/jira/browse/JENA-2021
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The JavaCC exception are caught and thrown but not logger to the error 
> handler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2021) Alt Turtle parser does not log some errors.

2021-01-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2021:
---

Commit 1b1904285b5097f1043e2068419cc0212f4438c8 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=1b19042 ]

JENA-2021: Log exception messages to error handler


> Alt Turtle parser does not log some errors.
> ---
>
> Key: JENA-2021
> URL: https://issues.apache.org/jira/browse/JENA-2021
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The JavaCC exception are caught and thrown but not logger to the error 
> handler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2021) Alt Turtle parser does not log some errors.

2021-01-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2021:
---

Commit 638f01f5849b42a54d80c643fc30309c3771b626 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=638f01f ]

Merge pull request #897 from afs/alt-turtle-error-msg

JENA-2021: Alt turtle (javacc) error msgs

> Alt Turtle parser does not log some errors.
> ---
>
> Key: JENA-2021
> URL: https://issues.apache.org/jira/browse/JENA-2021
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The JavaCC exception are caught and thrown but not logger to the error 
> handler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2017) Add SPARQL* Annotation syntax (experimental)

2021-01-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2017:
---

Commit f6fe5a8cc0d6558df535e54cc374d7986b484438 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=f6fe5a8 ]

JENA-2017: SPARQL* Syntax: Update test framework


> Add SPARQL* Annotation syntax (experimental)
> 
>
> Key: JENA-2017
> URL: https://issues.apache.org/jira/browse/JENA-2017
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Major
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2017) Add SPARQL* Annotation syntax (experimental)

2021-01-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2017:
---

Commit edde1cf9acee84d3f221fd6642bcace0dbdc1fb8 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=edde1cf ]

Merge pull request #894 from afs/jena2017-sparql-star

JENA-2017: Annotation syntax for SPARQL*

> Add SPARQL* Annotation syntax (experimental)
> 
>
> Key: JENA-2017
> URL: https://issues.apache.org/jira/browse/JENA-2017
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Major
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2001) Turtle/Trig: Write "rdf:type" if the RDF namespace has a prefix, else write "a".

2020-12-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2001:
---

Commit 79256b32342f64fe6e242a5f690897b8e8dfd055 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=79256b3 ]

Merge pull request #887 from afs/jena2001-write-type

JENA-2001: Print rdf:type if RDF prefix is available

> Turtle/Trig: Write "rdf:type" if the RDF namespace has a prefix, else write 
> "a".
> 
>
> Key: JENA-2001
> URL: https://issues.apache.org/jira/browse/JENA-2001
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, Turtle and Trig write "a" regardless of prefix settings.
> Write "rdf:type" if the RDF namespace has a prefix, else write "a" where the 
> full URI for rdf-type would be used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2001) Turtle/Trig: Write "rdf:type" if the RDF namespace has a prefix, else write "a".

2020-12-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2001:
---

Commit 74edeab4a6635d2e42de07ebf982ccf9f283cb6a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=74edeab ]

JENA-2001: Print rdf:type if RDF prefix is available


> Turtle/Trig: Write "rdf:type" if the RDF namespace has a prefix, else write 
> "a".
> 
>
> Key: JENA-2001
> URL: https://issues.apache.org/jira/browse/JENA-2001
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, Turtle and Trig write "a" regardless of prefix settings.
> Write "rdf:type" if the RDF namespace has a prefix, else write "a" where the 
> full URI for rdf-type would be used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2018) shacl parse: Getting RDFDataException - More than one match : (ANY rdf:type owl:Ontology)

2020-12-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2018:
---

Commit 5cc3c94017d5923089490822f045262fe604a90d in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=5cc3c94 ]

JENA-2018: Test import/base


> shacl parse: Getting RDFDataException - More than one match : (ANY rdf:type 
> owl:Ontology)
> -
>
> Key: JENA-2018
> URL: https://issues.apache.org/jira/browse/JENA-2018
> Project: Apache Jena
>  Issue Type: Bug
>  Components: SHACL
>Affects Versions: Jena 3.17.0
> Environment: Replicate by running
> {{shapesModel = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM)}}{{.read(stream);}}
>  {{Shapes.parse(shapesModel);}}
> Content of the file loaded:
> {{@prefix owl:  .}}
> {{@prefix ex:   .}}
> {{ex:foo a owl:Ontology ;}}
> {{    owl:imports ex:bar .}}
> Content of the referenced file:
> {{@prefix owl:  .}}
> {{@prefix ex:   .}}
> {{ex:bar a owl:Ontology .}}
>Reporter: Jan Rosecky
>Assignee: Andy Seaborne
>Priority: Major
>
> When running shacl parse on shapes model loaded as an ontology with several 
> owl:imports, I'm now getting
> {{RDFDataException - More than one match : (ANY rdf:type owl:Ontology)}}
> Of course, there is one triple {{ a owl:Ontology}} in each of the 
> imported files but always only one in a given file.
> This only started to happen in the new version of Jena (3.17.0), no such 
> issue experienced with 3.16.0



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2019) Rule$ParserException in Jena rules when string literal equals to open parenthesis

2020-12-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2019:
---

Commit e80048016846c19446e65211791e21dcc0eff6e8 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=e800480 ]

JENA-2019: Parse rule literals


> Rule$ParserException in Jena rules when string literal equals to open 
> parenthesis
> -
>
> Key: JENA-2019
> URL: https://issues.apache.org/jira/browse/JENA-2019
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 3.16.0, Jena 3.17.0
> Environment: _> java -version_
> openjdk version "1.8.0_232"
> OpenJDK Runtime Environment (build 1.8.0_232-BellSoft-b10)
> OpenJDK 64-Bit Server VM (build 25.232-b10, mixed mode)
> Windows 8.1
>Reporter: rdfman
>Assignee: Andy Seaborne
>Priority: Major
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> I have some [Jena 
> rules|https://jena.apache.org/documentation/inference/#RULEsyntax] and I 
> {color:#172b4d}need {color}to test a string literal in them:
> {code:java}
> @prefix my:  .
> # Rule including string "("
> [(?a my:text "(") -> ]  # fails for '(' is single quotes too
> {code}
> And a call to 
> {code:java}
> List rules = Rule.rulesFromURL(my_rules_path)
> {code}
> throws:
> {noformat}
> Exception in thread "main" 
> org.apache.jena.reasoner.rulesys.Rule$ParserException: Expected ')' at end of 
> clause, found ]
> At '[ ( ?a my:text " ( " ) -> ] '
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseNodeList(Rule.java:987)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseNode(Rule.java:906)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseNodeList(Rule.java:983)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseClause(Rule.java:998)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.doParseRule(Rule.java:1057)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseRule(Rule.java:1030)
> at org.apache.jena.reasoner.rulesys.Rule.parseRules(Rule.java:666)
> at org.apache.jena.reasoner.rulesys.Rule.rulesFromURL(Rule.java:515)
> at org.apache.jena.reasoner.rulesys.Rule.rulesFromURL(Rule.java:526)
> at ru.vstu.Main.runReasoning(Main.java:64){noformat}
> This crash happens if the string is exactly equal to *"("* (the use of double 
> quotes or single quotes does not matter). Escaping also with backslash *"\ 
> ("* does not help.
>  Changing the original string from *"("* to *"()"* , *"(("* , *"-("* or *")"* 
> eliminates the exception (but this is not what i want).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2019) Rule$ParserException in Jena rules when string literal equals to open parenthesis

2020-12-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2019:
---

Commit 58de541b1e7ee4d17e5fd8fdb4429ea907c123e8 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=58de541 ]

JENA-2019: Test rule parser


> Rule$ParserException in Jena rules when string literal equals to open 
> parenthesis
> -
>
> Key: JENA-2019
> URL: https://issues.apache.org/jira/browse/JENA-2019
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 3.16.0, Jena 3.17.0
> Environment: _> java -version_
> openjdk version "1.8.0_232"
> OpenJDK Runtime Environment (build 1.8.0_232-BellSoft-b10)
> OpenJDK 64-Bit Server VM (build 25.232-b10, mixed mode)
> Windows 8.1
>Reporter: rdfman
>Assignee: Andy Seaborne
>Priority: Major
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> I have some [Jena 
> rules|https://jena.apache.org/documentation/inference/#RULEsyntax] and I 
> {color:#172b4d}need {color}to test a string literal in them:
> {code:java}
> @prefix my:  .
> # Rule including string "("
> [(?a my:text "(") -> ]  # fails for '(' is single quotes too
> {code}
> And a call to 
> {code:java}
> List rules = Rule.rulesFromURL(my_rules_path)
> {code}
> throws:
> {noformat}
> Exception in thread "main" 
> org.apache.jena.reasoner.rulesys.Rule$ParserException: Expected ')' at end of 
> clause, found ]
> At '[ ( ?a my:text " ( " ) -> ] '
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseNodeList(Rule.java:987)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseNode(Rule.java:906)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseNodeList(Rule.java:983)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseClause(Rule.java:998)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.doParseRule(Rule.java:1057)
> at 
> org.apache.jena.reasoner.rulesys.Rule$Parser.parseRule(Rule.java:1030)
> at org.apache.jena.reasoner.rulesys.Rule.parseRules(Rule.java:666)
> at org.apache.jena.reasoner.rulesys.Rule.rulesFromURL(Rule.java:515)
> at org.apache.jena.reasoner.rulesys.Rule.rulesFromURL(Rule.java:526)
> at ru.vstu.Main.runReasoning(Main.java:64){noformat}
> This crash happens if the string is exactly equal to *"("* (the use of double 
> quotes or single quotes does not matter). Escaping also with backslash *"\ 
> ("* does not help.
>  Changing the original string from *"("* to *"()"* , *"(("* , *"-("* or *")"* 
> eliminates the exception (but this is not what i want).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2018) shacl parse: Getting RDFDataException - More than one match : (ANY rdf:type owl:Ontology)

2020-12-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2018:
---

Commit 38590999a6042454cc5a7e4e477b5308df594494 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=3859099 ]

JENA-2018: Extract a base URI if exactly one


> shacl parse: Getting RDFDataException - More than one match : (ANY rdf:type 
> owl:Ontology)
> -
>
> Key: JENA-2018
> URL: https://issues.apache.org/jira/browse/JENA-2018
> Project: Apache Jena
>  Issue Type: Bug
>  Components: SHACL
>Affects Versions: Jena 3.17.0
> Environment: Replicate by running
> {{shapesModel = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM)}}{{.read(stream);}}
>  {{Shapes.parse(shapesModel);}}
> Content of the file loaded:
> {{@prefix owl:  .}}
> {{@prefix ex:   .}}
> {{ex:foo a owl:Ontology ;}}
> {{    owl:imports ex:bar .}}
> Content of the referenced file:
> {{@prefix owl:  .}}
> {{@prefix ex:   .}}
> {{ex:bar a owl:Ontology .}}
>Reporter: Jan Rosecky
>Assignee: Andy Seaborne
>Priority: Major
>
> When running shacl parse on shapes model loaded as an ontology with several 
> owl:imports, I'm now getting
> {{RDFDataException - More than one match : (ANY rdf:type owl:Ontology)}}
> Of course, there is one triple {{ a owl:Ontology}} in each of the 
> imported files but always only one in a given file.
> This only started to happen in the new version of Jena (3.17.0), no such 
> issue experienced with 3.16.0



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2015) Add RDF* Annotation Syntax (experimental)

2020-12-16 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2015:
---

Commit 060093f64afbbf0067cacb6026e203b5da8b6ea7 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=060093f ]

Merge pull request #886 from afs/jena2015-rdf-star-syntax

JENA-2015: RDF* annotation syntax

> Add RDF* Annotation Syntax (experimental)
> -
>
> Key: JENA-2015
> URL: https://issues.apache.org/jira/browse/JENA-2015
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The RDF* group is discussing annotation syntax:
> [https://w3c.github.io/rdf-star/rdf-star-cg-spec.html#turtle-star-grammar]
> [https://github.com/w3c/rdf-star/issues/9]
> Example test:
>  
> [https://w3c.github.io/rdf-star/tests/turtle/syntax/manifest.html#turtle-star-ann-2]
> This is additional syntax - it does not invalidate any legal RDF.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2015) Add RDF* Annotation Syntax (experimental)

2020-12-16 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2015:
---

Commit ffe42022ac4527a32ad6822b84c96cd6ce1400a9 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=ffe4202 ]

JENA-2015: RDF* annotation syntax


> Add RDF* Annotation Syntax (experimental)
> -
>
> Key: JENA-2015
> URL: https://issues.apache.org/jira/browse/JENA-2015
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The RDF* group is discussing annotation syntax:
> [https://w3c.github.io/rdf-star/rdf-star-cg-spec.html#turtle-star-grammar]
> [https://github.com/w3c/rdf-star/issues/9]
> Example test:
>  
> [https://w3c.github.io/rdf-star/tests/turtle/syntax/manifest.html#turtle-star-ann-2]
> This is additional syntax - it does not invalidate any legal RDF.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2011) Fuseki does not work in IPv6 environment with Jetty

2020-12-12 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2011:
---

Commit 28dcacc041cc1c4733dadc184bcff1c6766ba000 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=28dcacc ]

Merge pull request #885 from afs/fixes-2011-2013-2014

Several tickets: JENA-2011 : JENA-2013 :  JENA-2014

> Fuseki does not work in IPv6 environment with Jetty
> ---
>
> Key: JENA-2011
> URL: https://issues.apache.org/jira/browse/JENA-2011
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Jena 3.17.0
> Environment: Tested on both Linux (with JDK 13) and Windows (with JDK 
> 15)
>Reporter: Alexander Radzin
>Priority: Major
>   Original Estimate: 1h
>  Time Spent: 40m
>  Remaining Estimate: 20m
>
> h1. Description
> Start fuseki server on IPv6 environment and navigate browser to 
> [http://localhost:3030|http://localhost:3030/].
> The UI does not show any datasets and all attempts to do anything with UI 
> fail. Press F12 (dev tools) in your browser and see that GET request to 
> `$/server` returns with error status 403 Forbidden.
> h1. Analysis
> The discovery shows the following problem. The status is set by 
> {{org.apache.jena.fuseki.authz.LocalhostFilter}}: {{isAccessAllowed()}} 
> returns `false`. 
>  This happens in turn because the {{remoteAddr}} should be one of 
> {{0:0:0:0:0:0:0:1}} or {{127.0.0.1}}.
> Now let's take a look on code in `org.eclipse.jetty.server.Request` 
> (implementation of `HttpServletRequest` used in Jetty): 
> {code:java}
> public String getRemoteAddr() {
>..
> // Add IPv6 brackets if necessary, to be consistent
> // with cases where _remote has been built from other
> // sources such as forward headers or PROXY protocol.
> return HostPort.normalizeHost(result);
> }
> {code}
> (I put here only the relevant part).
> Now let's review {{HostPort.normalizeHost}}:
> {code:java}
> public static String normalizeHost(String host)
> {
> // if it is normalized IPv6 or could not be IPv6, return
> if (host.isEmpty() || host.charAt(0) == '[' || host.indexOf(':') < 0)
> return host;
> // normalize with [ ]
> return "[" + host + "]";
> }
> {code}
> In case of IPv6 we this function wraps the address using squire brackets, 
> i.e. address {{0:0:0:0:0:0:0:1}} becomes {{[0:0:0:0:0:0:0:1]}}. However 
> jumping back to the {{LocalhostFilter.isAccessAllowed()}} the wrapped string 
> is compared to unwrapped one that causes {{isAccessAllowed}} to return false. 
> h1. Suggested fix
> Since wrapping of the address with squire brackets is the Jetty specific we 
> cannot just changes string {{"0:0:0:0:0:0:0:1"}} to {{"[0:0:0:0:0:0:0:1]"}} 
> in {{LocalhostFilter}} because such change might break this code in other 
> environments. However taking in cosideration comment  in 
> {{HostPort.normalizeHost}}:
> {code:java}
>  * Normalizes IPv6 address as per https://tools.ietf.org/html/rfc2732
>  * and https://tools.ietf.org/html/rfc6874,
>  * surrounding with square brackets if they are absent.
> {code}
> we can assume that such format is "standard" and just add wrapped version of 
> this IP to {{LocalhostFilter}}:
> {code:java}
> private static final Collection localhosts = new 
> HashSet<>(Arrays.asList(LOCALHOST_IpV4, LOCALHOST_IpV6, "[" +LOCALHOST_IpV4 + 
> "]"));
> protected boolean isAccessAllowed(ServletRequest request, ServletResponse 
> response, Object mappedValue) throws Exception {
> return  localhosts.contains(request.getRemoteAddr());
> }
> {code}
> h1. Workaround 
> Current workaround is to fix file {{shiro.ini}}: just uncomment line 
> {code}
> ##/$/** = anon
> {code}
> This grant permission to anonymous user to access to access all APIs (that 
> start with {{$}}). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2014) Comparison of xsd:duration does not account for fractional seconds.

2020-12-12 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2014:
---

Commit 04bae43e5f8a218639c5d0eb0e6b6740567a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=04bae43 ]

JENA-2014: Fix for comparing fractional seconds


> Comparison of xsd:duration does not account for fractional seconds.
> ---
>
> Key: JENA-2014
> URL: https://issues.apache.org/jira/browse/JENA-2014
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>
> The original imported code for duration processing does to work on durations 
> with fractional seconds.  If two durations are the same except for the 
> fractional seconds part, they are consider the same value.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2013) Comparison for DateTimeStamp not working

2020-12-12 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2013:
---

Commit 28dcacc041cc1c4733dadc184bcff1c6766ba000 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=28dcacc ]

Merge pull request #885 from afs/fixes-2011-2013-2014

Several tickets: JENA-2011 : JENA-2013 :  JENA-2014

> Comparison for DateTimeStamp not working
> 
>
> Key: JENA-2013
> URL: https://issues.apache.org/jira/browse/JENA-2013
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Jena 3.14.0
> Environment: This example dataset with both xsd:dateTime and 
> xsd:dateTimeStamp specified, loaded into Apache Jena Fuseki:
> {code:java}
> @prefix xsd:  .
> @prefix ex:  .
> ex:Foo ex:dateTime "2001-10-26T19:32:52+00:00"^^xsd:dateTime .
> ex:Foo ex:dateTimeStamp "2001-10-26T19:32:52+00:00"^^xsd:dateTimeStamp .
> {code}
>Reporter: Johannes Lipp
>Priority: Major
>
> *Summary:*
> The SPARQL query interface does handle greater/smaller than (< or >) for 
> xsd:dateTime properly, but does not handle xsd:dateTimeStamp correctly.
>  
> *Expected behavior:* 
> Executing the following query in Fuseki returns one result, because [the docs 
> say that xsd:dateTimeStamp is 
> supported|https://jena.apache.org/documentation/query/xsd-support.html]:
> {code:java}
> PREFIX xsd: SELECT ?subject ?predicate 
> ?object
> WHERE {
>   ?subject ?predicate ?object .
>   
>   FILTER (?object > "1999-10-26T19:32:52+00:00"^^xsd:dateTimeStamp) .
> }
> LIMIT 25
> {code}
> *Actual behavior:*
> The query returns no results. Querying via equals (= 2001...) instead of 
> greater (> 1999...) works. Also, replacing xsd:dateTimeStamp with 
> xsd:dateTime works as expected - but the xsd:dateTimeStamp does not return 
> anything.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2011) Fuseki does not work in IPv6 environment with Jetty

2020-12-12 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2011:
---

Commit a254043a14fe916edcfff7c15025f297d986a03f in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=a254043 ]

JENA-2011: Handle IPv6 localhost address for Jetty


> Fuseki does not work in IPv6 environment with Jetty
> ---
>
> Key: JENA-2011
> URL: https://issues.apache.org/jira/browse/JENA-2011
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Jena 3.17.0
> Environment: Tested on both Linux (with JDK 13) and Windows (with JDK 
> 15)
>Reporter: Alexander Radzin
>Priority: Major
>   Original Estimate: 1h
>  Time Spent: 40m
>  Remaining Estimate: 20m
>
> h1. Description
> Start fuseki server on IPv6 environment and navigate browser to 
> [http://localhost:3030|http://localhost:3030/].
> The UI does not show any datasets and all attempts to do anything with UI 
> fail. Press F12 (dev tools) in your browser and see that GET request to 
> `$/server` returns with error status 403 Forbidden.
> h1. Analysis
> The discovery shows the following problem. The status is set by 
> {{org.apache.jena.fuseki.authz.LocalhostFilter}}: {{isAccessAllowed()}} 
> returns `false`. 
>  This happens in turn because the {{remoteAddr}} should be one of 
> {{0:0:0:0:0:0:0:1}} or {{127.0.0.1}}.
> Now let's take a look on code in `org.eclipse.jetty.server.Request` 
> (implementation of `HttpServletRequest` used in Jetty): 
> {code:java}
> public String getRemoteAddr() {
>..
> // Add IPv6 brackets if necessary, to be consistent
> // with cases where _remote has been built from other
> // sources such as forward headers or PROXY protocol.
> return HostPort.normalizeHost(result);
> }
> {code}
> (I put here only the relevant part).
> Now let's review {{HostPort.normalizeHost}}:
> {code:java}
> public static String normalizeHost(String host)
> {
> // if it is normalized IPv6 or could not be IPv6, return
> if (host.isEmpty() || host.charAt(0) == '[' || host.indexOf(':') < 0)
> return host;
> // normalize with [ ]
> return "[" + host + "]";
> }
> {code}
> In case of IPv6 we this function wraps the address using squire brackets, 
> i.e. address {{0:0:0:0:0:0:0:1}} becomes {{[0:0:0:0:0:0:0:1]}}. However 
> jumping back to the {{LocalhostFilter.isAccessAllowed()}} the wrapped string 
> is compared to unwrapped one that causes {{isAccessAllowed}} to return false. 
> h1. Suggested fix
> Since wrapping of the address with squire brackets is the Jetty specific we 
> cannot just changes string {{"0:0:0:0:0:0:0:1"}} to {{"[0:0:0:0:0:0:0:1]"}} 
> in {{LocalhostFilter}} because such change might break this code in other 
> environments. However taking in cosideration comment  in 
> {{HostPort.normalizeHost}}:
> {code:java}
>  * Normalizes IPv6 address as per https://tools.ietf.org/html/rfc2732
>  * and https://tools.ietf.org/html/rfc6874,
>  * surrounding with square brackets if they are absent.
> {code}
> we can assume that such format is "standard" and just add wrapped version of 
> this IP to {{LocalhostFilter}}:
> {code:java}
> private static final Collection localhosts = new 
> HashSet<>(Arrays.asList(LOCALHOST_IpV4, LOCALHOST_IpV6, "[" +LOCALHOST_IpV4 + 
> "]"));
> protected boolean isAccessAllowed(ServletRequest request, ServletResponse 
> response, Object mappedValue) throws Exception {
> return  localhosts.contains(request.getRemoteAddr());
> }
> {code}
> h1. Workaround 
> Current workaround is to fix file {{shiro.ini}}: just uncomment line 
> {code}
> ##/$/** = anon
> {code}
> This grant permission to anonymous user to access to access all APIs (that 
> start with {{$}}). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2014) Comparison of xsd:duration does not account for fractional seconds.

2020-12-12 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2014:
---

Commit 28dcacc041cc1c4733dadc184bcff1c6766ba000 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=28dcacc ]

Merge pull request #885 from afs/fixes-2011-2013-2014

Several tickets: JENA-2011 : JENA-2013 :  JENA-2014

> Comparison of xsd:duration does not account for fractional seconds.
> ---
>
> Key: JENA-2014
> URL: https://issues.apache.org/jira/browse/JENA-2014
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>
> The original imported code for duration processing does to work on durations 
> with fractional seconds.  If two durations are the same except for the 
> fractional seconds part, they are consider the same value.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2013) Comparison for DateTimeStamp not working

2020-12-12 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2013:
---

Commit 1967e174200af7a355d6ccd3c01a46f9e26f894c in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=1967e17 ]

JENA-2013: Treat xsd:dateTimeStamp as a derived type of xsd:dateTime


> Comparison for DateTimeStamp not working
> 
>
> Key: JENA-2013
> URL: https://issues.apache.org/jira/browse/JENA-2013
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Jena 3.14.0
> Environment: This example dataset with both xsd:dateTime and 
> xsd:dateTimeStamp specified, loaded into Apache Jena Fuseki:
> {code:java}
> @prefix xsd:  .
> @prefix ex:  .
> ex:Foo ex:dateTime "2001-10-26T19:32:52+00:00"^^xsd:dateTime .
> ex:Foo ex:dateTimeStamp "2001-10-26T19:32:52+00:00"^^xsd:dateTimeStamp .
> {code}
>Reporter: Johannes Lipp
>Priority: Major
>
> *Summary:*
> The SPARQL query interface does handle greater/smaller than (< or >) for 
> xsd:dateTime properly, but does not handle xsd:dateTimeStamp correctly.
>  
> *Expected behavior:* 
> Executing the following query in Fuseki returns one result, because [the docs 
> say that xsd:dateTimeStamp is 
> supported|https://jena.apache.org/documentation/query/xsd-support.html]:
> {code:java}
> PREFIX xsd: SELECT ?subject ?predicate 
> ?object
> WHERE {
>   ?subject ?predicate ?object .
>   
>   FILTER (?object > "1999-10-26T19:32:52+00:00"^^xsd:dateTimeStamp) .
> }
> LIMIT 25
> {code}
> *Actual behavior:*
> The query returns no results. Querying via equals (= 2001...) instead of 
> greater (> 1999...) works. Also, replacing xsd:dateTimeStamp with 
> xsd:dateTime works as expected - but the xsd:dateTimeStamp does not return 
> anything.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2012) Check strings (including lexical forms) for legal high-then-low surrogate pairs.

2020-12-09 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2012:
---

Commit 9f4bb3cff63c261211d0de3c5c6ee44e0838b454 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=9f4bb3c ]

Merge pull request #884 from afs/jena2012-check-string

JENA-2012: Test for UTF-16 high-low surrogates pairs

> Check strings (including lexical forms) for legal high-then-low surrogate 
> pairs.
> 
>
> Key: JENA-2012
> URL: https://issues.apache.org/jira/browse/JENA-2012
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> This is from the rdf-tests discussions: 
> https://github.com/w3c/rdf-tests/pull/67 .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2012) Check strings (including lexical forms) for legal high-then-low surrogate pairs.

2020-12-09 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2012:
---

Commit a40b6c7e5679ea40ea10cd79aa8d613dacdd4504 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=a40b6c7 ]

JENA-2012: Test for UTF-16 high-low surrogates pairs


> Check strings (including lexical forms) for legal high-then-low surrogate 
> pairs.
> 
>
> Key: JENA-2012
> URL: https://issues.apache.org/jira/browse/JENA-2012
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> This is from the rdf-tests discussions: 
> https://github.com/w3c/rdf-tests/pull/67 .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2010) Compact function: Unwrap dataset to find TDB2 database

2020-12-09 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2010:
---

Commit 34b2d4886e09b84c399595dd31a4213e8f6b5016 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=34b2d48 ]

Merge pull request #883 from afs/unwrap-tdb2

JENA-2010: Unwrap to find a TDB2 dataset

> Compact function: Unwrap dataset to find TDB2 database
> --
>
> Key: JENA-2010
> URL: https://issues.apache.org/jira/browse/JENA-2010
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Follow-on from JENA-1987.
> A dataset like DetsetGraphText is a DatasetWrapper around a storage (TDB2) 
> dataset.
> This ticket adds unwrapping until the top of TDB2 is found 
> (DatasetGraphSwitchable).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2010) Compact function: Unwrap dataset to find TDB2 database

2020-12-09 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2010:
---

Commit 0d5a7379307e2e20707c9d56f0a39a6e4f2ee982 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=0d5a737 ]

JENA-2010: Unwrap to find a TDB2 dataset


> Compact function: Unwrap dataset to find TDB2 database
> --
>
> Key: JENA-2010
> URL: https://issues.apache.org/jira/browse/JENA-2010
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Follow-on from JENA-1987.
> A dataset like DetsetGraphText is a DatasetWrapper around a storage (TDB2) 
> dataset.
> This ticket adds unwrapping until the top of TDB2 is found 
> (DatasetGraphSwitchable).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2009) Add SHACL ConstraintVisitor

2020-12-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2009:
---

Commit 89e0070ad8f64aeff20c7464f2cea0207df91278 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=89e0070 ]

Merge pull request #882 from fkleedorfer/constraint-visitorpattern-JENA-2009

JENA-2009: Implement Visitor Pattern for SHACL Constraints

> Add SHACL ConstraintVisitor 
> 
>
> Key: JENA-2009
> URL: https://issues.apache.org/jira/browse/JENA-2009
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Jena
>Affects Versions: Jena 3.17.0
>Reporter: Florian Kleedorfer
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> As discussed in the [github comment thread on 
> JENA-2002|[https://github.com/apache/jena/pull/870#issuecomment-739490079]] 
> I'm suggesting to implemente the Visitor Pattern for SHACL Constraints.
> PR on github to follow.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2009) Add SHACL ConstraintVisitor

2020-12-08 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2009:
---

Commit 89e0070ad8f64aeff20c7464f2cea0207df91278 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=89e0070 ]

Merge pull request #882 from fkleedorfer/constraint-visitorpattern-JENA-2009

JENA-2009: Implement Visitor Pattern for SHACL Constraints

> Add SHACL ConstraintVisitor 
> 
>
> Key: JENA-2009
> URL: https://issues.apache.org/jira/browse/JENA-2009
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Jena
>Affects Versions: Jena 3.17.0
>Reporter: Florian Kleedorfer
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.18.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> As discussed in the [github comment thread on 
> JENA-2002|[https://github.com/apache/jena/pull/870#issuecomment-739490079]] 
> I'm suggesting to implemente the Visitor Pattern for SHACL Constraints.
> PR on github to follow.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2002) Access to private fields in SHACL Constraints

2020-12-06 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2002:
---

Commit 80e7db1ab7c966e3f8c9c3ba156a7a63b5d2c0db in jena's branch 
refs/heads/master from Florian Kleedorfer
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=80e7db1 ]

Add public getters to SHACL constraint implementations

As documented in https://issues.apache.org/jira/browse/JENA-2002, this commit 
adds public getters for accessing internal data in SHACL constraints.


> Access to private fields in SHACL Constraints
> -
>
> Key: JENA-2002
> URL: https://issues.apache.org/jira/browse/JENA-2002
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: SHACL
>Affects Versions: Jena 3.16.0
>Reporter: Florian Kleedorfer
>Priority: Trivial
> Fix For: Jena 3.18.0
>
>
> As explained in this [Jena-users mailinglist 
> thread|https://lists.apache.org/thread.html/rc759551efd7f5f619fd8847d34862dce6654089a13fd16e130d0a0d6%40%3Cusers.jena.apache.org%3E]
>  access is needed to the private properties of the SHACL constraint 
> implementations in package org.apache.jena.shacl.engine.constraint. Some are 
> already present as was needed for features already developed. 
> I need access to these properties for writing a SHACL-based java class 
> generator/instantiator  and will provide a PR with just the accessors.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2002) Access to private fields in SHACL Constraints

2020-12-06 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2002:
---

Commit 0c8bf0d07b94298555f713ceeaf082c748f4d945 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=0c8bf0d ]

Merge pull request #870 from fkleedorfer/feature-JENA-2002

Add public getters to SHACL constraint implementations

> Access to private fields in SHACL Constraints
> -
>
> Key: JENA-2002
> URL: https://issues.apache.org/jira/browse/JENA-2002
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: SHACL
>Affects Versions: Jena 3.16.0
>Reporter: Florian Kleedorfer
>Priority: Trivial
> Fix For: Jena 3.18.0
>
>
> As explained in this [Jena-users mailinglist 
> thread|https://lists.apache.org/thread.html/rc759551efd7f5f619fd8847d34862dce6654089a13fd16e130d0a0d6%40%3Cusers.jena.apache.org%3E]
>  access is needed to the private properties of the SHACL constraint 
> implementations in package org.apache.jena.shacl.engine.constraint. Some are 
> already present as was needed for features already developed. 
> I need access to these properties for writing a SHACL-based java class 
> generator/instantiator  and will provide a PR with just the accessors.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2006) Dataset prefixes

2020-12-04 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2006:
---

Commit 3ca8d0346049cae0bd764e66388b1991c7cd110b in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=3ca8d03 ]

Merge pull request #880 from afs/dataset-prefixes

JENA-2006: DatasetGraph prefixes

> Dataset prefixes
> 
>
> Key: JENA-2006
> URL: https://issues.apache.org/jira/browse/JENA-2006
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Summary:
> Add API calls:
> {{DatasetGraph.prefixes()}} -> {{PrefixMap}}
>  {{Dataset.getPrefixMapping()}} -> {{PrefixMapping}}
> Rework internal implementation code to reflect this.
> Clearup the different handling of prefixes; switch to a consistent provision 
> of a dataset prefix map. Remove {{DatasetPrefixStorage}} (multiple prefix 
> maps per dataset).
> My first attempt of this work was to use {{DatasetPrefixStorage}} 
> consistently but it ended up as a lot of classes mirroring PrefixMap 
> implementations. Because input formats only have prefixes by datasets, not 
> individual graph, the extra feature of multiple prefix maps can only be used 
> by API and it just doesn't seem worth the effort and extra code. It was 
> quicker doing the final form - "one prefix map per dataset" than the more 
> complicated form.
> More details:
> "TDB" means both TDB1 and TDB2.
> The main use case for prefixes is set as part of data parsing and use for 
> output to abbreviate URIs.
> For output, we know that URI->prefixed name is a performance critical 
> operation. It is optimized in {{PrefixMapStd}}. This does not change. The 
> writers copy prefixes into a {{PrefixMapStd}} which has a fast-path for the 
> common case of split at last "/" or "#" and a reverse map from URI to prefix.
> Mostly, up to now, implementation has been "store the prefixes in the default 
> graph" and while TDB stores multiple set of prefixes for each dataset so that 
> here is the possibility of graphs in the same dataset having different 
> prefixes, it used the default graph as well. Output has never made use of 
> multiple prefixes per dataset.
> The {{PrefixMapping}} API presumes a reverse mapping and the API contract is 
> part of the Model API (Model extends PrefixMapping). The other odd feature of 
> {{PrefixMapping}} is that there is no direct access to the prefixes as a map, 
> only a copy form.
> {{PrefixMap}} is simpler with the needs of parsers and storage implementation 
> in mind.
> The idea is that {{PrefixMapping}} is to be considered to be part of the 
> Dataset/Model/Statement/Resource APIs. There is a legacy quirk that Graph has 
> "getPrefixMapping".
> There will be adapters between the two viewpoints. Aside from the implicit 
> contract of {{PrefixMapping}} following XML qname rules, while Turtle is less 
> restrictive, the functionality can be mapped both ways.
> Mostly the XML-rules contract has been moved into the writers themselves in 
> previous iterations of implementation improvement. The adapters are 
> lightweight objects, with no state other than the object that adapt and 
> "double adapting" actually removes wrappers and returns the underlying 
> prefixes object.
> The improved way:
> Basic datasets (DatasetGraphMap and DatasetGraphMapLink) - dataset prefixes 
> are the default graph prefixes.
> TIM: All graphs in the dataset have the same prefix map. The PrefixMap is 
> thread-safe but isn't transactional (possible future work if needed).
> TDB1, TDB2: These have there own, more general prefix storage but the 
> additional feature is not exposed. All graphs in the dataset have the same 
> prefix map. There is no change to on-disk format.
> SDB: As before. There is no change to on-disk format.
> The nulls (DatasetGraphZero and DatasetGraphSink): Sink is "forget updates", 
> Zero is "empty, no updates": Suitably misbehaved implemented of the 
> {{PrefixMap}} API.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2006) Dataset prefixes

2020-12-04 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2006:
---

Commit 19b4ed3d8a6e39573a78d5a0c39aeb3b3f95fe7b in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=19b4ed3 ]

JENA-2006: DatasetGraph prefixes


> Dataset prefixes
> 
>
> Key: JENA-2006
> URL: https://issues.apache.org/jira/browse/JENA-2006
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Summary:
> Add API calls:
> {{DatasetGraph.prefixes()}} -> {{PrefixMap}}
>  {{Dataset.getPrefixMapping()}} -> {{PrefixMapping}}
> Rework internal implementation code to reflect this.
> Clearup the different handling of prefixes; switch to a consistent provision 
> of a dataset prefix map. Remove {{DatasetPrefixStorage}} (multiple prefix 
> maps per dataset).
> My first attempt of this work was to use {{DatasetPrefixStorage}} 
> consistently but it ended up as a lot of classes mirroring PrefixMap 
> implementations. Because input formats only have prefixes by datasets, not 
> individual graph, the extra feature of multiple prefix maps can only be used 
> by API and it just doesn't seem worth the effort and extra code. It was 
> quicker doing the final form - "one prefix map per dataset" than the more 
> complicated form.
> More details:
> "TDB" means both TDB1 and TDB2.
> The main use case for prefixes is set as part of data parsing and use for 
> output to abbreviate URIs.
> For output, we know that URI->prefixed name is a performance critical 
> operation. It is optimized in {{PrefixMapStd}}. This does not change. The 
> writers copy prefixes into a {{PrefixMapStd}} which has a fast-path for the 
> common case of split at last "/" or "#" and a reverse map from URI to prefix.
> Mostly, up to now, implementation has been "store the prefixes in the default 
> graph" and while TDB stores multiple set of prefixes for each dataset so that 
> here is the possibility of graphs in the same dataset having different 
> prefixes, it used the default graph as well. Output has never made use of 
> multiple prefixes per dataset.
> The {{PrefixMapping}} API presumes a reverse mapping and the API contract is 
> part of the Model API (Model extends PrefixMapping). The other odd feature of 
> {{PrefixMapping}} is that there is no direct access to the prefixes as a map, 
> only a copy form.
> {{PrefixMap}} is simpler with the needs of parsers and storage implementation 
> in mind.
> The idea is that {{PrefixMapping}} is to be considered to be part of the 
> Dataset/Model/Statement/Resource APIs. There is a legacy quirk that Graph has 
> "getPrefixMapping".
> There will be adapters between the two viewpoints. Aside from the implicit 
> contract of {{PrefixMapping}} following XML qname rules, while Turtle is less 
> restrictive, the functionality can be mapped both ways.
> Mostly the XML-rules contract has been moved into the writers themselves in 
> previous iterations of implementation improvement. The adapters are 
> lightweight objects, with no state other than the object that adapt and 
> "double adapting" actually removes wrappers and returns the underlying 
> prefixes object.
> The improved way:
> Basic datasets (DatasetGraphMap and DatasetGraphMapLink) - dataset prefixes 
> are the default graph prefixes.
> TIM: All graphs in the dataset have the same prefix map. The PrefixMap is 
> thread-safe but isn't transactional (possible future work if needed).
> TDB1, TDB2: These have there own, more general prefix storage but the 
> additional feature is not exposed. All graphs in the dataset have the same 
> prefix map. There is no change to on-disk format.
> SDB: As before. There is no change to on-disk format.
> The nulls (DatasetGraphZero and DatasetGraphSink): Sink is "forget updates", 
> Zero is "empty, no updates": Suitably misbehaved implemented of the 
> {{PrefixMap}} API.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2007) Improve timing of queries in cmd line tools

2020-12-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2007:
---

Commit 8e05866ecc8db9ba1680cc58287fc1a634a0dfd2 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=8e05866 ]

Merge pull request #881 from afs/jena2007-query-timing

JENA-2007: Better query timing

> Improve timing of queries in cmd line tools
> ---
>
> Key: JENA-2007
> URL: https://issues.apache.org/jira/browse/JENA-2007
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Cmd line tools
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Improvements:
>  
>  # Result set output NONE should consume the results, not merely print 
> nothing by doing nothing.
>  # Ensure the resutl format output is part of warm-up so the costs of class 
> loading is not incurred on the first timed run.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2007) Improve timing of queries in cmd line tools

2020-12-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2007:
---

Commit 5577ace43ba3fdbc78a4851c4670a4ba4b00babb in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=5577ace ]

JENA-2007: Include result format in warmup; write to null output stream


> Improve timing of queries in cmd line tools
> ---
>
> Key: JENA-2007
> URL: https://issues.apache.org/jira/browse/JENA-2007
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Cmd line tools
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Improvements:
>  
>  # Result set output NONE should consume the results, not merely print 
> nothing by doing nothing.
>  # Ensure the resutl format output is part of warm-up so the costs of class 
> loading is not incurred on the first timed run.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2007) Improve timing of queries in cmd line tools

2020-12-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2007:
---

Commit 21856bd94417ea451650f67c85140d2b8d3abe70 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=21856bd ]

JENA-2007: Consume the query results in null output format


> Improve timing of queries in cmd line tools
> ---
>
> Key: JENA-2007
> URL: https://issues.apache.org/jira/browse/JENA-2007
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Cmd line tools
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.18.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Improvements:
>  
>  # Result set output NONE should consume the results, not merely print 
> nothing by doing nothing.
>  # Ensure the resutl format output is part of warm-up so the costs of class 
> loading is not incurred on the first timed run.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2003) Common IO update breaks determining syntax from filenames.

2020-11-25 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2003:
---

Commit c8c91f8b2e1c4b54e004b55f2cf50f8feb8b4b90 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=c8c91f8 ]

JENA-2003: Handle file URIs with URI scheme name


> Common IO update breaks determining syntax from filenames.
> --
>
> Key: JENA-2003
> URL: https://issues.apache.org/jira/browse/JENA-2003
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Base, RIOT
>Affects Versions: Jena 3.16.0
> Environment: MS Windows
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Blocker
> Fix For: Jena 3.17.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Apache Commons IO 2.7.0 added a check for misplaced ':' in Windows filenames. 
> This breaks handling filenames, and other URIs, with a schema name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2003) Common IO update breaks determining syntax from filenames.

2020-11-25 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2003:
---

Commit a33b86878e9bba4b06ea14feb251d593aa0821d7 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=a33b868 ]

Merge pull request #871 from apache/windows-file

JENA-2003: Handle file URIs with URI scheme name

> Common IO update breaks determining syntax from filenames.
> --
>
> Key: JENA-2003
> URL: https://issues.apache.org/jira/browse/JENA-2003
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Base, RIOT
>Affects Versions: Jena 3.16.0
> Environment: MS Windows
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Blocker
> Fix For: Jena 3.17.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Apache Commons IO 2.7.0 added a check for misplaced ':' in Windows filenames. 
> This breaks handling filenames, and other URIs, with a schema name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2003) Common IO update breaks determining syntax from filenames.

2020-11-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2003:
---

Commit c8c91f8b2e1c4b54e004b55f2cf50f8feb8b4b90 in jena's branch 
refs/heads/windows-file from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=c8c91f8 ]

JENA-2003: Handle file URIs with URI scheme name


> Common IO update breaks determining syntax from filenames.
> --
>
> Key: JENA-2003
> URL: https://issues.apache.org/jira/browse/JENA-2003
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Base, RIOT
>Affects Versions: Jena 3.16.0
> Environment: MS Windows
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Blocker
> Fix For: Jena 3.17.0
>
>
> Apache Commons IO 2.7.0 added a check for misplaced ':' in Windows filenames. 
> This breaks handling filenames, and other URIs, with a schema name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-2003) Common IO update breaks determining syntax from filenames.

2020-11-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-2003:
---

Commit 13dffc12e7e0877ceb9c13f86f1e076608ddf887 in jena's branch 
refs/heads/windows-file from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=13dffc1 ]

JENA-2003: Handle file URIs with URI scheme name


> Common IO update breaks determining syntax from filenames.
> --
>
> Key: JENA-2003
> URL: https://issues.apache.org/jira/browse/JENA-2003
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Base, RIOT
>Affects Versions: Jena 3.16.0
> Environment: MS Windows
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Blocker
> Fix For: Jena 3.17.0
>
>
> Apache Commons IO 2.7.0 added a check for misplaced ':' in Windows filenames. 
> This breaks handling filenames, and other URIs, with a schema name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-23 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 29cd5c11917f3ae5bc1777d870f4263471f5f646 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=29cd5c1 ]

JENA-1987: Checking during request processing


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
> Attachments: log
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1997) Remove old Turtle/N3 writer (jena-core)

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1997:
---

Commit 6774bb339ae929c92ce5d6214c9c1523ff62ca3d in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=6774bb3 ]

Merge pull request #867 from afs/n3-writer

JENA-1997: Remove old Turtle/N3 writer

> Remove old Turtle/N3 writer (jena-core)
> ---
>
> Key: JENA-1997
> URL: https://issues.apache.org/jira/browse/JENA-1997
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> jena-core contains an old Turtle/N3 writer. (The N3 is for data only - not N3 
> nested graphs).
> Jena-core only needs Turtle/N3 because there are tests written using Turtle.
> The jena-core parser and writer are not up-to-date with the Turtle W3C 
> Recommendation and are replaced in normal use by the Turtle support in RIOT.
> While the reader is needed for test data, the writer is not used.
> It would only be used by applications depending on jena-core without the rest 
> of apache-jena-libs (specifically, jena-arq for RIOT). If RIOT is present, 
> then the writer will have been rewired to be the correct one.
> The overall result is that jena-core has RDF/XML, an N-Triples reader and a 
> basicTurtle parser. 
> jena-core is not intended for standalone use. We have has apache-jena-libs 
> fora long time now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1997) Remove old Turtle/N3 writer (jena-core)

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1997:
---

Commit d65ae5ee8e2cfddd8f007d43fac614568effdf7e in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=d65ae5e ]

JENA-1997: Remove old Turtle/N3 writer

Remaining Turtle parser supports jena-core tests.
Rename private TTL parser as org.apache.jena.ttl
Remove deprecated RDFFactoryF methods - includes changes to ModelCom.


> Remove old Turtle/N3 writer (jena-core)
> ---
>
> Key: JENA-1997
> URL: https://issues.apache.org/jira/browse/JENA-1997
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> jena-core contains an old Turtle/N3 writer. (The N3 is for data only - not N3 
> nested graphs).
> Jena-core only needs Turtle/N3 because there are tests written using Turtle.
> The jena-core parser and writer are not up-to-date with the Turtle W3C 
> Recommendation and are replaced in normal use by the Turtle support in RIOT.
> While the reader is needed for test data, the writer is not used.
> It would only be used by applications depending on jena-core without the rest 
> of apache-jena-libs (specifically, jena-arq for RIOT). If RIOT is present, 
> then the writer will have been rewired to be the correct one.
> The overall result is that jena-core has RDF/XML, an N-Triples reader and a 
> basicTurtle parser. 
> jena-core is not intended for standalone use. We have has apache-jena-libs 
> fora long time now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1998) Provide SHACL imports processing.

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1998:
---

Commit 0c93f37e34ba0934e405ebaea709f2a79fbf34eb in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=0c93f37 ]

Merge pull request #866 from afs/shacl-imports

JENA-1998: Imports closure machinery

> Provide SHACL imports processing.
> -
>
> Key: JENA-1998
> URL: https://issues.apache.org/jira/browse/JENA-1998
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: SHACL
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> SHACL has an import mechanism using {{owl:imports}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1998) Provide SHACL imports processing.

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1998:
---

Commit 7eb3ba91784ad0a6ad625d7dba52f857c293a6f0 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=7eb3ba9 ]

JENA-1998: Imports closure machinery


> Provide SHACL imports processing.
> -
>
> Key: JENA-1998
> URL: https://issues.apache.org/jira/browse/JENA-1998
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: SHACL
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> SHACL has an import mechanism using {{owl:imports}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 1fe930c39dbb08ab8d17aea4f0c70500c5f5520f in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=1fe930c ]

Rename method for clarity (JENA-1987)


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 09019c08249e4dda0eb6ec26f234b86b0dacbdbf in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=09019c0 ]

Unit tests for /$/compact/ (JENA-1987)


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 3e5e7129a8fc17f9b66b290eae863080d97b5b77 in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=3e5e712 ]

Remove unnecessary extra dependency (JENA-1987)


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 15be63482c7644d154b75fa505f9f648c565c1ac in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=15be634 ]

Add Fuseki /$/compact/* endpoint (JENA-1987)

Some of the implementation for adding a /$/compact/* endpoint to a
Fuseki server that allows live database compaction via the REST API


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit b5dff72279a630e380e011f7288d7c1897bd9819 in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=b5dff72 ]

Merge pull request #822 from rvesse/JENA-1987

Add Fuseki /$/compact/* endpoint (JENA-1987)

> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit b5dff72279a630e380e011f7288d7c1897bd9819 in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=b5dff72 ]

Merge pull request #822 from rvesse/JENA-1987

Add Fuseki /$/compact/* endpoint (JENA-1987)

> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 2decb5d97d8dd88827ba55987199f97ffc5cc348 in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2decb5d ]

Ensure ActionSleep throws errors upwards (JENA-1987)


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 2ecccbd3d8699e509d1ca3afb2ad1d31e7f1e20f in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2ecccbd ]

Indicate task success/failure correctly (JENA-1987)


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 207dcce55a2d0d2fa2736e91133c719d52083f93 in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=207dcce ]

Rollback irrelevant changes (JENA-1987)


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit 697772891e17b3d080d69eec5e82ae6857476cd6 in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=6977728 ]

Rollback more irrelevant changes (JENA-1987)


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1987) HTTP API for TDB compact AND/OR periodical compact

2020-11-18 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1987:
---

Commit c7ab131ab01881dc26435f7c047ec1299415e869 in jena's branch 
refs/heads/master from Rob Vesse
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=c7ab131 ]

Simplify code (JENA-1987)


> HTTP API for TDB compact AND/OR periodical compact
> --
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Reporter: Martin Kopeček
>Assignee: Rob Vesse
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1994) PrefixMappingUtils.calcInUsePrefixMapping() does not reflect prefixes used in typed literals

2020-11-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1994:
---

Commit b85e31d0526584d6f64662670dce8379c40a28d8 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=b85e31d ]

JENA-1994: Look in datatype URI (#864)

JENA-1994: Look in datatype URI

> PrefixMappingUtils.calcInUsePrefixMapping() does not reflect prefixes used in 
> typed literals
> 
>
> Key: JENA-1994
> URL: https://issues.apache.org/jira/browse/JENA-1994
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Reporter: Jan Rosecky
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Prefixes used in typed literals are not reflected in computed prefix mapping 
> used in given the graph, as calculated by 
> PrefixMappingUtils.calcInUsePrefixMapping().
>  
> Not really sure if this is a bug or a feature request.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1994) PrefixMappingUtils.calcInUsePrefixMapping() does not reflect prefixes used in typed literals

2020-11-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1994:
---

Commit b85e31d0526584d6f64662670dce8379c40a28d8 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=b85e31d ]

JENA-1994: Look in datatype URI (#864)

JENA-1994: Look in datatype URI

> PrefixMappingUtils.calcInUsePrefixMapping() does not reflect prefixes used in 
> typed literals
> 
>
> Key: JENA-1994
> URL: https://issues.apache.org/jira/browse/JENA-1994
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Reporter: Jan Rosecky
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Prefixes used in typed literals are not reflected in computed prefix mapping 
> used in given the graph, as calculated by 
> PrefixMappingUtils.calcInUsePrefixMapping().
>  
> Not really sure if this is a bug or a feature request.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1990) Add short name 'turtle' of ?format= legal values.

2020-11-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1990:
---

Commit 7f42c3af8b89ad9bd251fc9c665a957ec22a586a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=7f42c3a ]

JENA-1990: Add short name "turtle" (for SPARQLWrapper.py)

> Add short name 'turtle' of ?format= legal values.
> -
>
> Key: JENA-1990
> URL: https://issues.apache.org/jira/browse/JENA-1990
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {{format=turtle}} is used by SPARQLWrapper.py.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1993) Update Eclipse Jetty to 9.4.34

2020-11-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1993:
---

Commit 94acc4f646dd6837d85f7fd5bf05b493e0448873 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=94acc4f ]

JENA-1993: Update Eclipse Jetty


> Update Eclipse Jetty to 9.4.34
> --
>
> Key: JENA-1993
> URL: https://issues.apache.org/jira/browse/JENA-1993
> Project: Apache Jena
>  Issue Type: Task
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1992) Update log4j2 to 2.14.0

2020-11-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1992:
---

Commit 96c6b26cfa925504383015cbfabfadfc62cb42d1 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=96c6b26 ]

JENA-1992: Update Log4j2 to 2.14.0


> Update log4j2 to 2.14.0
> ---
>
> Key: JENA-1992
> URL: https://issues.apache.org/jira/browse/JENA-1992
> Project: Apache Jena
>  Issue Type: Task
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1991) Move operations from RiotLib to G; add some quad "find" operations

2020-11-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1991:
---

Commit 90010766f69ade2f0ebf613b4b6a8145303adf76 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=9001076 ]

Merge pull request #824 from afs/small-items

JENA-1990, JENA-1991, JENA-1992, JENA-1993: Upgrade and small items

> Move operations from RiotLib to G; add some quad "find" operations
> --
>
> Key: JENA-1991
> URL: https://issues.apache.org/jira/browse/JENA-1991
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.16.0
>
>
> RiotLib has a couple of helper functions that make more sense in G.
> Put in quad versions of "find" operations.
> Rename exisiting find forms to say they are for triples.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1993) Update Eclipse Jetty to 9.4.34

2020-11-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1993:
---

Commit 90010766f69ade2f0ebf613b4b6a8145303adf76 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=9001076 ]

Merge pull request #824 from afs/small-items

JENA-1990, JENA-1991, JENA-1992, JENA-1993: Upgrade and small items

> Update Eclipse Jetty to 9.4.34
> --
>
> Key: JENA-1993
> URL: https://issues.apache.org/jira/browse/JENA-1993
> Project: Apache Jena
>  Issue Type: Task
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1991) Move operations from RiotLib to G; add some quad "find" operations

2020-11-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1991:
---

Commit 67f84720847f329ca09b923172286025c6eb66ce in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=67f8472 ]

JENA-1991: Operations for G

> Move operations from RiotLib to G; add some quad "find" operations
> --
>
> Key: JENA-1991
> URL: https://issues.apache.org/jira/browse/JENA-1991
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.16.0
>
>
> RiotLib has a couple of helper functions that make more sense in G.
> Put in quad versions of "find" operations.
> Rename exisiting find forms to say they are for triples.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1992) Update log4j2 to 2.14.0

2020-11-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1992:
---

Commit 90010766f69ade2f0ebf613b4b6a8145303adf76 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=9001076 ]

Merge pull request #824 from afs/small-items

JENA-1990, JENA-1991, JENA-1992, JENA-1993: Upgrade and small items

> Update log4j2 to 2.14.0
> ---
>
> Key: JENA-1992
> URL: https://issues.apache.org/jira/browse/JENA-1992
> Project: Apache Jena
>  Issue Type: Task
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1990) Add short name 'turtle' of ?format= legal values.

2020-11-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1990:
---

Commit 90010766f69ade2f0ebf613b4b6a8145303adf76 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=9001076 ]

Merge pull request #824 from afs/small-items

JENA-1990, JENA-1991, JENA-1992, JENA-1993: Upgrade and small items

> Add short name 'turtle' of ?format= legal values.
> -
>
> Key: JENA-1990
> URL: https://issues.apache.org/jira/browse/JENA-1990
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {{format=turtle}} is used by SPARQLWrapper.py.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1989) No log output with Fuseki+Tomcat9+Systemd

2020-11-10 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1989:
---

Commit 5223ffec980e5009f5c48bdac9c52d2477b37697 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=5223ffe ]

JENA-1989: Remove debug code; correct initalization test


> No log output with Fuseki+Tomcat9+Systemd 
> --
>
> Key: JENA-1989
> URL: https://issues.apache.org/jira/browse/JENA-1989
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>
> Running Fuseki and Tomcat9 with systemd shows a number of problems:
>  # /etc/fuseki/ is not accessible - Tomcat9 with systemd is sandboxed and 
> /etc/fuseki is not writable. (Fix: document that systemd needs configuring).
>  # Log output handled differently. systemd captures stdout and sends it to 
> the system journal. There is no catalina.out. (Fix: document how to setup 
> systemd)
>  # log4j2 setup happens as the webapp starts and before Fuseki initialization 
> is called. Result - the Fuseki configuration is not used. Fix: Use the 
> log4j-web artifact and configure web.xml.
> The servlet/log setup probably applies to Fuseki logging for log4j2 in 
> Tomcat8 as well but I can't install the stabndard setupo of tomcat8 and 
> systemd because it is no longer available in the Ubuntu repos (Ubuntu 20.10).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1898) Force commons-codec dependency to be Jena parent POM choice

2020-11-10 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1898:
---

Commit da2e8ddc3c833a94687d2b2ec2cbe1909151f36f in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=da2e8dd ]

JENA-1898: Log output for webapp


> Force commons-codec dependency to be Jena parent POM choice
> ---
>
> Key: JENA-1898
> URL: https://issues.apache.org/jira/browse/JENA-1898
> Project: Apache Jena
>  Issue Type: Task
>Affects Versions: Jena 3.15.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.16.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> I have a project where the dependency resolution causes the commons-codec 
> from Apache httpcomponents to be chosen (v1.11), not the version needed by 
> Jena (v1.14).
> Maven dependency rules: 
> [https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]
> The project depends on several Jena artifacts and the encounter order of 
> dependencies can matter.
> This happens with maven 3.6.3, which is current latest.
> Clearing up the projects dependencies will also fix the problem but leaves it 
> to the user to deal with it. (The project is an old and messy scratch working 
> area and the POM isn't neat and tidy. It was bringing in Jena test code.)
> To be safe, this ticket is to force the dependency resolution by excluding 
> common-codec from the org.apache.httpcomponents (httpclient and httpclient).
> Then at least the order of any Jena artifacts does not impact the outcome.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1898) Force commons-codec dependency to be Jena parent POM choice

2020-11-10 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1898:
---

Commit fd94c6b2a56df4e3e012c1acb617ecda9346ca42 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=fd94c6b ]

Merge pull request #823 from afs/jena1989-fuseki

JENA-1898: Log output for webapp

> Force commons-codec dependency to be Jena parent POM choice
> ---
>
> Key: JENA-1898
> URL: https://issues.apache.org/jira/browse/JENA-1898
> Project: Apache Jena
>  Issue Type: Task
>Affects Versions: Jena 3.15.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.16.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> I have a project where the dependency resolution causes the commons-codec 
> from Apache httpcomponents to be chosen (v1.11), not the version needed by 
> Jena (v1.14).
> Maven dependency rules: 
> [https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]
> The project depends on several Jena artifacts and the encounter order of 
> dependencies can matter.
> This happens with maven 3.6.3, which is current latest.
> Clearing up the projects dependencies will also fix the problem but leaves it 
> to the user to deal with it. (The project is an old and messy scratch working 
> area and the POM isn't neat and tidy. It was bringing in Jena test code.)
> To be safe, this ticket is to force the dependency resolution by excluding 
> common-codec from the org.apache.httpcomponents (httpclient and httpclient).
> Then at least the order of any Jena artifacts does not impact the outcome.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1949) Docker build tools for Fuseki

2020-11-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1949:
---

Commit 2c1617cef565bf5af2475c2e25849484a97d6423 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2c1617c ]

JENA-1949: Add https crypto modules from the JDK


> Docker build tools for Fuseki
> -
>
> Key: JENA-1949
> URL: https://issues.apache.org/jira/browse/JENA-1949
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
> Attachments: image-2020-10-29-20-32-25-174.png, 
> image-2020-10-29-20-33-20-634.png, image-2020-10-29-20-36-15-499.png
>
>  Time Spent: 6h 10m
>  Remaining Estimate: 0h
>
> JENA-909 is for a docker container available in docker hub.
> Integrating complete deployment within the project release process is 
> difficult because we do not want docker container binary artifact going to 
> Docker Hub until (1) they are not snapshots and (2) the vote has concluded 
> successfully.
> At the same time, being stateful, a deployment needs to consider where 
> databases and logs go outside the container.
> This ticket is for the setup and scripts to build an image, not to publish it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1949) Docker build tools for Fuseki

2020-11-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1949:
---

Commit 7ee5d343ee3326e064960217ac8ae4a403f3ecc4 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=7ee5d34 ]

Merge pull request #821 from afs/jena1949-crypto

JENA-1949: Add https crypto modules from the JDK

> Docker build tools for Fuseki
> -
>
> Key: JENA-1949
> URL: https://issues.apache.org/jira/browse/JENA-1949
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
> Attachments: image-2020-10-29-20-32-25-174.png, 
> image-2020-10-29-20-33-20-634.png, image-2020-10-29-20-36-15-499.png
>
>  Time Spent: 6h 10m
>  Remaining Estimate: 0h
>
> JENA-909 is for a docker container available in docker hub.
> Integrating complete deployment within the project release process is 
> difficult because we do not want docker container binary artifact going to 
> Docker Hub until (1) they are not snapshots and (2) the vote has concluded 
> successfully.
> At the same time, being stateful, a deployment needs to consider where 
> databases and logs go outside the container.
> This ticket is for the setup and scripts to build an image, not to publish it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1982) SPARQL parser does not handle \U escapes in strings.

2020-10-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1982:
---

Commit 72cdb2bdb41eff60513777c743a6609a779f1245 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=72cdb2b ]

Merge pull request #820 from afs/jena1982-sparql-unicode

JENA-1982: SPARQL unicode escapes

> SPARQL parser does not handle \U escapes in strings.
> 
>
> Key: JENA-1982
> URL: https://issues.apache.org/jira/browse/JENA-1982
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1982) SPARQL parser does not handle \U escapes in strings.

2020-10-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1982:
---

Commit b8922e393d58556dfcc801098e7066a00c23d480 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=b8922e3 ]

JENA-1982: Unicode escapes for SPARQL


> SPARQL parser does not handle \U escapes in strings.
> 
>
> Key: JENA-1982
> URL: https://issues.apache.org/jira/browse/JENA-1982
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1982) SPARQL parser does not handle \U escapes in strings.

2020-10-29 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1982:
---

Commit 3ba9a927e3cf0b37f5bd6d21d1cdfb29a62438a5 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=3ba9a92 ]

JENA-1982: Unicode escapes for SSE


> SPARQL parser does not handle \U escapes in strings.
> 
>
> Key: JENA-1982
> URL: https://issues.apache.org/jira/browse/JENA-1982
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1984) XSD casting fixes

2020-10-23 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1984:
---

Commit d5d1c8934ae323ef531a7b1c1971b5834d5530ad in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=d5d1c89 ]

Merge pull request #819 from afs/jena1984-xsd-casting

JENA-1984: Fixed to XSD casting

> XSD casting fixes
> -
>
> Key: JENA-1984
> URL: https://issues.apache.org/jira/browse/JENA-1984
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> [https://www.w3.org/TR/xpath-functions/#casting|https://www.w3.org/TR/xpath-functions/#casting]
> 1/ xsd:boolean cast includes casting from decimal and floating point which 
> ARQ is not doing correctly.
> 2/ decimals and floating point not truncating to integer properly.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1986) Nested aggregates in SPARQL expressions not always being rejected

2020-10-23 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1986:
---

Commit 2cfd63e8100754b769af5980f65be31e643ea273 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2cfd63e ]

JENA-1986: Negative syntax tests for nested aggregates


> Nested aggregates in SPARQL expressions not always being rejected
> -
>
> Key: JENA-1986
> URL: https://issues.apache.org/jira/browse/JENA-1986
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.16.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1984) XSD casting fixes

2020-10-23 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1984:
---

Commit 34759aa6d286e4fc88b570b26c8fb898ae59a354 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=34759aa ]

JENA-1984: Additional tidying up


> XSD casting fixes
> -
>
> Key: JENA-1984
> URL: https://issues.apache.org/jira/browse/JENA-1984
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> [https://www.w3.org/TR/xpath-functions/#casting|https://www.w3.org/TR/xpath-functions/#casting]
> 1/ xsd:boolean cast includes casting from decimal and floating point which 
> ARQ is not doing correctly.
> 2/ decimals and floating point not truncating to integer properly.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1986) Nested aggregates in SPARQL expressions not always being rejected

2020-10-23 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1986:
---

Commit cc65126203ed0a97a4a60924a483de9348650c5c in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=cc65126 ]

JENA-1986: Error for nested aggregates


> Nested aggregates in SPARQL expressions not always being rejected
> -
>
> Key: JENA-1986
> URL: https://issues.apache.org/jira/browse/JENA-1986
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ
>Affects Versions: Jena 3.17.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.16.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1984) XSD casting fixes

2020-10-23 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1984:
---

Commit d1d65c4d01b65e9984d8f8b9ac8b56642dceba8e in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=d1d65c4 ]

JENA-1984: Improve XSD casting


> XSD casting fixes
> -
>
> Key: JENA-1984
> URL: https://issues.apache.org/jira/browse/JENA-1984
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> [https://www.w3.org/TR/xpath-functions/#casting|https://www.w3.org/TR/xpath-functions/#casting]
> 1/ xsd:boolean cast includes casting from decimal and floating point which 
> ARQ is not doing correctly.
> 2/ decimals and floating point not truncating to integer properly.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1985) Adding TriG and N-Quads content-type in Fuseki2

2020-10-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1985:
---

Commit 3f2d133bc12ea4d4c775df1bf77367f047d5603f in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=3f2d133 ]

Merge pull request #817 from marcelomachado/patch-1

[JENA-1985] Adding TriG and N-Quads content-type in Fuseki2.

> Adding TriG and N-Quads content-type in Fuseki2
> ---
>
> Key: JENA-1985
> URL: https://issues.apache.org/jira/browse/JENA-1985
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: MARCELO DE OLIVEIRA COSTA MACHADO
>Priority: Trivial
> Fix For: Jena 3.17.0
>
>   Original Estimate: 2m
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1985) Adding TriG and N-Quads content-type in Fuseki2

2020-10-22 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1985:
---

Commit 3f2d133bc12ea4d4c775df1bf77367f047d5603f in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=3f2d133 ]

Merge pull request #817 from marcelomachado/patch-1

[JENA-1985] Adding TriG and N-Quads content-type in Fuseki2.

> Adding TriG and N-Quads content-type in Fuseki2
> ---
>
> Key: JENA-1985
> URL: https://issues.apache.org/jira/browse/JENA-1985
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: MARCELO DE OLIVEIRA COSTA MACHADO
>Priority: Trivial
> Fix For: Jena 3.17.0
>
>   Original Estimate: 2m
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1981) SUBSTR fails on strings with codepoints beyond U+10000

2020-10-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1981:
---

Commit a771c8d81174bc1b84f13a985e6ec60f7ab1815f in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=a771c8d ]

JENA-1981: Unicode and SUBSTR


> SUBSTR fails on strings with codepoints beyond U+1
> --
>
> Key: JENA-1981
> URL: https://issues.apache.org/jira/browse/JENA-1981
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> This is from [https://github.com/w3c/rdf-tests/pull/65]
> {noformat}
> # As a UTF-16 pair, but one codepoint.
> substr('\\uD83D\\uDC6A', 2)
> {noformat}
> {noformat}
> substr('👪', 2)
> {noformat}
> The character is U+0001F46A 👪 - FAMILY.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1982) SPARQL parser does not handle \U escapes in strings.

2020-10-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1982:
---

Commit 36e9d9847d2b42daaddcc2274c5781e4dae1c2d1 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=36e9d98 ]

JENA-1982: 8 byte escapes (shaclc.jj)


> SPARQL parser does not handle \U escapes in strings.
> 
>
> Key: JENA-1982
> URL: https://issues.apache.org/jira/browse/JENA-1982
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1982) SPARQL parser does not handle \U escapes in strings.

2020-10-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1982:
---

Commit 79a205935eb21f64d30bba3479d2ef75bfb249ad in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=79a2059 ]

JENA-1982: 8 bytes escapes (turtle.jj)


> SPARQL parser does not handle \U escapes in strings.
> 
>
> Key: JENA-1982
> URL: https://issues.apache.org/jira/browse/JENA-1982
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1981) SUBSTR fails on strings with codepoints beyond U+10000

2020-10-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1981:
---

Commit 1b5bc3bceced525368c02b3524bd6c9c94d01795 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=1b5bc3b ]

Merge pull request #815 from afs/jena1981_unicode-substr

JENA-1981 Unicode and SUBSTR

> SUBSTR fails on strings with codepoints beyond U+1
> --
>
> Key: JENA-1981
> URL: https://issues.apache.org/jira/browse/JENA-1981
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> This is from [https://github.com/w3c/rdf-tests/pull/65]
> {noformat}
> # As a UTF-16 pair, but one codepoint.
> substr('\\uD83D\\uDC6A', 2)
> {noformat}
> {noformat}
> substr('👪', 2)
> {noformat}
> The character is U+0001F46A 👪 - FAMILY.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1980) Error with CacheGuava when compiling source

2020-10-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1980:
---

Commit aaa6e8160cea094af0368f0a354496e7205e143a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=aaa6e81 ]

Merge pull request #814 from afs/pom-cleaning

POM cleaning (from JENA-1980)

> Error with CacheGuava when compiling source
> ---
>
> Key: JENA-1980
> URL: https://issues.apache.org/jira/browse/JENA-1980
> Project: Apache Jena
>  Issue Type: Question
>  Components: Base
>Affects Versions: Jena 3.16.0
> Environment: IntelliJ 2020.2 on Windows.
>Reporter: Martin Pekár
>Priority: Critical
>  Labels: build
> Fix For: Jena 3.16.0
>
> Attachments: output.txt
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When running the tests, or compiling the source, an error is returned 
> indicating that package org.apache.jena.ext.com.google.common.cache does not 
> exists. Furthermore, the last 4 plugins in the pom.xml file are not found by 
> Maven. These are the following:
>  
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.17
>  
> org.apache.maven.plugins
> maven-jxr-plugin
> 2.5
>  
> org.apache.maven.plugins
> maven-pmd-plugin
> 3.8
>  
> com.github.spotbugs
> spotbugs-maven-plugin
> 3.1.1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1980) Error with CacheGuava when compiling source

2020-10-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1980:
---

Commit 32f1c4c0498b7ca4376842cc2b45db6116ec358a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=32f1c4c ]

POM cleaning (from JENA-1980)


> Error with CacheGuava when compiling source
> ---
>
> Key: JENA-1980
> URL: https://issues.apache.org/jira/browse/JENA-1980
> Project: Apache Jena
>  Issue Type: Question
>  Components: Base
>Affects Versions: Jena 3.16.0
> Environment: IntelliJ 2020.2 on Windows.
>Reporter: Martin Pekár
>Priority: Critical
>  Labels: build
> Fix For: Jena 3.16.0
>
> Attachments: output.txt
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When running the tests, or compiling the source, an error is returned 
> indicating that package org.apache.jena.ext.com.google.common.cache does not 
> exists. Furthermore, the last 4 plugins in the pom.xml file are not found by 
> Maven. These are the following:
>  
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.17
>  
> org.apache.maven.plugins
> maven-jxr-plugin
> 2.5
>  
> org.apache.maven.plugins
> maven-pmd-plugin
> 3.8
>  
> com.github.spotbugs
> spotbugs-maven-plugin
> 3.1.1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1979) SHACL validation: NullPointerException when shapes with sh:alternativePath importing

2020-10-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1979:
---

Commit 7e98a8accd09264284cc978c6199f3073259a054 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=7e98a8a ]

Merge pull request #810 from afs/jena1979-shacl-path

JENA-1979: Protect against complex paths for $PATH

> SHACL validation: NullPointerException when shapes with sh:alternativePath 
> importing 
> -
>
> Key: JENA-1979
> URL: https://issues.apache.org/jira/browse/JENA-1979
> Project: Apache Jena
>  Issue Type: Bug
>  Components: SHACL
>Affects Versions: Jena 3.16.0
> Environment: Run
> {{Graph shapesGraph = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM).read("shapes.ttl", 
> "TTL").getGraph();}}
> {{ Graph dataGraph = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM).read("data.ttl", 
> "TTL").getGraph();}}
> {{ validator = ShaclValidator.get();}}
> {{ return validator.validate(shapesGraph, dataGraph);}}
>Reporter: Jan Rosecky
>Priority: Major
> Attachments: data.ttl, shapes.ttl
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> h2. How to replicate
> Run
> Graph shapesGraph = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM).read("shapes.ttl", 
> "TTL").getGraph();
> {{Graph dataGraph = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM).read("data.ttl", 
> "TTL").getGraph();
> {{validator = ShaclValidator.get();}}
> {{return validator.validate(shapesGraph, dataGraph);}}
> Files attached.
> h2. What is happening
> The exception happens when a property shape with sh:alternativePath is 
> evaluated inside ConstraintComponentSPARQL. I'm not sure why however it only 
> happens when dash/tosh shapes are imported by a shape.
> The exception seems to happen on line 239 of SparqlValidation.java:
> {{RDFNode z = ModelUtils.convertGraphNodeToRDFNode(ShaclPaths.pathNode(path), 
> model);}}
> where pathNode() returns null - only supporting P_Link, not P_Alt and 
> convertGraphNodeToRDFNode() then runs unchecked node.isVariable().
> Stack trace:
> {{parameterMapToPreBinding:239, SparqlValidation 
> (org.apache.jena.shacl.engine.constraint)}}
>  {{validateMap:122, SparqlValidation 
> (org.apache.jena.shacl.engine.constraint)}}
>  {{validate:87, SparqlValidation (org.apache.jena.shacl.engine.constraint)}}
>  {{lambda$validatePropertyShape$0:69, ConstraintComponentSPARQL 
> (org.apache.jena.shacl.engine.constraint)}}
>  {{accept:-1, 1035363280 
> (org.apache.jena.shacl.engine.constraint.ConstraintComponentSPARQL$$Lambda$125)}}
>  {{forEach:75, Iterable (java.lang)}}
>  {{validatePropertyShape:68, ConstraintComponentSPARQL 
> (org.apache.jena.shacl.engine.constraint)}}
>  {{evalConstraint:264, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{validationPropertyShape:248, ValidationProc 
> (org.apache.jena.shacl.validation)}}
>  {{validationPropertyShapes:228, ValidationProc 
> (org.apache.jena.shacl.validation)}}
>  {{validateShape:219, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{simpleValidationInternal:178, ValidationProc 
> (org.apache.jena.shacl.validation)}}
>  {{simpleValidation:122, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{simpleValidation:109, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{simpleValidation:101, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{validate:79, ShaclSimpleValidator (org.apache.jena.shacl.validation)}}
>  {{validate:91, ShaclSimpleValidator (org.apache.jena.shacl.validation)}}
>  {{validate:23, mytest (com.msd.gin.mrlitdi.test)}}
>  {{run:17, mytest (com.msd.gin.mrlitdi.test)}}
>  {{invoke0:-1, NativeMethodAccessorImpl (sun.reflect)}}
>  {{invoke:62, NativeMethodAccessorImpl (sun.reflect)}}
>  {{invoke:43, DelegatingMethodAccessorImpl (sun.reflect)}}
>  {{invoke:498, Method (java.lang.reflect)}}
>  {{runReflectiveCall:50, FrameworkMethod$1 (org.junit.runners.model)}}
>  {{run:12, ReflectiveCallable (org.junit.internal.runners.model)}}
>  {{invokeExplosively:47, FrameworkMethod (org.junit.runners.model)}}
>  {{evaluate:17, InvokeMethod (org.junit.internal.runners.statements)}}
>  {{runLeaf:325, ParentRunner (org.junit.runners)}}
>  {{runChild:78, BlockJUnit4ClassRunner (org.junit.runners)}}
>  {{runChild:57, BlockJUnit4ClassRunner (org.junit.runners)}}
>  {{run:290, ParentRunner$3 (org.junit.runners)}}
>  {{schedule:71, ParentRunner$1 (org.junit.runners)}}
>  {{runChildren:288, ParentRunner (org.junit.runners)}}
>  {{access$000:58, ParentRunner (org.junit.runners)}}
>  {{evaluate:268, Pa

[jira] [Commented] (JENA-1979) SHACL validation: NullPointerException when shapes with sh:alternativePath importing

2020-10-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1979:
---

Commit 54b1f508498d172fe2f5d690a56eec525b681022 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=54b1f50 ]

JENA-1979: Protect against complex paths for $PATH


> SHACL validation: NullPointerException when shapes with sh:alternativePath 
> importing 
> -
>
> Key: JENA-1979
> URL: https://issues.apache.org/jira/browse/JENA-1979
> Project: Apache Jena
>  Issue Type: Bug
>  Components: SHACL
>Affects Versions: Jena 3.16.0
> Environment: Run
> {{Graph shapesGraph = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM).read("shapes.ttl", 
> "TTL").getGraph();}}
> {{ Graph dataGraph = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM).read("data.ttl", 
> "TTL").getGraph();}}
> {{ validator = ShaclValidator.get();}}
> {{ return validator.validate(shapesGraph, dataGraph);}}
>Reporter: Jan Rosecky
>Priority: Major
> Attachments: data.ttl, shapes.ttl
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> h2. How to replicate
> Run
> Graph shapesGraph = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM).read("shapes.ttl", 
> "TTL").getGraph();
> {{Graph dataGraph = 
> ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM).read("data.ttl", 
> "TTL").getGraph();
> {{validator = ShaclValidator.get();}}
> {{return validator.validate(shapesGraph, dataGraph);}}
> Files attached.
> h2. What is happening
> The exception happens when a property shape with sh:alternativePath is 
> evaluated inside ConstraintComponentSPARQL. I'm not sure why however it only 
> happens when dash/tosh shapes are imported by a shape.
> The exception seems to happen on line 239 of SparqlValidation.java:
> {{RDFNode z = ModelUtils.convertGraphNodeToRDFNode(ShaclPaths.pathNode(path), 
> model);}}
> where pathNode() returns null - only supporting P_Link, not P_Alt and 
> convertGraphNodeToRDFNode() then runs unchecked node.isVariable().
> Stack trace:
> {{parameterMapToPreBinding:239, SparqlValidation 
> (org.apache.jena.shacl.engine.constraint)}}
>  {{validateMap:122, SparqlValidation 
> (org.apache.jena.shacl.engine.constraint)}}
>  {{validate:87, SparqlValidation (org.apache.jena.shacl.engine.constraint)}}
>  {{lambda$validatePropertyShape$0:69, ConstraintComponentSPARQL 
> (org.apache.jena.shacl.engine.constraint)}}
>  {{accept:-1, 1035363280 
> (org.apache.jena.shacl.engine.constraint.ConstraintComponentSPARQL$$Lambda$125)}}
>  {{forEach:75, Iterable (java.lang)}}
>  {{validatePropertyShape:68, ConstraintComponentSPARQL 
> (org.apache.jena.shacl.engine.constraint)}}
>  {{evalConstraint:264, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{validationPropertyShape:248, ValidationProc 
> (org.apache.jena.shacl.validation)}}
>  {{validationPropertyShapes:228, ValidationProc 
> (org.apache.jena.shacl.validation)}}
>  {{validateShape:219, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{simpleValidationInternal:178, ValidationProc 
> (org.apache.jena.shacl.validation)}}
>  {{simpleValidation:122, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{simpleValidation:109, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{simpleValidation:101, ValidationProc (org.apache.jena.shacl.validation)}}
>  {{validate:79, ShaclSimpleValidator (org.apache.jena.shacl.validation)}}
>  {{validate:91, ShaclSimpleValidator (org.apache.jena.shacl.validation)}}
>  {{validate:23, mytest (com.msd.gin.mrlitdi.test)}}
>  {{run:17, mytest (com.msd.gin.mrlitdi.test)}}
>  {{invoke0:-1, NativeMethodAccessorImpl (sun.reflect)}}
>  {{invoke:62, NativeMethodAccessorImpl (sun.reflect)}}
>  {{invoke:43, DelegatingMethodAccessorImpl (sun.reflect)}}
>  {{invoke:498, Method (java.lang.reflect)}}
>  {{runReflectiveCall:50, FrameworkMethod$1 (org.junit.runners.model)}}
>  {{run:12, ReflectiveCallable (org.junit.internal.runners.model)}}
>  {{invokeExplosively:47, FrameworkMethod (org.junit.runners.model)}}
>  {{evaluate:17, InvokeMethod (org.junit.internal.runners.statements)}}
>  {{runLeaf:325, ParentRunner (org.junit.runners)}}
>  {{runChild:78, BlockJUnit4ClassRunner (org.junit.runners)}}
>  {{runChild:57, BlockJUnit4ClassRunner (org.junit.runners)}}
>  {{run:290, ParentRunner$3 (org.junit.runners)}}
>  {{schedule:71, ParentRunner$1 (org.junit.runners)}}
>  {{runChildren:288, ParentRunner (org.junit.runners)}}
>  {{access$000:58, ParentRunner (org.junit.runners)}}
>  {{evaluate:268, ParentRunner$2 (org.junit.runners)}}
>  {{run:363, Pare

[jira] [Commented] (JENA-1977) ja:rule does not process @prefix.

2020-10-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1977:
---

Commit dbbcea3051ec850a752fe439927ce8822033747e in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=dbbcea3 ]

Merge pull request #809 from afs/jena1977-process-rule-header

JENA-1977: Parse rules header

> ja:rule does not process @prefix.
> -
>
> Key: JENA-1977
> URL: https://issues.apache.org/jira/browse/JENA-1977
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Report: 
> [https://lists.apache.org/thread.html/rfb65bb5d0a140d80ce8a9e08831a57562fdaea6c7e2255831f91b1b7%40%3Cusers.jena.apache.org%3E]
> {{ja:rule}} does not grok @prefix or @import.
> {{Rule.parseRules(String)}} directly calls the rule parer, whereas 
> {{rulesParserFromReader}} processes the input to handle the header, then 
> calls the rule parser.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1978) Add examples for Fuseki Main

2020-10-11 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1978:
---

Commit 97785d438d5ca053af16b0e68c771a098fecc8f5 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=97785d4 ]

JENA-1978: Parse rules header


> Add examples for Fuseki Main
> 
>
> Key: JENA-1978
> URL: https://issues.apache.org/jira/browse/JENA-1978
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Add more examples for Fuseki Main configuration and custoization.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1978) Add examples for Fuseki Main

2020-10-10 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1978:
---

Commit e0737568a56e48aae4f46fc6776179f8b72174c3 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=e073756 ]

JENA-1978: Fuseki examples


> Add examples for Fuseki Main
> 
>
> Key: JENA-1978
> URL: https://issues.apache.org/jira/browse/JENA-1978
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Add more examples for Fuseki Main configuration and custoization.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1976) Make CORS support in Fuseki main the default or always on.

2020-10-10 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1976:
---

Commit 5d7898306fe5a2e6402302ab6535c636f625db7a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=5d78983 ]

JENA-1976: Default to enabled CORS for coimmand line Fuskei main exec


> Make CORS support in Fuseki main the default or always on.
> --
>
> Key: JENA-1976
> URL: https://issues.apache.org/jira/browse/JENA-1976
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> CORS support was added to Fuseki main in JENA-1846.
> It is activated by command line \{{–cors}}.
> This ticket is to ask the community whether CORS should always be available 
> as it is in Fuseki Webapp.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1978) Add examples for Fuseki Main

2020-10-10 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1978:
---

Commit ebf15c7c6338cbc4de5fdab9e6e06ed75671d685 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=ebf15c7 ]

Merge pull request #808 from afs/fuseki-examples

JENA-1978: Fuseki examples

> Add examples for Fuseki Main
> 
>
> Key: JENA-1978
> URL: https://issues.apache.org/jira/browse/JENA-1978
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Add more examples for Fuseki Main configuration and custoization.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1974) Function library for working with Graph objects

2020-10-05 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1974:
---

Commit 65d571cfdf5ce3257fea29aa6996b31ecb43da3a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=65d571c ]

Merge pull request #804 from afs/graph-ops

JENA-1974: G, a library of functions for working with Graph.

> Function library for working with Graph objects
> ---
>
> Key: JENA-1974
> URL: https://issues.apache.org/jira/browse/JENA-1974
> Project: Apache Jena
>  Issue Type: New Feature
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> This ticket introduces a library "G" (with the expectation it is usually a 
> static import) for writing code working with Graph. It is based on original 
> use in jena-shacl but is itself generally useful when working in Java walking 
> data in graphs.
> It provides checking operation like "getOne" when the code is expecting 
> exactly one match, not zero, not several.
> There are some operations that are RDFS aware - these would be applicable for 
> when RDFS reasoning is not enabled (in SHACL, certain parts of RDFS are 
> required like transitive subclass but not full RDFS reasoning).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1974) Function library for working with Graph objects

2020-10-05 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1974:
---

Commit 2ce67087fc0decde38d3c79b6b85dde259c788ea in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2ce6708 ]

JENA-1974: Function library for working with graphs


> Function library for working with Graph objects
> ---
>
> Key: JENA-1974
> URL: https://issues.apache.org/jira/browse/JENA-1974
> Project: Apache Jena
>  Issue Type: New Feature
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> This ticket introduces a library "G" (with the expectation it is usually a 
> static import) for writing code working with Graph. It is based on original 
> use in jena-shacl but is itself generally useful when working in Java walking 
> data in graphs.
> It provides checking operation like "getOne" when the code is expecting 
> exactly one match, not zero, not several.
> There are some operations that are RDFS aware - these would be applicable for 
> when RDFS reasoning is not enabled (in SHACL, certain parts of RDFS are 
> required like transitive subclass but not full RDFS reasoning).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1975) Clean Log support and check usage.

2020-10-04 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1975:
---

Commit 60b3984151172bcd69755a3edaf4d0bc5b7c928a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=60b3984 ]

Merge pull request #806 from afs/clean-logging

JENA-1975: Clean up logging

> Clean Log support and check usage.
> --
>
> Key: JENA-1975
> URL: https://issues.apache.org/jira/browse/JENA-1975
> Project: Apache Jena
>  Issue Type: New Feature
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The class "Log" provides easy use of logging. Some places were calling with 
> "Loggers" as first argument which caused the wrong output.
> This clean:
>  # Make determining the logger to use dynamic by introspection
>  # Remove unnecessary Log operations
>  # Cleans up call sites anyway
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1975) Clean Log support and check usage.

2020-10-04 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1975:
---

Commit 86fbc49921c7f7f199f8e188d6439a22a26dc4f0 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=86fbc49 ]

JENA-1975: Clean up logging


> Clean Log support and check usage.
> --
>
> Key: JENA-1975
> URL: https://issues.apache.org/jira/browse/JENA-1975
> Project: Apache Jena
>  Issue Type: New Feature
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The class "Log" provides easy use of logging. Some places were calling with 
> "Loggers" as first argument which caused the wrong output.
> This clean:
>  # Make determining the logger to use dynamic by introspection
>  # Remove unnecessary Log operations
>  # Cleans up call sites anyway
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1972) Update Jetty dependency version

2020-10-04 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1972:
---

Commit e941c9e3fbe8698f6ec76a4bfc03ed7e61af377b in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=e941c9e ]

JENA-1972: Update Jetty dependency to 9.4.31


> Update Jetty dependency version
> ---
>
> Key: JENA-1972
> URL: https://issues.apache.org/jira/browse/JENA-1972
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Update: 9.4.26 -> 9.4.31



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1973) Update Micrometer dependency

2020-10-04 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1973:
---

Commit 4f9c7987c89faf710897a057e6397efb00ac9a34 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=4f9c798 ]

JENA-1973: Update Micrometer dependency to 1.5.5


> Update Micrometer dependency
> 
>
> Key: JENA-1973
> URL: https://issues.apache.org/jira/browse/JENA-1973
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>
> Update 1.2.1 -> 1.5.1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1973) Update Micrometer dependency

2020-10-04 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1973:
---

Commit ff08afd590a666c663d26ce1c000b8e5e48c3b8c in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=ff08afd ]

Merge pull request #805 from afs/updates

JENA-1972, JENA-1973: Updates for Jetty and Micrometer

> Update Micrometer dependency
> 
>
> Key: JENA-1973
> URL: https://issues.apache.org/jira/browse/JENA-1973
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>
> Update 1.2.1 -> 1.5.1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1972) Update Jetty dependency version

2020-10-04 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1972:
---

Commit ff08afd590a666c663d26ce1c000b8e5e48c3b8c in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=ff08afd ]

Merge pull request #805 from afs/updates

JENA-1972, JENA-1973: Updates for Jetty and Micrometer

> Update Jetty dependency version
> ---
>
> Key: JENA-1972
> URL: https://issues.apache.org/jira/browse/JENA-1972
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.17.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Update: 9.4.26 -> 9.4.31



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1967) Update dependency for jsonld-java to 0.13.1

2020-09-25 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1967:
---

Commit 248f585fcda425e2dae8524f8a530a6e1bbcba36 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=248f585 ]

Merge pull request #802 from umbreak/docs_and_test_bump

JENA-1967: Bumped JsonLD Java dependency; fixed tests

> Update dependency for jsonld-java to 0.13.1
> ---
>
> Key: JENA-1967
> URL: https://issues.apache.org/jira/browse/JENA-1967
> Project: Apache Jena
>  Issue Type: Task
>Affects Versions: Jena 3.16.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1950) Replace Nashorn with GraalVM-based JavaScript engine

2020-09-25 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on JENA-1950:
---

Commit 38b659c9973492e0b74903b1b653dd9492ddfe95 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=38b659c ]

Merge pull request #801 from strangepleasures/make-graalvm-test-dependency

JENA-1950: Make GraalVM a test dependency

> Replace Nashorn with GraalVM-based JavaScript engine
> 
>
> Key: JENA-1950
> URL: https://issues.apache.org/jira/browse/JENA-1950
> Project: Apache Jena
>  Issue Type: Task
>  Components: ARQ
>Reporter: Pavel Mikhailovskii
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.17.0
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> ARQ is using the Nashorn JavaScript engine which will be 
> [removed|https://openjdk.java.net/jeps/372] in JDK 15. To keep supporting 
> JavaScript in Jena we need to migrate to GraalVM-based JavaScript engine. 
> Backward compatibility can be achieved by enabling Nashorn-compatibility mode.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


<    1   2   3   4   5   6   7   8   9   10   >