Wimmics / corese

Software platform implementing and extending the standards of the Semantic Web.
https://project.inria.fr/corese/
Other
103 stars 29 forks source link

[Feature request] Federated ASK/EXISTS queries sent to remote server #147

Open MaillPierre opened 1 year ago

MaillPierre commented 1 year ago

Is your feature request related to a problem? Please describe. When I send a federated ASK query such as ASK { SERVICE { ?s ?p ?o } }, the Corese server sends the following query to the server:

select *  where {   ?s ?p ?o . } limit 1000

Describe the solution you'd like I would like to know if there is a setting to put the limit of the sent query to 1 or if federated ASK queries could be sent to the remote server as ASK sub-queries instead of a SELECT one.

Describe alternatives you've considered I can use the service extension feature, but it requires doing a lot of parsing/rewriting work on every query to automate the querying.

ocorby commented 1 year ago

HiYou may try this :Ask { service {   select * where { s p o } limit 1 } }RegardsOlivier -------- Message d'origine --------De : Pierre Maillot @.> Date : 11/10/2023 11:37 (GMT+01:00) À : Wimmics/corese @.> Cc : Subscribed @.**> Objet : [Wimmics/corese] Federated ASK/EXISTS queries sent to remote server (Issue #147) Is your feature request related to a problem? Please describe. When I send a federated ASK query such as ASK { SERVICE { ?s ?p ?o } }, the Corese server sends the following query to the server: select where { ?s ?p ?o . } limit 1000 Describe the solution you'd like I would like to know if there is a setting to put the limit of the sent query to 1 or if federated ASK queries could be sent to the remote server as ASK sub-queries instead of a SELECT one. Describe alternatives you've considered I can use the service extension feature, but it requires doing a lot of parsing/rewriting work on every query to automate the querying.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>