[jira] [Created] (JENA-1433) Query Builder does not have a short hand method to add group clause with single triple

Claude Warren created JENA-1433: --- Summary: Query Builder does not have a short hand method to add group clause with single triple Key: JENA-1433 URL: https://issues.apache.org/jira/browse/JENA-1433

[jira] [Updated] (JENA-1432) Query Builder does not have a mechanism to put value var block in the where clause

[ https://issues.apache.org/jira/browse/JENA-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren updated JENA-1432: Issue Type: Improvement (was: Bug) > Query Builder does not have a mechanism to put value var block

[jira] [Updated] (JENA-1432) Query Builder does not have a mechanism to put value var block in the where clause

[ https://issues.apache.org/jira/browse/JENA-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren updated JENA-1432: Summary: Query Builder does not have a mechanism to put value var block in the where clause (was:

[jira] [Assigned] (JENA-1432) Query Builder does not have a mechanism to put values in

[ https://issues.apache.org/jira/browse/JENA-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren reassigned JENA-1432: --- Assignee: Claude Warren Priority: Minor (was: Major) Component/s: QueryBuilder

[jira] [Created] (JENA-1432) Query Builder does not have a mechanism to put values in

Claude Warren created JENA-1432: --- Summary: Query Builder does not have a mechanism to put values in Key: JENA-1432 URL: https://issues.apache.org/jira/browse/JENA-1432 Project: Apache Jena

ElementData.equalTo problem?

I think equalTo for ElementData is not correct. Given 2 ElementData instances ElementData 1: {noformat} VALUES ( ?x ?v ) { ( "three" ) ( "four" ) } {noformat} ElementData 2: {noformat} VALUES ( ?v ?x ) { ( "three" ) ( "four" ) } {noformat} shouldn't the equalTo() method return

[jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

[ https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263362#comment-16263362 ] Adam Jacobs commented on JENA-1427: --- Sounds great to me. Whether integrating with Java's {{Optional}} or

[jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

[ https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263306#comment-16263306 ] Andy Seaborne commented on JENA-1427: - If we add to {{ExtendedIterator}}, these are the possible

Re: mapping URIs

Another use case is where an endpoint is known to have moved. So that if the user attempts to resolve the data they are correctly redirected to the new location. On Wed, Nov 22, 2017 at 5:26 PM, Claude Warren wrote: > actually, I want the urn:foo:bar: prefixed URLs in Jena

Re: mapping URIs

actually, I want the urn:foo:bar: prefixed URLs in Jena to be converted to http://server:8080/ on the way out so that all urn:foo:bar prefixed URNs are resolvable by the browser. I would then add a script at http:server:8080/ to take the path and make a call back to fuseki to resolve the item.

Re: mapping URIs

Claude, are you saying you want people to be able to query Fuseki using urn:foo:bar:yeehaw and get back answers using http://server:8080/yeehaw? Otherwise, I'm guessing I'm missing something, but why wouldn't you do the substitutions on the way from the backend to Fuseki? ajs6f > On Nov 22,

mapping URIs

I have a case where data are generated in a backend system that is not publicly accessible and has no idea where the data are going to be served from. The backend system generates URNs like "" What I think I want to do is on the fuseki server be able to configure "urn:foo:bar" as a place holder

[jira] [Commented] (JENA-1430) Quad loading for in-memory assemblers

[ https://issues.apache.org/jira/browse/JENA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262881#comment-16262881 ] ASF GitHub Bot commented on JENA-1430: -- Github user ajs6f commented on the issue:

[GitHub] jena issue #314: JENA-1430

Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/314 @afs What do you think of that? It's clearer, I think, along the lines [you suggested](https://github.com/apache/jena/pull/314#discussion_r152289270). ---

Re: CMS diff: Jena Full Text Search

Hi Andy and Osma, I posted JENA-1426 since the “improve this page” facility didn’t seem to offer any way to add a commit message or more extensive explanation of the reasons for the proposed edits and they were somewhat extensive. So raising an

Re: CMS diff: Jena Full Text Search

How is this related to JENA-1426? Andy On 21/11/17 14:48, Osma Suominen wrote: ajs6f kirjoitti 20.11.2017 klo 18:36: Osma (or anyone else who knows text indexing better than do I, which wouldn't take much)-- could you review this? It's got some great useful detail about how the indexing

[jira] [Commented] (JENA-1384) Make canonical literals lowercase language tags.

[ https://issues.apache.org/jira/browse/JENA-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262293#comment-16262293 ] ASF GitHub Bot commented on JENA-1384: -- Github user afs commented on a diff in the pull request:

[GitHub] jena pull request #308: JENA-1384: Canonical literals: lexical form and lang...

Github user afs commented on a diff in the pull request: https://github.com/apache/jena/pull/308#discussion_r152531097 --- Diff: jena-arq/src/main/java/org/apache/jena/riot/process/normalize/CanonicalizeLiteral.java --- @@ -73,6 +76,36 @@ public Node apply(Node node) {

[jira] [Commented] (JENA-1384) Make canonical literals lowercase language tags.

[ https://issues.apache.org/jira/browse/JENA-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262248#comment-16262248 ] ASF GitHub Bot commented on JENA-1384: -- Github user rvesse commented on a diff in the pull request:

[GitHub] jena pull request #308: JENA-1384: Canonical literals: lexical form and lang...

Github user rvesse commented on a diff in the pull request: https://github.com/apache/jena/pull/308#discussion_r152523288 --- Diff: jena-arq/src/main/java/org/apache/jena/riot/process/normalize/CanonicalizeLiteral.java --- @@ -73,6 +76,36 @@ public Node apply(Node node) {

[GitHub] jena issue #299: Turtle Star

Github user hartig commented on the issue: https://github.com/apache/jena/pull/299 Thanks Andy! I agree with what you write. Do you think there is a chance for such a separate maven module to become part of the official family of Apache Jena maven modules? ---