Comments F&R

Dear all,

below are some comments to the current version of the F&R document, per
my ACTION-46.

They are mainly minor changes, which I do not see as stoppers for
publishing FPWD.

Cheers,
Simon


"SPARQL is a query language for RDF data on the Semantic Web with
formally defined meaning. This document is a simple introduction to the
new features of the language, including an explanation of its
differences with respect to the previous SPARQL Query Language
Recommendation [SPARQL/Query 1.0]."

The new features of the language should somehow be qualified e.g.
"proposed by the [SPARQL WG]".

"3 Service Description" -> "3 Service Descriptions" (?) 

In general, we have a mixture of singular and plurals in the naming of
features, as well as subsection names. Personally I prefer plurals.
Whatever the decision, this should be consistent throughout the
document.

Section 5.5 is in the TOC, but does not exist.

Time permitting features: The names of the features in the overview are
not the same as the headlines. Links to the corresponding sections are
missing.

2.1.1
"They are currently not taken into account in SPARQL and then require
additional scripting to parse query results and get these informations" 
->
"They are currently not taken into account in SPARQL and require
additional scripting to parse query results and get these informations"

2.1.2
"Aggregates provides the ability" -> "Aggregates provide the ability"

2.1.3
"implementations tend to project out results like for example:" [...]
"return the number of times the a triple of the form _ :name "Alice"
appears in the source data." 
->
"implementations tend to project out results like in the following
examples:

Return the number of times the a triple of the form _ :name "Alice"
appears in the source data."
[...] here be the first example
"Return the average value of goods of type :Widget."
[...] here be the second example

2.3.2
"identify the name of people that does not know anyone)." 
->
"identify the names of people that do not know anyone)."

@@TODO
2.3.3
We might want to clarify, that SeRQL's MINUS != UNSAID in the other
implementations.

2.4.1
"Being able to return the values of expressions over result bindings,
rather than just RDF terms in the store."
->
"This features allows being able to return the values of expressions
over result bindings, rather than just RDF terms in the store."

2.4.2
"Projecting expressions represents the ability for SPARQL SELECT queries
to project any SPARQL expression"
->
"Projecting expressions represents the ability for SPARQL SELECT queries
to project any scalar SPARQL expression"

2.4.3
"In ARQ" -> "ARQ"
"In Open Anzo" -> "Open Anzo"

"We wish to find names, and whether the person is over 18."
->
"In the following example, we wish to find names, and whether the person
is over 18."

2.6.1
"Many classes of query over RDF graphs"
->
"Many classes of queries over RDF graphs"

2.7.1
"See Working Group issue: ISSUE-2 -
http://www.w3.org/2009/sparql/tracker/issues/2"
should be a link

4.1.2
"As such, it uses the SPARQL in both style and detail, reduces the
learning curve for developers and reduces implementation costs."
->
"As such, it uses SPARQL syntax in both style and detail, reduces the
learning curve for developers and reduces implementation costs."

4.2.2
"By this, clients doesn't need to know the SPARQL language to update
graphs when it is not needed."
->
"By this, clients do not need to know the SPARQL language to update
graphs when it is not needed."



-- 
Simon Schenk | ISWeb | Uni Koblenz
http://isweb.uni-koblenz.de
http://www.uni-koblenz.de/~sschenk
Five sentences policy: http://five.sentenc.es/