W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1386] [XQuery] some editorial comments on A.2.2.2 Explicit Whitespace Handling

From: <bugzilla@wiggum.w3.org>
Date: Sat, 09 Jul 2005 21:00:27 +0000
To: public-qt-comments@w3.org
Message-Id: <E1DrMR1-0000Dg-Hl@wiggum.w3.org>


------- Additional Comments From scott_boag@us.ibm.com  2005-07-09 21:00 -------
(In reply to comment #0)
> A.2.2.2 Explicit Whitespace Handling
> [See a later comment for suggested alternate wording.]
> (whole section)
>     Given that there's only one 'ws:' notation now, you could reduce some of the
>     repetition.
> "if EBNF rule"
>     Insert "an"


> "do not inherit"
>     Do not inherit what? You mean "are not inherited".


> "the rule does not automatically apply"
>     Change "rule" to "notation" or "marking".


> "ws:explicit"
>     insert space after colon


> "S explicitly notates where whitespace is allowed"
>     'S' isn't the only such symbol. There's also Char and [^abc].

Now reads:
<gitem id="ws-explicit"><label>ws: explicit</label><def><p>/* ws: explicit */
means that  the EBNF notation explicitly notates,  with <code>S</code> or
otherwise,  where <termref def="Whitespace">whitespace characters</termref> are
allowed.  In productions with the /* ws: explicit */ annotation,   <specref
ref="DefaultWhitespaceHandling"/> does not apply.  <nt
def="Comment">Comments</nt> are also not allowed in these

> "Whitespace is not freely allowed in the direct Constructor productions, but is
> specified explicitly in the grammar, in order to be more consistent with XML."
>     Start the sentence with "For example,". (Before "ws" annotations were
>     introduced, the sentence was normative, but now it's just rephrasing the
>     effect of some of the "ws" markings.)


>     Change "allowed in" to "allowed by".


>     Change "Constructor" to use lower case 'c'.

Received on Saturday, 9 July 2005 21:00:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC