[GitHub] jena issue #246: Generic text analyzers

Github user xristy commented on the issue: https://github.com/apache/jena/pull/246 I've resolved the conflict in TextVocab.java and add further updates to the text-querty.mdtext a couple of weeks ago. What are the next steps that I need to take to get this PR accepted? --- If your p

[jira] [Commented] (JENA-1364) Jena-core has dependency on vulnerable Xerces version

[ https://issues.apache.org/jira/browse/JENA-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064959#comment-16064959 ] Andy Seaborne commented on JENA-1364: - As a workaround, here are two ways to switch to

[jira] [Resolved] (JENA-1367) Property function apf:strSplit is not well-behaved

[ https://issues.apache.org/jira/browse/JENA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1367. - Resolution: Done Assignee: Andy Seaborne Fix Version/s: Jena 3.4.0 > Property funct

[jira] [Commented] (JENA-1367) Property function apf:strSplit is not well-behaved

[ https://issues.apache.org/jira/browse/JENA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064951#comment-16064951 ] ASF subversion and git services commented on JENA-1367: --- Commit 05738

[jira] [Commented] (JENA-1367) Property function apf:strSplit is not well-behaved

[ https://issues.apache.org/jira/browse/JENA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064952#comment-16064952 ] ASF subversion and git services commented on JENA-1367: --- Commit c2a8a

[jira] [Commented] (JENA-1367) Property function apf:strSplit is not well-behaved

[ https://issues.apache.org/jira/browse/JENA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064949#comment-16064949 ] ASF subversion and git services commented on JENA-1367: --- Commit eae24

[jira] [Commented] (JENA-1367) Property function apf:strSplit is not well-behaved

[ https://issues.apache.org/jira/browse/JENA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064950#comment-16064950 ] ASF subversion and git services commented on JENA-1367: --- Commit 11234

[jira] [Commented] (JENA-1367) Property function apf:strSplit is not well-behaved

[ https://issues.apache.org/jira/browse/JENA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064948#comment-16064948 ] ASF subversion and git services commented on JENA-1367: --- Commit 305a5

[jira] [Commented] (JENA-1367) Property function apf:strSplit is not well-behaved

[ https://issues.apache.org/jira/browse/JENA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064953#comment-16064953 ] ASF GitHub Bot commented on JENA-1367: -- Github user asfgit closed the pull request at:

[GitHub] jena pull request #266: JENA-1367: Improve apf:strSplit corner cases

Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/266 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enable

Re: path statements in queries

On 27/06/17 10:54, Claude Warren wrote: I know that the SPARQL recommendation states that path elements must be URIs (https://www.w3.org/TR/sparql11-property-paths/#id41857) but sine the path may be expanded as noted in the recommendation so that This optimization already exists in ARQ. Tran

path statements in queries

I know that the SPARQL recommendation states that path elements must be URIs (https://www.w3.org/TR/sparql11-property-paths/#id41857) but sine the path may be expanded as noted in the recommendation so that {noformat} { ?x foaf:mbox . ?x foaf:kn

Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)

from bui...@apache.org Recap: In just over 2 weeks, downtime for a migration AND upgrade is planned. Sunday, 16 July 2017 at 00:00:00 Forwarded Message Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation) Date: Tue, 27 Jun 2017 17:03:13 +

Re: Unexpected difference in query results

After further investigation the issue is in the query builder and how it handles "_:b0" while createing nodes. I'll dig further to but there is no issue with fuseki or RDFConnection. On Mon, Jun 26, 2017 at 5:33 PM, Claude Warren wrote: > Fuseki 2.5.0 > Jena 3.3.0 > > I have a graph and a query