

Re: review of rq23 1.377

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Mon, 13 Jun 2005 13:55:20 +0100
Message-ID: <42AD8238.2090607@hp.com>
To: kendall@monkeyfist.com

Kendall Clark wrote:
>>Protocol And RDF Query Language (SPARQL) [I think the acronym for
>>>the query language and protocol shouldn't be overloaded in this document 
>>>to refer to the query language alone. It's potentially confusing and bad 
>>>meet the requirements and design objectives described in RDF Data Access 
>>There isn't a separe name for the query language.  It already says "query 
>>language part of".
> you do, then maybe the confusion will be more obvious?

Hmm - the QL is SPARQL already is "query language" so that is "query language 
query language" as the acronym is expanded at that point.

"query language part of the"

avoids that.

> All over the DAWG page we say "SPARQL query language" rather than just
> "SPARQL", because that would confuse people.
> (And, further on, it says "The simplest graph pattern is the triple
> patterns" now: I think you mean s/patterns/pattern/?)
>>>Later sections of this document describe how other graph patterns can be 
>>>and also how queries can extract information from more than one graph 
>>>allowed in matching a pattern.
>>Kept the last part as-is because it emphaises the combination of triples 
> FWIW, it should be semicolons separating these phrases, or commas, but not a
> mixture of both.

I see pandas.

>>(we don't talk about "producers").
> Well, it's shorter (which counts) and it covers both "clients" and
> "applications". What's the difference between a client and an application?
> And there's no rule that says if you use "consumer" you have to use
> Thanks for the response, Andy.
> Kendall Clark

Received on Monday, 13 June 2005 12:57:06 GMT
