[jira] [Commented] (JENA-1462) RDF/XML parsing fails on newer/provisional/private URI schemes in base URI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-1462:
--

Github user afs commented on the issue:

https://github.com/apache/jena/pull/341
  
To be clear: RIOT based parsing does not enforce IANA checking. It was just 
that the RDF/XML parser didn't pick up the right IRIFactory via RIOT.


https://github.com/apache/jena/pull/342/commits/aecfaac0d631995120b77f22059291ffe6b9f06f


> RDF/XML parsing fails on newer/provisional/private URI schemes in base URI
> --
>
> Key: JENA-1462
> URL: https://issues.apache.org/jira/browse/JENA-1462
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ, RDF/XML
>Affects Versions: Jena 3.3.0, Jena 3.4.0, Jena 3.5.0, Jena 3.6.0
> Environment: Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.10.0-42-generic", arch: "amd64", family: "unix"
> Distributor ID:   Ubuntu
> Description:  Ubuntu 16.04.3 LTS
> Release:  16.04
> Codename: xenial
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>
> RIOT parsing RDF/XML with a base URI different from http/https/file, such as 
> ssh://, fails.
> See https://github.com/stain/jena-test-unregistered-iana for some tests I 
> came up with.
> Tests fail both for xml:base or if the base URI is provided to RDFDataMgr, 
> but not if the URI is full inside the RDF/XML.
> {code}
> org.apache.jena.riot.RiotException: [line: 5, col: 40] {E214} Resolving 
> against bad URI : 
>   at 
> org.apache.jena.riot.TestParseURISchemeBases.sshBaseRDF(TestParseURISchemeBases.java:336)
> {code}
> This error message comes from ERR_RESOLVING_AGAINST_MALFORMED_BASE - for some 
> reason the warning becomes an error as the IRI Factory used for creating the 
> Base IRI within the RDF/XML parser is a bit too strict.
> However I could not find anything in the specs:
> * https://www.w3.org/TR/2014/REC-rdf-syntax-grammar-20140225/
> * https://www.w3.org/TR/2009/REC-xmlbase-20090128/
> * https://www.ietf.org/rfc/rfc3986
> that says "foreign" URI schemes should not be permitted. Anyway Jena's IANA 
> list is probably out of date, as my tests shown.
> This was initially detected in TAVERNA-1027 which tries to parse an RDF/XML 
> with the [app:// URI scheme|https://www.w3.org/TR/app-uri/] , which is *not* 
> registered with IANA https://www.iana.org/assignments/uri-schemes according 
> to https://tools.ietf.org/html/bcp35
> However, testing Jena with other permanent and provisional schemes from the 
> registry, such as example://, ssh:// or a conformant private scheme with a 
> domain-based name org.apache.jena.test:// also give the same error.  
> IMHO they should all be understood in the same way as when parsing the Turtle 
> examples, which don't fail.
> I could trace this back to Jena 3.3.0, so I suspect this was introduced with 
> JENA-1306. With versions before that all my tests *) work.
> I'll raise a pull request with the junit tests, but have not been able to 
> find a good way to fix it.
> _*) There's a separate issue that hostnames in file://example.com/etc/passwd 
> style URIs also seem to be misparsed in RDF/XML into 
> file:///example.com/etc/passwd , reported separately as JENA-1463, that goes 
> back till 3.0.1._



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena issue #341: JENA-1462: Tests RDF/XML parsing newer URI schemes

[afs]

Github user afs commented on the issue:

https://github.com/apache/jena/pull/341
  
To be clear: RIOT based parsing does not enforce IANA checking. It was just 
that the RDF/XML parser didn't pick up the right IRIFactory via RIOT.


https://github.com/apache/jena/pull/342/commits/aecfaac0d631995120b77f22059291ffe6b9f06f


---

[jira] [Commented] (JENA-1462) RDF/XML parsing fails on newer/provisional/private URI schemes in base URI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-1462:
--

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/341#discussion_r161378376
  
--- Diff: jena-arq/testing/RIOT/URISchemes/app.nt ---
@@ -0,0 +1 @@
+ 
 
 .
--- End diff --

N-Triples is handled differently - there is no IRI base resolution in 
normal parsing; this is intentional.

The command line "riot" specially adds IRI checking for N-Triples. Please 
remove the NT tests.




> RDF/XML parsing fails on newer/provisional/private URI schemes in base URI
> --
>
> Key: JENA-1462
> URL: https://issues.apache.org/jira/browse/JENA-1462
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ, RDF/XML
>Affects Versions: Jena 3.3.0, Jena 3.4.0, Jena 3.5.0, Jena 3.6.0
> Environment: Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.10.0-42-generic", arch: "amd64", family: "unix"
> Distributor ID:   Ubuntu
> Description:  Ubuntu 16.04.3 LTS
> Release:  16.04
> Codename: xenial
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>
> RIOT parsing RDF/XML with a base URI different from http/https/file, such as 
> ssh://, fails.
> See https://github.com/stain/jena-test-unregistered-iana for some tests I 
> came up with.
> Tests fail both for xml:base or if the base URI is provided to RDFDataMgr, 
> but not if the URI is full inside the RDF/XML.
> {code}
> org.apache.jena.riot.RiotException: [line: 5, col: 40] {E214} Resolving 
> against bad URI : 
>   at 
> org.apache.jena.riot.TestParseURISchemeBases.sshBaseRDF(TestParseURISchemeBases.java:336)
> {code}
> This error message comes from ERR_RESOLVING_AGAINST_MALFORMED_BASE - for some 
> reason the warning becomes an error as the IRI Factory used for creating the 
> Base IRI within the RDF/XML parser is a bit too strict.
> However I could not find anything in the specs:
> * https://www.w3.org/TR/2014/REC-rdf-syntax-grammar-20140225/
> * https://www.w3.org/TR/2009/REC-xmlbase-20090128/
> * https://www.ietf.org/rfc/rfc3986
> that says "foreign" URI schemes should not be permitted. Anyway Jena's IANA 
> list is probably out of date, as my tests shown.
> This was initially detected in TAVERNA-1027 which tries to parse an RDF/XML 
> with the [app:// URI scheme|https://www.w3.org/TR/app-uri/] , which is *not* 
> registered with IANA https://www.iana.org/assignments/uri-schemes according 
> to https://tools.ietf.org/html/bcp35
> However, testing Jena with other permanent and provisional schemes from the 
> registry, such as example://, ssh:// or a conformant private scheme with a 
> domain-based name org.apache.jena.test:// also give the same error.  
> IMHO they should all be understood in the same way as when parsing the Turtle 
> examples, which don't fail.
> I could trace this back to Jena 3.3.0, so I suspect this was introduced with 
> JENA-1306. With versions before that all my tests *) work.
> I'll raise a pull request with the junit tests, but have not been able to 
> find a good way to fix it.
> _*) There's a separate issue that hostnames in file://example.com/etc/passwd 
> style URIs also seem to be misparsed in RDF/XML into 
> file:///example.com/etc/passwd , reported separately as JENA-1463, that goes 
> back till 3.0.1._



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena pull request #341: JENA-1462: Tests RDF/XML parsing newer URI schemes

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/341#discussion_r161378376
  
--- Diff: jena-arq/testing/RIOT/URISchemes/app.nt ---
@@ -0,0 +1 @@
+ 
 
 .
--- End diff --

N-Triples is handled differently - there is no IRI base resolution in 
normal parsing; this is intentional.

The command line "riot" specially adds IRI checking for N-Triples. Please 
remove the NT tests.




---

[jira] [Commented] (JENA-1462) RDF/XML parsing fails on newer/provisional/private URI schemes in base URI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-1462:
--

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/341#discussion_r161378072
  
--- Diff: jena-arq/testing/RIOT/URISchemes/file-base.rdf ---
@@ -0,0 +1,8 @@
+http://2dee5b0a-6100-470a-a67f-1399518cb470/nested/;
--- End diff --

Wrong URI scheme, was "file://example.com/nested/" intended?


> RDF/XML parsing fails on newer/provisional/private URI schemes in base URI
> --
>
> Key: JENA-1462
> URL: https://issues.apache.org/jira/browse/JENA-1462
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ, RDF/XML
>Affects Versions: Jena 3.3.0, Jena 3.4.0, Jena 3.5.0, Jena 3.6.0
> Environment: Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.10.0-42-generic", arch: "amd64", family: "unix"
> Distributor ID:   Ubuntu
> Description:  Ubuntu 16.04.3 LTS
> Release:  16.04
> Codename: xenial
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>
> RIOT parsing RDF/XML with a base URI different from http/https/file, such as 
> ssh://, fails.
> See https://github.com/stain/jena-test-unregistered-iana for some tests I 
> came up with.
> Tests fail both for xml:base or if the base URI is provided to RDFDataMgr, 
> but not if the URI is full inside the RDF/XML.
> {code}
> org.apache.jena.riot.RiotException: [line: 5, col: 40] {E214} Resolving 
> against bad URI : 
>   at 
> org.apache.jena.riot.TestParseURISchemeBases.sshBaseRDF(TestParseURISchemeBases.java:336)
> {code}
> This error message comes from ERR_RESOLVING_AGAINST_MALFORMED_BASE - for some 
> reason the warning becomes an error as the IRI Factory used for creating the 
> Base IRI within the RDF/XML parser is a bit too strict.
> However I could not find anything in the specs:
> * https://www.w3.org/TR/2014/REC-rdf-syntax-grammar-20140225/
> * https://www.w3.org/TR/2009/REC-xmlbase-20090128/
> * https://www.ietf.org/rfc/rfc3986
> that says "foreign" URI schemes should not be permitted. Anyway Jena's IANA 
> list is probably out of date, as my tests shown.
> This was initially detected in TAVERNA-1027 which tries to parse an RDF/XML 
> with the [app:// URI scheme|https://www.w3.org/TR/app-uri/] , which is *not* 
> registered with IANA https://www.iana.org/assignments/uri-schemes according 
> to https://tools.ietf.org/html/bcp35
> However, testing Jena with other permanent and provisional schemes from the 
> registry, such as example://, ssh:// or a conformant private scheme with a 
> domain-based name org.apache.jena.test:// also give the same error.  
> IMHO they should all be understood in the same way as when parsing the Turtle 
> examples, which don't fail.
> I could trace this back to Jena 3.3.0, so I suspect this was introduced with 
> JENA-1306. With versions before that all my tests *) work.
> I'll raise a pull request with the junit tests, but have not been able to 
> find a good way to fix it.
> _*) There's a separate issue that hostnames in file://example.com/etc/passwd 
> style URIs also seem to be misparsed in RDF/XML into 
> file:///example.com/etc/passwd , reported separately as JENA-1463, that goes 
> back till 3.0.1._



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena pull request #341: JENA-1462: Tests RDF/XML parsing newer URI schemes

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/341#discussion_r161378072
  
--- Diff: jena-arq/testing/RIOT/URISchemes/file-base.rdf ---
@@ -0,0 +1,8 @@
+http://2dee5b0a-6100-470a-a67f-1399518cb470/nested/;
--- End diff --

Wrong URI scheme, was "file://example.com/nested/" intended?


---

[jira] [Commented] (JENA-1462) RDF/XML parsing fails on newer/provisional/private URI schemes in base URI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-1462:
--

GitHub user afs opened a pull request:

https://github.com/apache/jena/pull/342

IRI resolving

Cleaning up resolving IRIs.

Addresses JENA-1462 and JENA-1463.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/afs/jena iri-resolving

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/342.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #342


commit ca760f74291f8bcd4f4f983a56c0e8b7e41dddb2
Author: Andy Seaborne 
Date:   2018-01-13T17:12:26Z

Move to test source tree.

commit ed34030fc9a75095a14e310159f3a314417d6647
Author: Andy Seaborne 
Date:   2018-01-13T17:13:26Z

Use RIOT-wide global IRIResolver.iriFactory.

commit a8c99ff7a095b473a756f6709fdb5803e42f625e
Author: Andy Seaborne 
Date:   2018-01-13T17:15:15Z

Deprecate FileUtils.toURL

commit 35a5cc927222ea69d827633e13dd9065676558eb
Author: Andy Seaborne 
Date:   2018-01-13T17:17:22Z

N3IRIResolver for jena-core test support only.

commit c055fa62b54ff800a820b87712a1c5403ff366e5
Author: Andy Seaborne 
Date:   2018-01-13T17:19:18Z

Add documentation about legecay uses. Clean classes.

commit aecfaac0d631995120b77f22059291ffe6b9f06f
Author: Andy Seaborne 
Date:   2018-01-13T17:22:03Z

JENA-1462: Use RIOT global default resolver.

commit 1d037e80dfd8a91e9c4042f65695cadec4b17097
Author: Andy Seaborne 
Date:   2018-01-13T17:24:29Z

JENA-1463: Fix for file://host/path




> RDF/XML parsing fails on newer/provisional/private URI schemes in base URI
> --
>
> Key: JENA-1462
> URL: https://issues.apache.org/jira/browse/JENA-1462
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ, RDF/XML
>Affects Versions: Jena 3.3.0, Jena 3.4.0, Jena 3.5.0, Jena 3.6.0
> Environment: Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.10.0-42-generic", arch: "amd64", family: "unix"
> Distributor ID:   Ubuntu
> Description:  Ubuntu 16.04.3 LTS
> Release:  16.04
> Codename: xenial
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>
> RIOT parsing RDF/XML with a base URI different from http/https/file, such as 
> ssh://, fails.
> See https://github.com/stain/jena-test-unregistered-iana for some tests I 
> came up with.
> Tests fail both for xml:base or if the base URI is provided to RDFDataMgr, 
> but not if the URI is full inside the RDF/XML.
> {code}
> org.apache.jena.riot.RiotException: [line: 5, col: 40] {E214} Resolving 
> against bad URI : 
>   at 
> org.apache.jena.riot.TestParseURISchemeBases.sshBaseRDF(TestParseURISchemeBases.java:336)
> {code}
> This error message comes from ERR_RESOLVING_AGAINST_MALFORMED_BASE - for some 
> reason the warning becomes an error as the IRI Factory used for creating the 
> Base IRI within the RDF/XML parser is a bit too strict.
> However I could not find anything in the specs:
> * https://www.w3.org/TR/2014/REC-rdf-syntax-grammar-20140225/
> * https://www.w3.org/TR/2009/REC-xmlbase-20090128/
> * https://www.ietf.org/rfc/rfc3986
> that says "foreign" URI schemes should not be permitted. Anyway Jena's IANA 
> list is probably out of date, as my tests shown.
> This was initially detected in TAVERNA-1027 which tries to parse an RDF/XML 
> with the [app:// URI scheme|https://www.w3.org/TR/app-uri/] , which is *not* 
> registered with IANA https://www.iana.org/assignments/uri-schemes according 
> to https://tools.ietf.org/html/bcp35
> However, testing Jena with other permanent and provisional schemes from the 
> registry, such as example://, ssh:// or a conformant private scheme with a 
> domain-based name org.apache.jena.test:// also give the same error.  
> IMHO they should all be understood in the same way as when parsing the Turtle 
> examples, which don't fail.
> I could trace this back to Jena 3.3.0, so I suspect this was introduced with 
> JENA-1306. With versions before that all my tests *) work.
> I'll raise a pull request with the junit tests, but have not been able to 
> find a good way to fix it.
> _*) There's a separate issue that hostnames in file://example.com/etc/passwd 
> style URIs also seem to be misparsed in RDF/XML into 
> file:///example.com/etc/passwd , reported separately as 

[GitHub] jena pull request #342: IRI resolving

[afs]

GitHub user afs opened a pull request:

https://github.com/apache/jena/pull/342

IRI resolving

Cleaning up resolving IRIs.

Addresses JENA-1462 and JENA-1463.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/afs/jena iri-resolving

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/342.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #342


commit ca760f74291f8bcd4f4f983a56c0e8b7e41dddb2
Author: Andy Seaborne 
Date:   2018-01-13T17:12:26Z

Move to test source tree.

commit ed34030fc9a75095a14e310159f3a314417d6647
Author: Andy Seaborne 
Date:   2018-01-13T17:13:26Z

Use RIOT-wide global IRIResolver.iriFactory.

commit a8c99ff7a095b473a756f6709fdb5803e42f625e
Author: Andy Seaborne 
Date:   2018-01-13T17:15:15Z

Deprecate FileUtils.toURL

commit 35a5cc927222ea69d827633e13dd9065676558eb
Author: Andy Seaborne 
Date:   2018-01-13T17:17:22Z

N3IRIResolver for jena-core test support only.

commit c055fa62b54ff800a820b87712a1c5403ff366e5
Author: Andy Seaborne 
Date:   2018-01-13T17:19:18Z

Add documentation about legecay uses. Clean classes.

commit aecfaac0d631995120b77f22059291ffe6b9f06f
Author: Andy Seaborne 
Date:   2018-01-13T17:22:03Z

JENA-1462: Use RIOT global default resolver.

commit 1d037e80dfd8a91e9c4042f65695cadec4b17097
Author: Andy Seaborne 
Date:   2018-01-13T17:24:29Z

JENA-1463: Fix for file://host/path




---

[jira] [Resolved] (JENA-1461) Allow ARQ custom functions to be written in JavaScript

[Andy Seaborne (JIRA)]

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

Andy Seaborne resolved JENA-1461.
-
   Resolution: Done
Fix Version/s: Jena 3.7.0

> Allow ARQ custom functions to be written in JavaScript
> --
>
> Key: JENA-1461
> URL: https://issues.apache.org/jira/browse/JENA-1461
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
> Fix For: Jena 3.7.0
>
>
> Provide execution of JavaScript for SPARQL extension functions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (JENA-1464) Refactor Fuseki configuration to make the faciities available from the embedded server

[Andy Seaborne (JIRA)]

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

Andy Seaborne resolved JENA-1464.
-
   Resolution: Fixed
Fix Version/s: Jena 3.7.0

> Refactor Fuseki configuration to make the faciities available from the 
> embedded server
> --
>
> Key: JENA-1464
> URL: https://issues.apache.org/jira/browse/JENA-1464
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.7.0
>
>
> This will allow the Fuseki basic server to process the server section of a 
> full Fuseki configuration file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1461) Allow ARQ custom functions to be written in JavaScript

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-1461:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/340


> Allow ARQ custom functions to be written in JavaScript
> --
>
> Key: JENA-1461
> URL: https://issues.apache.org/jira/browse/JENA-1461
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> Provide execution of JavaScript for SPARQL extension functions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1464) Refactor Fuseki configuration to make the faciities available from the embedded server

[ASF subversion and git services (JIRA)]

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

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

Commit 64fe8bd9161bed88150e330d8808ed45ce35d957 in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=64fe8bd ]

JENA-1464: Refactor Fuseki configuration processing.


> Refactor Fuseki configuration to make the faciities available from the 
> embedded server
> --
>
> Key: JENA-1464
> URL: https://issues.apache.org/jira/browse/JENA-1464
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> This will allow the Fuseki basic server to process the server section of a 
> full Fuseki configuration file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1461) Allow ARQ custom functions to be written in JavaScript

[ASF subversion and git services (JIRA)]

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

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

Commit 2eb211f80aebe37f54df246ef626cffd7f5b9fc8 in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=2eb211f ]

JENA-1461: Put contants into a public place.

Improve and add tests


> Allow ARQ custom functions to be written in JavaScript
> --
>
> Key: JENA-1461
> URL: https://issues.apache.org/jira/browse/JENA-1461
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> Provide execution of JavaScript for SPARQL extension functions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1461) Allow ARQ custom functions to be written in JavaScript

[ASF subversion and git services (JIRA)]

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

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

Commit a0108d77c46616e65285f410a2f0f6cdab842c4f in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=a0108d7 ]

JENA-1461: Nashorn and threading


> Allow ARQ custom functions to be written in JavaScript
> --
>
> Key: JENA-1461
> URL: https://issues.apache.org/jira/browse/JENA-1461
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> Provide execution of JavaScript for SPARQL extension functions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1461) Allow ARQ custom functions to be written in JavaScript

[ASF subversion and git services (JIRA)]

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

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

Commit c4f79ee9f908f301028a4e13dfc7c2fc2de89cbf in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=c4f79ee ]

JENA-1461: JavaScript custom functions


> Allow ARQ custom functions to be written in JavaScript
> --
>
> Key: JENA-1461
> URL: https://issues.apache.org/jira/browse/JENA-1461
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> Provide execution of JavaScript for SPARQL extension functions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena pull request #340: JENA-1461: JavaScript custom functions

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/340


---

[jira] [Comment Edited] (JENA-1463) RDF/XML parsing of file://hostname/ base URI miswrites URI

[Andy Seaborne (JIRA)]

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

Andy Seaborne edited comment on JENA-1463 at 1/13/18 10:08 AM:
---

Not related to JENA-1462.

(Quoting an RFC that post-dates the code isn't exactly evidence!)



was (Author: andy.seaborne):
Not related to JENA-1462.

(Quoiting an RFC that post-dates the code isn't exactly evidence!)


> RDF/XML parsing of file://hostname/ base URI miswrites URI
> --
>
> Key: JENA-1463
> URL: https://issues.apache.org/jira/browse/JENA-1463
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ, RDF/XML
>Affects Versions: Jena 3.0.1, Jena 3.1.0, Jena 3.1.1, Jena 3.2.0, Jena 
> 3.3.0, Jena 3.4.0, Jena 3.5.0, Jena 3.6.0
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>
> Similar to JENA-1462, but there seems to be special handling of file: URLs in 
> RDF/XML parsing, where parsing an RDF/XML file like:
> {code:xml}
>  xml:base="file://example.com/nested/"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;
> xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#;>
>   
> 
>   
> 
> {code}
> using 
> {code}
> RDFDataMgr.read(m, load("file-base.rdf"), Lang.RDFXML);
> {code}
> (Note, load() returns a InputStream, no explicit base)
> it comes out wrongly as:
> {code}
>  
>   .
> {code}
> Notice the hostname somehow became part of the path, now with a file:/// with 
> no hostname. 
> *Note: *https://tools.ietf.org/html/rfc8089#section-2 says that file URIs can 
> have a hostname, as well as the obvious hostname "localhost",  this is 
> typically used to address Windows shares no remote hosts.
> Equivalent in Turtle parses fine:
> {code}
> @base  .
> @prefix rdfs:  .
>  rdfs:seeAlso  .
> {code}
> becomes:
> {code}
>  
>   .
> {code}
> Equivalent RDF/XML without xml:base and passing file://example.com/nested/ as 
> Base also fails: 
> {code:java}
> RDFDataMgr.read(m, load("rel.rdf"), "file://example.com/nested/", 
> Lang.RDFXML);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1463) RDF/XML parsing of file://hostname/ base URI miswrites URI

[Andy Seaborne (JIRA)]

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

Andy Seaborne commented on JENA-1463:
-

Not related to JENA-1462.

(Quoiting an RFC that post-dates the code isn't exactly evidence!)


> RDF/XML parsing of file://hostname/ base URI miswrites URI
> --
>
> Key: JENA-1463
> URL: https://issues.apache.org/jira/browse/JENA-1463
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ, RDF/XML
>Affects Versions: Jena 3.0.1, Jena 3.1.0, Jena 3.1.1, Jena 3.2.0, Jena 
> 3.3.0, Jena 3.4.0, Jena 3.5.0, Jena 3.6.0
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>
> Similar to JENA-1462, but there seems to be special handling of file: URLs in 
> RDF/XML parsing, where parsing an RDF/XML file like:
> {code:xml}
>  xml:base="file://example.com/nested/"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;
> xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#;>
>   
> 
>   
> 
> {code}
> using 
> {code}
> RDFDataMgr.read(m, load("file-base.rdf"), Lang.RDFXML);
> {code}
> (Note, load() returns a InputStream, no explicit base)
> it comes out wrongly as:
> {code}
>  
>   .
> {code}
> Notice the hostname somehow became part of the path, now with a file:/// with 
> no hostname. 
> *Note: *https://tools.ietf.org/html/rfc8089#section-2 says that file URIs can 
> have a hostname, as well as the obvious hostname "localhost",  this is 
> typically used to address Windows shares no remote hosts.
> Equivalent in Turtle parses fine:
> {code}
> @base  .
> @prefix rdfs:  .
>  rdfs:seeAlso  .
> {code}
> becomes:
> {code}
>  
>   .
> {code}
> Equivalent RDF/XML without xml:base and passing file://example.com/nested/ as 
> Base also fails: 
> {code:java}
> RDFDataMgr.read(m, load("rel.rdf"), "file://example.com/nested/", 
> Lang.RDFXML);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (JENA-1463) RDF/XML parsing of file://hostname/ base URI miswrites URI

[Andy Seaborne (JIRA)]

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

Andy Seaborne reassigned JENA-1463:
---

Assignee: Andy Seaborne

> RDF/XML parsing of file://hostname/ base URI miswrites URI
> --
>
> Key: JENA-1463
> URL: https://issues.apache.org/jira/browse/JENA-1463
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ, RDF/XML
>Affects Versions: Jena 3.0.1, Jena 3.1.0, Jena 3.1.1, Jena 3.2.0, Jena 
> 3.3.0, Jena 3.4.0, Jena 3.5.0, Jena 3.6.0
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>
> Similar to JENA-1462, but there seems to be special handling of file: URLs in 
> RDF/XML parsing, where parsing an RDF/XML file like:
> {code:xml}
>  xml:base="file://example.com/nested/"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;
> xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#;>
>   
> 
>   
> 
> {code}
> using 
> {code}
> RDFDataMgr.read(m, load("file-base.rdf"), Lang.RDFXML);
> {code}
> (Note, load() returns a InputStream, no explicit base)
> it comes out wrongly as:
> {code}
>  
>   .
> {code}
> Notice the hostname somehow became part of the path, now with a file:/// with 
> no hostname. 
> *Note: *https://tools.ietf.org/html/rfc8089#section-2 says that file URIs can 
> have a hostname, as well as the obvious hostname "localhost",  this is 
> typically used to address Windows shares no remote hosts.
> Equivalent in Turtle parses fine:
> {code}
> @base  .
> @prefix rdfs:  .
>  rdfs:seeAlso  .
> {code}
> becomes:
> {code}
>  
>   .
> {code}
> Equivalent RDF/XML without xml:base and passing file://example.com/nested/ as 
> Base also fails: 
> {code:java}
> RDFDataMgr.read(m, load("rel.rdf"), "file://example.com/nested/", 
> Lang.RDFXML);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (JENA-1462) RDF/XML parsing fails on newer/provisional/private URI schemes in base URI

[Andy Seaborne (JIRA)]

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

Andy Seaborne reassigned JENA-1462:
---

Assignee: Andy Seaborne

> RDF/XML parsing fails on newer/provisional/private URI schemes in base URI
> --
>
> Key: JENA-1462
> URL: https://issues.apache.org/jira/browse/JENA-1462
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ, RDF/XML
>Affects Versions: Jena 3.3.0, Jena 3.4.0, Jena 3.5.0, Jena 3.6.0
> Environment: Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.10.0-42-generic", arch: "amd64", family: "unix"
> Distributor ID:   Ubuntu
> Description:  Ubuntu 16.04.3 LTS
> Release:  16.04
> Codename: xenial
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>
> RIOT parsing RDF/XML with a base URI different from http/https/file, such as 
> ssh://, fails.
> See https://github.com/stain/jena-test-unregistered-iana for some tests I 
> came up with.
> Tests fail both for xml:base or if the base URI is provided to RDFDataMgr, 
> but not if the URI is full inside the RDF/XML.
> {code}
> org.apache.jena.riot.RiotException: [line: 5, col: 40] {E214} Resolving 
> against bad URI : 
>   at 
> org.apache.jena.riot.TestParseURISchemeBases.sshBaseRDF(TestParseURISchemeBases.java:336)
> {code}
> This error message comes from ERR_RESOLVING_AGAINST_MALFORMED_BASE - for some 
> reason the warning becomes an error as the IRI Factory used for creating the 
> Base IRI within the RDF/XML parser is a bit too strict.
> However I could not find anything in the specs:
> * https://www.w3.org/TR/2014/REC-rdf-syntax-grammar-20140225/
> * https://www.w3.org/TR/2009/REC-xmlbase-20090128/
> * https://www.ietf.org/rfc/rfc3986
> that says "foreign" URI schemes should not be permitted. Anyway Jena's IANA 
> list is probably out of date, as my tests shown.
> This was initially detected in TAVERNA-1027 which tries to parse an RDF/XML 
> with the [app:// URI scheme|https://www.w3.org/TR/app-uri/] , which is *not* 
> registered with IANA https://www.iana.org/assignments/uri-schemes according 
> to https://tools.ietf.org/html/bcp35
> However, testing Jena with other permanent and provisional schemes from the 
> registry, such as example://, ssh:// or a conformant private scheme with a 
> domain-based name org.apache.jena.test:// also give the same error.  
> IMHO they should all be understood in the same way as when parsing the Turtle 
> examples, which don't fail.
> I could trace this back to Jena 3.3.0, so I suspect this was introduced with 
> JENA-1306. With versions before that all my tests *) work.
> I'll raise a pull request with the junit tests, but have not been able to 
> find a good way to fix it.
> _*) There's a separate issue that hostnames in file://example.com/etc/passwd 
> style URIs also seem to be misparsed in RDF/XML into 
> file:///example.com/etc/passwd , reported separately as JENA-1463, that goes 
> back till 3.0.1._



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)