Re: Definition of SPARQL variable pre-binding

Here's a slightly relevant discussion about how to support something like pre-bound variables / parametrized queries in YASQE, a graphical SPARQL editor component in the YASGUI suite (and used by Fuseki among others): https://github.com/YASGUI/YASQE/issues/24 I'm not sure I understand all the

[jira] [Commented] (JENA-960) The construction of jena-cmd

[ https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588088#comment-14588088 ] Rob Vesse commented on JENA-960: Well speaking for Airline which I've spent a lot of time on

[GitHub] jena pull request: Lucene index synchro on triple deletion (jena-t...

Github user amiara514 commented on the pull request: https://github.com/apache/jena/pull/53#issuecomment-112409094 Yes absolutly, you can merge it... before another conflict ;-) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

Re: [GSoC 2015 - JENA-491] Refactoring Template

On 16/06/15 12:19, Andy Seaborne wrote: On 15/06/15 11:36, Qihong Lin wrote: Hi, Please check my last 3 commits[1], related to refactoring Template. master.jj is modified accordingly, *without* implementing the new CONSTRUCT query function for quad. Just to make sure: the maven build test for

[jira] [Commented] (JENA-960) The construction of jena-cmd

[ https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588059#comment-14588059 ] A. Soroka commented on JENA-960: My hope is to at least replace a good portion of the CLI

Re: [GSoC 2015 - JENA-491] JavaCC with master.jj

On 16/06/15 09:06, Qihong Lin wrote: Hi, Thanks! I just marked GRAPH mandatory, and it worked without producing the warnings. I'll look into the details later. By the way, if the new parser is ready, how to test it? I mean, where to drop the unit test code and the query strings to be tested?

[jira] [Commented] (JENA-960) The construction of jena-cmd

[ https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588160#comment-14588160 ] A. Soroka commented on JENA-960: There's not a dependency, but obviously, asking for a new

[jira] [Commented] (JENA-959) riot: gzip output option

[ https://issues.apache.org/jira/browse/JENA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588216#comment-14588216 ] Andy Seaborne commented on JENA-959: It was background on how things are as the

[jira] [Commented] (JENA-961) Move arq.cmd.* to jena-base's jena.cmd

[ https://issues.apache.org/jira/browse/JENA-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588238#comment-14588238 ] A. Soroka commented on JENA-961: I'm taking a swing at this ticket. Move arq.cmd.* to

[jira] [Commented] (JENA-959) riot: gzip output option

[ https://issues.apache.org/jira/browse/JENA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588219#comment-14588219 ] Andy Seaborne commented on JENA-959: Would it be better to assume a compositional model

[jira] [Commented] (JENA-959) riot: gzip output option

[ https://issues.apache.org/jira/browse/JENA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588245#comment-14588245 ] A. Soroka commented on JENA-959: I guess the question then is whether [~stain]'s use case is

[jira] [Commented] (JENA-959) riot: gzip output option

[ https://issues.apache.org/jira/browse/JENA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588151#comment-14588151 ] Andy Seaborne commented on JENA-959: To pipe a gziped stream: {{-}} is the standard

[jira] [Comment Edited] (JENA-960) The construction of jena-cmd

[ https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588160#comment-14588160 ] A. Soroka edited comment on JENA-960 at 6/16/15 3:22 PM: - There's

[jira] [Commented] (JENA-961) Move arq.cmd.* to jena-base's jena.cmd

[ https://issues.apache.org/jira/browse/JENA-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588485#comment-14588485 ] ASF GitHub Bot commented on JENA-961: - GitHub user ajs6f opened a pull request:

[jira] [Commented] (JENA-961) Move arq.cmd.* to jena-base's jena.cmd

[ https://issues.apache.org/jira/browse/JENA-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588486#comment-14588486 ] A. Soroka commented on JENA-961: https://github.com/apache/jena/pull/77 Move arq.cmd.* to

[GitHub] jena pull request: Move arq.cmd.* to jena-base's jena.cmd

GitHub user ajs6f opened a pull request: https://github.com/apache/jena/pull/77 Move arq.cmd.* to jena-base's jena.cmd https://issues.apache.org/jira/browse/JENA-961 This is a multi-module PR, but I could find no other way to do it: since several Jena modules depend on

[jira] [Created] (JENA-966) LazyIterator

Claude Warren created JENA-966: -- Summary: LazyIterator Key: JENA-966 URL: https://issues.apache.org/jira/browse/JENA-966 Project: Apache Jena Issue Type: Bug Components: Core

[GitHub] jena pull request: Lucene index synchro on triple deletion (jena-t...

Github user afs commented on the pull request: https://github.com/apache/jena/pull/53#issuecomment-112564393 Ack! --- 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

[GitHub] jena pull request: Move arq.cmd.* to jena-base's jena.cmd

Github user afs commented on the pull request: https://github.com/apache/jena/pull/77#issuecomment-112548845 Moving into jena-base is probably the best first step. It separates it from gathering all the commands which may well not be good idea anyway, or at least, a pointless

Re: Definition of SPARQL variable pre-binding

On 6/16/2015 22:03, Osma Suominen wrote: Here's a slightly relevant discussion about how to support something like pre-bound variables / parametrized queries in YASQE, a graphical SPARQL editor component in the YASGUI suite (and used by Fuseki among others):

[jira] [Created] (JENA-964) remove home argument from fuseki startup script

Yang Yuanzhe created JENA-964: - Summary: remove home argument from fuseki startup script Key: JENA-964 URL: https://issues.apache.org/jira/browse/JENA-964 Project: Apache Jena Issue Type: Bug

Re: [GSoC 2015 - JENA-491] JavaCC with master.jj

Hi, Thanks! I just marked GRAPH mandatory, and it worked without producing the warnings. I'll look into the details later. By the way, if the new parser is ready, how to test it? I mean, where to drop the unit test code and the query strings to be tested? I'm confused with

Re: Definition of SPARQL variable pre-binding

Thanks, Andy. On 6/16/15 6:03 PM, Andy Seaborne wrote: On 16/06/15 04:20, Holger Knublauch wrote: Hi, (this question is motivated by the ongoing Data Shapes WG, but I don't speak on their behalf). Ptr? http://w3c.github.io/data-shapes/shacl/ esp

Re: Trouble Building Under Eclipse

Just got back from holiday Have gone through the rest of the thread on this and it seems like just having jena-base closed in Eclipse does resolve the issue for me Rob On 05/06/2015 16:04, Andy Seaborne a...@apache.org wrote: Rob, Did you get this sorted? Any clues? Andy On 04/06/15

[jira] [Commented] (JENA-965) Threading Issue in OntDocumentManager.loadImports

[ https://issues.apache.org/jira/browse/JENA-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587845#comment-14587845 ] Andy Seaborne commented on JENA-965: Failed to reproduce on Ubuntu (Jena 2.13.0 and Jena

[jira] [Created] (JENA-965) Threading Issue in OntDocumentManager.loadImports

Andy Seaborne created JENA-965: -- Summary: Threading Issue in OntDocumentManager.loadImports Key: JENA-965 URL: https://issues.apache.org/jira/browse/JENA-965 Project: Apache Jena Issue Type:

Re: Definition of SPARQL variable pre-binding

On 16/06/15 04:20, Holger Knublauch wrote: Hi, (this question is motivated by the ongoing Data Shapes WG, but I don't speak on their behalf). Ptr? Jena and other APIs such as Sesame support the concept of pre-binding variables prior to SPARQL execution, using

[jira] [Commented] (JENA-960) The construction of jena-cmd

[ https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587739#comment-14587739 ] Rob Vesse commented on JENA-960: In the long term is the thought that we might move off to

Re: Definition of SPARQL variable pre-binding

On 16/06/15 09:33, Holger Knublauch wrote: Thanks, Andy. On 6/16/15 6:03 PM, Andy Seaborne wrote: On 16/06/15 04:20, Holger Knublauch wrote: Hi, (this question is motivated by the ongoing Data Shapes WG, but I don't speak on their behalf). Ptr? http://w3c.github.io/data-shapes/shacl/ esp

[jira] [Commented] (JENA-960) The construction of jena-cmd

[ https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587807#comment-14587807 ] Andy Seaborne commented on JENA-960: Unclear. jena command line processing isn't just

[jira] [Resolved] (JENA-964) remove home argument from fuseki startup script

[ https://issues.apache.org/jira/browse/JENA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-964. Resolution: Fixed Fix Version/s: Fuseki 2.0.1 Thanks for that. Now fixed in the codebase.

[jira] [Assigned] (JENA-964) remove home argument from fuseki startup script

[ https://issues.apache.org/jira/browse/JENA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne reassigned JENA-964: -- Assignee: Andy Seaborne remove home argument from fuseki startup script

[jira] [Updated] (JENA-964) remove home argument from fuseki startup script

[ https://issues.apache.org/jira/browse/JENA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-964: --- Priority: Minor (was: Major) remove home argument from fuseki startup script

[jira] [Updated] (JENA-964) remove home argument from fuseki startup script

[ https://issues.apache.org/jira/browse/JENA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-964: --- Affects Version/s: (was: Fuseki 2.0.1) remove home argument from fuseki startup script

[jira] [Updated] (JENA-964) remove home argument from fuseki startup script

[ https://issues.apache.org/jira/browse/JENA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-964: --- Description: Hi Andy, How is everything going? Today I tried to run fuseki as a service with the

[jira] [Commented] (JENA-964) remove home argument from fuseki startup script

[ https://issues.apache.org/jira/browse/JENA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587815#comment-14587815 ] ASF subversion and git services commented on JENA-964: -- Commit

Re: [GSoC 2015 - JENA-491] Refactoring Template

On 15/06/15 11:36, Qihong Lin wrote: Hi, Please check my last 3 commits[1], related to refactoring Template. master.jj is modified accordingly, *without* implementing the new CONSTRUCT query function for quad. Just to make sure: the maven build test for this jena-arq module is successful.