W3C home > Mailing lists > Public > public-sparql-dev@w3.org > July to September 2018

Re: Extending SPARQL XML result format

From: Karima Rafes <karima.rafes@gmail.com>
Date: Wed, 11 Jul 2018 16:09:00 +0200
Message-ID: <CALsrFgNSVY9uiW+Jr44PF=qVwC9v=J6WoreoDx8K0xH4rqu8+w@mail.gmail.com>
To: Bijan Parsia <bijan.parsia@manchester.ac.uk>
Cc: Thomas Francart <thomas.francart@sparna.fr>, "public-sparql-dev@w3.org" <public-sparql-dev@w3.org>
A need also very close...
At the next extended, we need to think to insert a place in the XML for the
errors' messages of different SPARQL services for federated queries, with a
mode verbore ;)

It's maybe a good idea to start to prepare a new version of SPARQL


2018-07-11 15:49 GMT+02:00 Bijan Parsia <bijan.parsia@manchester.ac.uk>:

> Other hacks:
> 1) Wrap the result in a custom format and strip it off before passing the
> results to a results processor
>         Pro: pretty easy and clean
>         Con: Clients which are unaware of this will bork hard
> 2) Dork the schema to allow for the meta data and dork the schema location
> to point to your dorked schema
>         Pro: Lets you use the format of choice. Should work with most
> processors even validating ones
>         Con: If the process makes assumptions about the PSVI you could get
> borkage.
> I think link with datauri is likely to be the most robust if a bit
> unpleasant for e.g. inspecting the results by hand.
Received on Wednesday, 11 July 2018 14:09:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 July 2018 14:09:33 UTC