Hi Andy

The setup is ./fuseki-server --update --loc=./RDFDATA /ds

After having selected the /ds dataset in the web console the query could
retrieve the RDF triples. THANK YOU!!!

Regards
Fabio

PS: Interesting semantics of FROM - retrieving RDF from that URL. In my
case the graph was just a label.


Am 14.2.15 um 13:22 schrieb Andy Seaborne:
>> ./s-put http://localhost:3030/ds/data http://semweb.ch/SEMWEB
>> /Users/fabio/Documents/DATA/thesauri/pp_project_semweb.ttl
>
> The graph is loaded with name http://semweb.ch/SEMWEB
>
> On 13/02/15 22:47, Fabio Ricci wrote:
>> Hi Andy - thank you for answer
>>
>> my point is that
>>
>> ./s-get http://localhost:3030/ds/data http://semweb.ch/SEMWEB
>> ./s-query --service http://localhost:3030/ds/query 'SELECT * from
>> <http://semweb.ch/SEMWEB> {?s ?p ?o}'
>
> For which setup --mem or --loc?
>
>>
>> is functioning at command line level while
>>
>> SELECT * from <http://semweb.ch/SEMWEB> {?s ?p ?o}
>> and
>> SELECT * {GRAPH <http://semweb.ch/SEMWEB> {?s ?p ?o}}
>>
>> are ***NOT*** functioning inside the SPARQLer - General purpose
>> processor
>>
>> with error "Error 400: No dataset description in protocol request or in
>> the query string"
>
> The general purpose processor does not have any data behind it.
>
> FROM will try to do a HTTP GET on http://semweb.ch/SEMWEB, which will
> fail with a 404.
>
> """
> Error 400: Failed to load URL http://semweb.ch/SEMWEB
> """
>
> The GRAPH version will have no data to query.
>
> It is not connected to the data you loaded in /ds.
>
> To query your loaded data in /ds go:
>
> "Control panel" -> pick /ds -> use the query form.
>
>
>
>>
>> Although same repository ...
>>
>>
>> Furthermore
>> ./s-get http://localhost:3030/ds/data http://semweb.ch/SEMWEB ./s-query
>> --service http://localhost:3030/ds/query 'SELECT * { GRAPH
>> <http://semweb.ch/SEMWEB> {?s ?p ?o}}'
>> gives an error "`cmd_soh': invalid option: --service
>> (OptionParser::InvalidOption)
>>      from ./s-get:703:in `<main>'"
>
> Different and unrelated - you have all the commands one line so the
> s-get is seeing the --service from s-query.
>
>> So we still have the issue...
>>
>> Any ideas ?
>
>     Andy
>
>>
>> Thank you in advance :)
>>
>> Kind regards / Meilleures salutations / Freundliche Grüsse
>> /Fabio Ricci/
>> semweb        
>>
>>     Semantic Web Technologies · Records Management
>> Software systems · ICT coaching · ICT Projects leading    
>>
>>     
>>
>> *www.semweb.ch* <http://semweb.ch>
>>
>>     
>>
>>     
>>
>> Weinmanngasse 26
>> CH-8700 Küsnacht ZH (Switzerland)
>>
>>     
>>
>>     
>>
>> /Tel./
>>
>>     
>>
>> +41 (076) 5281961
>> +39 (389) 0681334
>>
>> /Skype:/
>>
>>     
>>
>> *semweb-llc* <http://myskype.info/semweb-llc>
>>
>> *Confidentiality Warning*: This message and any attachments are intended
>> only for the use of the intended recipients, are confidential and maybe
>> privileged. If you are not the intended recipient, you are hereby
>> notified that any review, retransmission, conversion to hard copy,
>> copying, circulation or other use of this message and any attachments is
>> strictly prohibited. If you are not the intended recipient, please
>> notify the sender immediately by return email, and delete this message
>> and any attachments from your system. Thank you.
>>
>> Am 10.2.15 um 14:37 schrieb Andy Seaborne:
>>> On 09/02/15 21:47, Fabio Ricci wrote:
>>>> Dear Jena community
>>>>
>>>> I am starting to use the Jena framework but before I am
>>>> installing/using
>>>> the fuseki RDF server.
>>>> I could start and run it properly but with some peculiarities:
>>>>
>>>> 1. When started with the mem option (in memory) and some RDF data is
>>>> loaded into a graph (no default graph) the only command that runs well
>>>> is the s-get with the graph again: All the RDF statements are
>>>> returned.
>>>> The s-query --service is not running - nothing returned. And in the
>>>> webconsole http://localhost:3030/sparql.html none of my graphs are
>>>> loadable, neither per from <graph> nor by the apposite field "Target
>>>> Graph URI". Why is this so? Is there a bug in the fuseki server?
>>>> Here my operations:
>>>>
>>>> ./s-put http://localhost:3030/ds/data http://semweb.ch/SEMWEB
>>>> /Users/fabio/Documents/DATA/thesauri/pp_project_semweb.ttl
>>>
>>> That puts data into named graph http://semweb.ch/SEMWEB.
>>>
>>>> ./s-get http://localhost:3030/ds/data http://semweb.ch/SEMWEB
>>>> ./s-query --service http://localhost:3030/ds/query 'SELECT * from
>>>> <http://semweb.ch/SEMWEB> {?s ?p ?o}'
>>>
>>> To access a named graph, use GRAPH.  FROM on a general dataset tries
>>> to load it from the web.  Did the fuskei log say anything about not
>>> being able to load it?
>>>
>>> Try:
>>>
>>> SELECT * { GRAPH <http://semweb.ch/SEMWEB> { ?s ?p ?o} }'
>>>
>>>> 2. I restarted the fuseki server with "./fuseki-server --update
>>>> --loc=./RDFDATA /ds" and noticed that all three of the commands ran
>>>> well:
>>>> ./s-put http://localhost:3030/ds/data http://semweb.ch/SEMWEB
>>>> /Users/fabio/Documents/DATA/thesauri/pp_project_semweb.ttl
>>>> ./s-get http://localhost:3030/ds/data http://semweb.ch/SEMWEB
>>>> ./s-query --service http://localhost:3030/ds/query 'SELECT * from
>>>> <http://semweb.ch/SEMWEB> {?s ?p ?o}'
>>>
>>> For TDB, FROM picks out a graph from the dataset, not the whole web.
>>>
>>> TDB can't load from the web for a temporary dataset just for the query
>>> so the mechanism is overloaded.  See the thread with Willie Minor.
>>>
>>> Again. GRAPH is the way to access the named graph.  Or
>>>
>>> --set tdb:unionDefaultGraph=true
>>>
>>> to make the default graph for query the computed union of all the
>>> named graphs.
>>>
>>>>
>>>> still the web console "SPARQLer" "could not load" the graph
>>>> "http://semweb.ch/SEMWEB";
>>>
>>> I'd expect hat from the in-memory dataset but not with TDB. Testing
>>> here, I don't see that with --loc -- I see some query results.
>>>
>>>     Andy
>>>
>>>
>>>
>>>>
>>>> What is wrong in what I am doing?
>>>>
>>>> Thank you for your advice
>>>>
>>>> Regards
>>>> Fabio
>>>>
>>>>
>>>>
>>>>
>>>
>>
>

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to