Re: Problem with MAX when no result expected

Hi, You answer just realized I committed an error while typing the question. I have just sent a good one. But from the answer below you confirm that the current Jena output is the desired behaviour. I still don't know why the aggregate for MAX or MIN returns one row in result. I will have to

Re: Problem with MAX when no result expected

Hi, Forget the last one. I've just realized again I included a mistake this is the good one (I hope ;)) # Case 1) select ?id ?value ?latitude ?longitude where { .. } -- { "head": { "vars": [ "id", "value", "latitude", "longitude" ] },

Re: Problem with MAX when no result expected

If there is an aggregation, you will get one row. SELECT (MAX(?x) AS ?M) { FILTER(false) } ==> (sparql --query Q.rq) - | M | = | | - which is: (sparql --query Q.rq --results json) { "head": { "vars": [ "M" ] } , "results": { "bindings": [ { } ] } }

Re: Problem with MAX when no result expected

Hi Andy, Now I understand the misunderstanding between you and me. The responses I included in my original mail where wrong :( Please accept my apologizes. These are the right query/responses: # Case 1) select ?id (MAX(?ti) as ?time) ?value ?latitude ?longitude where { .. }-- {

Re: loading many small rdf/xml files

RDF/XML was the first RDF syntax. On Sat, 7 Oct 2017 at 20.27, Andrew U. Frank wrote: > thank you again! > > rereading your answers, i checked on the utilities xargs and riot, which > i had not ever used before. then i understood your approach (thank you > for

Re: loading many small rdf/xml files

thank you again! rereading your answers, i checked on the utilities xargs and riot, which i had not ever used before. then i understood your approach (thank you for putting the comand line in!) and followed your approach. it indeed produces lots of warnings and i had also a hard error in the

Re: loading many small rdf/xml files

On 07/10/17 17:06, Andrew U. Frank wrote: thank you - your link indicates why the solution with calling s-put for each individual file is so slow. practically - i will just wait the 10 hours and then extract the triples from the store. I admire your patience! I've just downloaded the

Why RDF/XML? Was: loading many small rdf/xml files

Simply because it is both XML and RDF. There is an enormous installed base of expertise and tooling for XML. It's often worth taking advantage of, even if it is technically unperformant on a case-by-case basis. If you have to process RDF and you already know a great deal about XML and use

Re: loading many small rdf/xml files

thank you - your link indicates why the solution with calling s-put for each individual file is so slow. practically - i will just wait the 10 hours and then extract the triples from the store. can you understand, why somebody would select this format? what is the advantage? andrew On

Re: Change DESCRIBE @context

Try to get it working locally - read and write a file to get it in th format you want. https://jena.apache.org/documentation/io/rdf-output.html#json-ld and the example: https://github.com/apache/jena/blob/master/jena-arq/src-examples/arq/examples/riot/ExJsonLD.java It is a long path

Re: Change DESCRIBE @context

Not talking about proposing Fuseki a context/frame. I'm OK with a auto-generated context. But Fuseki is creating a new prefix for every URI (see previous email). Rather than creating 100s of new prefixes, it would be more useful if Fuseki would reuse the same PREFIXes that were already

Re: loading many small rdf/xml files

The continual round trip times are more than the time it takes Fuseki to perform an update. On 07/10/17 15:42, aj...@apache.org wrote: Couple of possibilities: 1) Get something other than RDF/XML from Gutenberg. I don't mean that to sound flippant. They may very well maintain some other

Re: loading many small rdf/xml files

Hello Andrew, if I understand this correctly, I think I stumbled on the same problem before. Concatenating XML files will not work indeed. My solution was to convert all XML files to N-Triples, then concatenate all those triples into a single file, and finally load only this file. Ultimately,

Re: Change DESCRIBE @context

There's no way (as far as I know) right now to propose a particular context (or other profile information) via HTTP when accepting JSON-LD: https://github.com/json-ld/json-ld.org/issues/491 Or is your expectation that Jena would somehow figure out to do what you want unhinted? If you can

Re: loading many small rdf/xml files

Couple of possibilities: 1) Get something other than RDF/XML from Gutenberg. I don't mean that to sound flippant. They may very well maintain some other representation (NTriples, Turtle, etc) for their own use and they might be willing to share it. It's worth an email. Then use SOH. 2A)

Re: loading many small rdf/xml files

Run a script to convert them to N-Triples and then another to concatenate the files? On Sat, Oct 7, 2017 at 4:17 PM, Andrew U. Frank wrote: > i have to load the Gutenberg projects catalog in rdf/xml format. this is a > collection of about 50,000 files, each

Re: Change DESCRIBE @context

The problem is that Fuseki (when I select JSON-LD output format) creates a @context with as many properties as there are URIs. For example "@context" : { "name" : { "@id" : "example.org/vocab/name", "@type" : ... }, "surname" : { "@id" :

loading many small rdf/xml files

i have to load the Gutenberg projects catalog in rdf/xml format. this is a collection of about 50,000 files, each containing a single record as attached. if i try to concatenate these files into a single one the result is not legal rdf/xml - there are xml doc headers:

Re: Change DESCRIBE @context

The result Model from DESCRIBE has the prefixes of the data and the query. There can be multiple prefixes for the same URI. How that gets processed by JSON-LD is another matter and I don't know the details. Andy On 07/10/17 10:27, Laura Morales wrote: When I query Fuseki like this

Change DESCRIBE @context

When I query Fuseki like this "DESCRIBE <> FROM <>" and return a JSON-LD, it looks like the "@context" is generated automatically and it ignores any "PREFIX" declaration. For example if I have "PREFIX foo: " it will create the property "Person" instead of