Move grammar entry points text out of 'notes'. Tidy markup.

[afs]

This extracts the HTML changes from #272 (First EXISTS scope restriction PR) in the "Variable Scope" and Grammar Notes sections. The PR breaking up long lines in lists and changes most <code> to `.

The PR moves the grammar note about entry points and the note about LL(1) out of the notes list.

---

Preview | Diff

[hartig]

Thanks for your effort!

[TallTed]

Suggested change

	<p>The variable `v` must not be in-scope at the point of the
	`(expr AS v)` form. The scoping for `(expr AS v)`
	applies immediately in `SELECT` expressions.
	</p>
	<p>In `BIND (expr AS v)` requires that the variable `v` is not
	in-scope from the preceeding elements in the group graph pattern in which it is used.
	</p>
	<p>In `SELECT`, the variable `v` must not be in-scope in the graph
	pattern of the `SELECT` clause, nor used in another select expression earlier in
	the clause.
	</p>
	<p>The variable `v` MUST NOT be in-scope at the point of the
	`(expr AS v)` form. The scoping for `(expr AS v)`
	applies immediately in `SELECT` expressions.
	</p>
	<p>In `BIND (expr AS v)`, the variable `v` MUST NOT be
	in-scope from the preceding elements in the group graph
	pattern in which it is used.
	</p>
	<p>In `SELECT`, the variable `v` MUST NOT be in-scope in the graph
	pattern of the `SELECT` clause, nor be used in another select
	expression earlier in the clause.
	</p>

[TallTed]

Suggested change

	<li><a href="#rQueryUnit">`QueryUnit`</a> for the SPARQL query language</li>
	<li><a href="#rQueryUnit">`QueryUnit`</a> for the SPARQL query language.</li>

[TallTed]

Suggested change

	The SPARQL grammar is LL(1) when the rules with uppercased names are used as terminals.
	The SPARQL grammar is LL(1) when the rules with uppercase names are used as terminals.

[TallTed]

Suggested change

	<a href="#rDeleteData">`DELETE DATA`</a> and
	<a href="#rDeleteData">`DELETE DATA`</a>, and

[TallTed]

Suggested change

	The single space version is used in the grammar for clarity.
	The single-space version is used in the grammar for clarity.

[TallTed]

Suggested change

	<a href="#rDeleteData">`DELETE DATA`</a>
	<a href="#rDeleteData">`DELETE DATA`</a>,

[TallTed]

There are a few edits which might be applied here. This is my favorite. If there are significant objections, I'll provide other options.

Suggested change

	Blank node syntax is not allowed in
	<a href="#rDeleteWhere">`DELETE WHERE`</a>,
	the <a href="#rDeleteClause">`DeleteClause`</a> for
	`DELETE`,
	nor in <a href="#rDeleteData">`DELETE DATA`</a>.
	</li>
	Blank node syntax is allowed in neither
	<a href="#rDeleteWhere">`DELETE WHERE`</a>,
	<a href="#rDeleteData">`DELETE DATA`</a>,
	nor the <a href="#rDeleteClause">`DeleteClause`</a> for
	`DELETE`.
	</li>

[TallTed]

Normative language SHOULD NOT be used unless it is meant normatively. I'm sure I'm not catching all instances.

Suggested change

	must correspond to the number of
	MUST correspond to the number of

[TallTed]

Suggested change

	must be unique within that list.
	</li>
	<li>
	Variables introduced by `AS` in a
	<a href="#rSelectClause">`SELECT`</a> clause
	must not already be <a href="#variableScope">in-scope</a>.
	</li>
	<li>
	The variable assigned in a <a href="#rBind">`BIND`</a> clause
	must not already be in-use within the immediately preceding
	MUST be unique within that list.
	</li>
	<li>
	Variables introduced by `AS` in a
	<a href="#rSelectClause">`SELECT`</a> clause
	MUST NOT already be <a href="#variableScope">in-scope</a>.
	</li>
	<li>
	The variable assigned in a <a href="#rBind">`BIND`</a> clause
	MUST NOT already be in-use within the immediately preceding

[TallTed]

Suggested change

	The expression argument of an aggregate function can not
	contain an aggregate function.
	</li>
	<li>
	Only custom aggregate functions use the `DISTINCT` keyword
	The expression argument of an aggregate function cannot
	contain an aggregate function.
	</li>
	<li>
	Only custom aggregate functions can use the `DISTINCT` keyword