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 30007 - [XP31] (editorial) Missing subject in sentence
Summary: [XP31] (editorial) Missing subject in sentence
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-16 21:46 UTC by Abel Braaksma
Modified: 2016-12-06 15:47 UTC (History)
2 users (show)

See Also:

Attachments

Description Abel Braaksma 2016-11-16 21:46:13 UTC 
Under the section on whitespace rules, we say "an XPath", whereas we normally say "an XPath expression", or "an XPath 3.1 expression" (or processor, error etc).

Under section A.2.4.1 Default Whitespace Handling:

"Ignorable whitespace characters are not significant to the semantics of an expression. Whitespace is allowed before the first terminal and after the last terminal of an XPath."

I suggest we end the sentence as something like "after the last terminal of an XPath 3.1 production."
Comment 1 Michael Dyck 2016-12-06 04:39:29 UTC 
> I suggest we end the sentence as something like "after the last terminal of
> an XPath 3.1 production."

That would be either incorrect or dangerously close to it. For example, whitespace is not allowed after an instance of the BracedURILiteral production (because BracedURILiteral occurs in productions marked "ws: explicit" that don't allow whitespace after it).

I think it would be fine if we just changed "an XPath" to "an XPath expression".
Comment 2 Abel Braaksma 2016-12-06 15:47:47 UTC 
(In reply to Michael Dyck from comment #1)
> I think it would be fine if we just changed "an XPath" to "an XPath
> expression".
Sounds good to me.