This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1386 - [XQuery] some editorial comments on A.2.2.2 Explicit Whitespace Handling
Summary: [XQuery] some editorial comments on A.2.2.2 Explicit Whitespace Handling
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Scott Boag
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard: grammar
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-11 07:40 UTC by Michael Dyck
Modified: 2007-02-25 23:53 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2005-05-11 07:40:21 UTC
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].

"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'.
Comment 1 Scott Boag 2005-07-09 21:00:27 UTC
(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"

Done.

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

Done.

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

done.

> 
> "ws:explicit"
>     insert space after colon

Done.

> 
> "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
productions.</p></def></gitem>

> 
> "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.)

Done.

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

Done.

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

done.
Comment 2 Scott Boag 2005-07-22 19:30:43 UTC
A joint meeting of the Query and XSLT working groups considered this comment on 
July 20, 2005.  

The WGs agreed to resolve these editorial issues as listed in my previous comment.

If you do not agree with this resolution, please add a comment explaining why.
If you wish to appeal the WG's decision to the Director, then change the Status
of the record to Reopened. If we do not hear from you in the next two weeks, we
will assume you agree with the WG decision.
Comment 3 Jim Melton 2007-02-25 23:53:52 UTC
Closing bug because commenter has not objected to the resolution posted and more than two weeks have passed.