SPARQL 1.2 Extended Protocol

Hi

I'd like to see in future specifications :

- A minimal protocol
A minimal protocol MUST be defined for SPARQL services to facilitate SPARQL
clients development [2].

- Extended the protocol for errors
Developers have difficulty debugging SPARQL queries because the error
messages are not uniform enough  and SPARQL editors  are not able to catch
correctly these messages.
And most importantly, error messages disappear between SPARQL services in
federated queries. The SPARQL services MUST forward the error messages of
sub-queries.

- Extended the protocol in order to building IRIs' autocompletion, via
keywords/text research.
This autocompletion of IRIs does not presuppose any prior knowledge of the
SPARQL service and the ontologies it contains. The user writes keywords, in
the language of his choice, to obtain a list of suggestions for relative
IRIs. It is then enough to choose one so that the SPARQL editor can insert
it in the current request. This type of feature is requested by all kinds
of users.
For the moment, I use the Wikidata API to build the demonstrator of this
autocompletion  but ideally, all SPARQL services should offer this research
of its IRIs when it's possible [1].

- Protocol to access the logs of SPARQL queries
To develop new autocompletions for SPARQL queries [1], it is necessary to
allow the collection of users queries. Via the protocol, the user
should request that his query be public or private and the SPARQL service
is able to share these queries public without transformation (ie. with
variables names original and comments).

[1] Designing scientific SPARQL queries using autocompletion by snippets
<https://scholar.google.fr/scholar?oi=bibs&cluster=5846700921540854881&btnI=1&hl=fr>
K Rafes, S Abiteboul, S Cohen-Boulakia, B Rance - 2018 IEEE 14th
International Conference on e-Science, 2018
[2] (chapter 5) Le Linked Data à l'université: la plateforme LinkedWiki
<https://tel.archives-ouvertes.fr/tel-02003672/> (French) K Rafes - 2019

Thanks
Bye
Karima