W3C home > Mailing lists > Public > semantic-web@w3.org > April 2010

Re: Processing RDF in XML/XSLT workflows

From: Paul Gearon <gearon@ieee.org>
Date: Mon, 26 Apr 2010 18:59:52 -0400
Message-ID: <q2oa25ac1f1004261559x1739b614v402b8cbf16c7f1d3@mail.gmail.com>
To: Bob DuCharme <bob@snee.com>
Cc: Johan De Smedt <johan.de-smedt@tenforce.com>, semantic-web@w3.org
On Mon, Apr 26, 2010 at 5:14 PM, Bob DuCharme <bob@snee.com> wrote:
> Hi Johan,
>>SPARQL result xml is not a full solution because it is limited to ASK and
>> SELECT queries.
> Can you give me some examples of a need to process RDF with XSLT where the
> results of a SELECT query were inappropriate?

I confess that I've been wondering the same myself.

For any given RDF, a SPARQL result can contain all the information, or
any desired subset, often in a more convenient form.  For instance, an
RDF document can have the subjects and predicates in any order, but a
SPARQL result can order everything to creating groupings that would
make subjects and predicates easier to deal with:
  SELECT ?s ?p ?o FROM <graph:uri> WHERE { ?s ?p ?o } ORDER BY ?s ?p ?o

Sure, the elements aren't nested, but everything is there, and it's
completely deterministic.

Received on Monday, 26 April 2010 23:00:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:42:19 UTC