Kingsley Idehen

> Feature requests is out of scope of 0.7. They belong in the solid/specification repository. > > New issues can only be about erratas to the 0.7 spec. Yes, and...

> > no "new features" goal is achieved by not including any "new feature" option in the template that @melvincarvalho is putting together. > > One alternatively could provide a...

> @kidehen Yes, but _if_ someone is already looking for a way to submit a feature request he or she will perhaps simply submit a "bug" instead. > > Anyway,...

Trying to deduce what's happening from SPARQL query text and results tables is challenging. Thus, do you have any of the following: 1. A live SPARQL endpoint? 2. A little...

On 8/14/14 6:08 AM, jakubklimek wrote: > We use Virtuoso in our tools UnifiedViews http://unifiedeviews.eu > (part of LOD2 stack) and Payola http://live.payola.cz as a data > source. These are...

On 8/15/14 6:53 AM, jakubklimek wrote: > Thanks for the explanation, that finally brings some light into this. > The question is of course whether the construct query could not...

On 8/15/14 10:29 AM, Alexey Zakhlestin wrote: >> What is the issue? > > @kidehen https://github.com/kidehen did you look at github page? the > issue is this error: `Virtuoso 22023...

On 8/15/14 11:36 AM, jakubklimek wrote: > Nevertheless, it is the case. I execute the query using `wget`, > accessing Jena's SPARQL HTTP endpoint (Fuseki) and the solution is >...

On 8/15/14 11:48 AM, jakubklimek wrote: >> If you have a SPARQL Protocol URL comprised of a CONSTRUCT that results >> in output, of the magnitude requested, that works, then...

> Thanks for the feedback! Not sure what you mean with inverted subqueries? > > I've tried performing the query starting with the weather observations as the innermost subquery and...