Brad,
Thanks for the report. Could you raise a JIRA ticket please? It's a bug.
The BaseInfGraph.clear should be inside a transaction and somehow that's
getting missed.
Other updates work (e.g. insert data) so it's specific to "clear"
somehow. It was supposed to be fixed at JENA-1492 which is
bif:contains uses a Virtuoso full text index.
SPARQL's CONTAINS looks for exact substring.
(it is the same as XQuery/XPath fn:contains)
https://www.w3.org/TR/sparql11-query/#func-contains
FILTER(CONTAINS((LCASE(?something), "word")))
or a regex
Andy
On 29/11/2018 17:51, Dan Davis wrote:
I have a Query Execution Service that returns a QueryExecution that is
within another triple-store, and that other triple store supports some
functions my other graphs do not. Specifically, it is virtuoso, and
supports bif:lower and bif:contains. My intuition is that I need to write
filter funct
I can't speak precisely to your error, but have you tried DROP GRAPH [1]? Might
be a useful workaround for the moment.
ajs6f
[1] https://www.w3.org/TR/sparql11-update/#drop
> On Nov 29, 2018, at 10:07 AM, Brad Stallion
> wrote:
>
> Hi All,
> I'm using Fuseki 3.9.0.
> I have a TDB-backed gra
I've used xslt transformations in the past and was impressed by the speed
and its ability to transform large documents. But in the end I usually
reverted back to custom transformations (in code) on the production machine
due to quirks in the incoming or outgoing data. Still a generic JSON to RDF
te
Ok so I will give it a spin over the weekend to see how it performs and if
it gets me what I want
On Thu 29 Nov 2018 at 15:54, ajs6f wrote:
> I'm not Martynas, so you didn't misname anyone that I saw.
>
> JSON-LD can certainly help with this: any time you have JSON, and you wish
> it were RDF, J
Sure, but you get that if you produce RDF/XML or TriX. I've tried that
and transformed JSON directly into TriX with Saxon.
On Thu, Nov 29, 2018 at 4:41 PM Marco Neumann wrote:
>
> thanks for the link Martynas, one still has to go to rdf from xml. I find
> the data assembler in jena/d2rq more conve
I'm not Martynas, so you didn't misname anyone that I saw.
JSON-LD can certainly help with this: any time you have JSON, and you wish it
were RDF, JSON-LD is there for you! Whether it's the best choice, only you can
say. Keep in mind that JSON-LD contexts can take JSON and create triples (or
ev
thanks for the link Martynas, one still has to go to rdf from xml. I find
the data assembler in jena/d2rq more convenient but am open to new ideas.
btw I never quite know who is posting on ajs6f hence the misnomer
On Thu 29. Nov 2018 at 14:29, Martynas Jusevičius
wrote:
> Marco,
>
> FYI XSLT 3
Hi All,I'm using Fuseki 3.9.0. I have a TDB-backed graph. Configuration file is
attached.Everything works, including inference on triples added
incrementally.I'd like to reset the TDB content.
The SPARQL directive "DELETE { ?s ?p ?o } WHERE { ?s ?p ?o }" is too slow.
The directive "CLEAR ALL", on
Marco,
FYI XSLT 3.0 supports JSON transformations: https://www.w3.org/TR/xslt-30/#json
Martynas
On Thu, Nov 29, 2018 at 2:27 PM Marco Neumann wrote:
>
> good to know that we are on the same page here Adam. With regards to json
> let's limit the scope of the discussion here to the Jena project fo
good to know that we are on the same page here Adam. With regards to json
let's limit the scope of the discussion here to the Jena project for now. I
am not looking at an alternative to JSON-LD, correct my if I am wrong but
as far as my limited understanding of JSON-LD goes it is a way to
store/ser
I agree _very heartily_ with the caution that Andy and Marco are expressing.
I've been following the conversation on semantic-...@w3.org and I have yet to
hear anything that seems very useful or practical to me.
That having been said, and speaking very much as a member of W3C's JSON-LD
Working
I agree Andy, there is no need to rush things here and break the API. Maybe
we could provide an in memory model for "Generalized RDF" as sandbox for
people to play with. But what I'd like to see are more bridges to the json
community as it has become the defacto lingua franca for data exchange on
t
Many thanks for your patience, these are very useful details.
> Can you provide *repeatable examples*? Ideally, not using YASQE.
-- unfortunately not... but if I have the same problem, I'll try to
configure Jetty and/or Jena error handling (as Marco suggested) to get
some more information if I
On 29/11/2018 08:03, Vincent Ventresque wrote:
Thanks a lot for all these elements Andy.
However, I still don't understand /why the parser works most of the time
and fails sometimes/.
Can you provide repeatable examples? Ideally, not using YASQE.
(BTW YASQE retains internal state like last
Hello Marco,
Thanks for the link, I'll have a look.
Also opened a few javascript files this morning : I wonder if the
problem could be linked to 'sparql.js' or 'codemirror.js' ( in
webapp/js/lib/ and webapp/js/lib/mode/ )
Le 29/11/2018 à 12:04, Marco Neumann a écrit :
one seems to be t
one seems to be the jetty error + jena error message and the other is the
specific jena 'lexical error' message. keep in mind fuseki uses jetty to
serve http requests in the standard configuration.
since jena is open source you can inspect the error handle in more detail
yourself, show more detai
Thanks a lot for all these elements Andy.
However, I still don't understand /why the parser works most of the time
and fails sometimes/. Any clue about what's happening? I find it very
strange that re-typing the same query can solve the problem (I don't
change anything but the query string : t
19 matches
Mail list logo
