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 7758 - charGroupPart prose and production mismatch
Summary: charGroupPart prose and production mismatch
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: PC Windows 2000
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2009-09-29 15:10 UTC by Kevin Braun
Modified: 2009-10-12 13:24 UTC (History)
1 user (show)

See Also:

Attachments

Description Kevin Braun 2009-09-29 15:10:29 UTC 
The prose for charGroupPart says it includes charClassEsc, but the production says it includes charClassExpr.

If the given production is correct, then we may have regular expressions such as:
  [[abc]]

If that is the case, I think the "changes since 1.0" section should explicitly point it out.  As far as I know, such an RE would not be valid under the 1.0 grammar.
Comment 1 Dave Peterson 2009-10-02 15:18:36 UTC 
(In reply to comment #0)
> The prose for charGroupPart says it includes charClassEsc, but the production
> says it includes charClassExpr.
> 
> If the given production is correct, then 

I believe the prose is correct; we should correct the production.
Comment 2 Dave Peterson 2009-10-09 15:38:17 UTC 
Specifically, change

   charGroupPart ::= singleChar | charRange | charClassExpr

to

   charGroupPart ::= singleChar | charRange | charClassEsc

in production 80, the production for charGroupPart.
Comment 3 David Ezell 2009-10-09 16:06:18 UTC 
The WG approved the text in comment #2 as decided.
Comment 4 C. M. Sperberg-McQueen 2009-10-10 01:54:27 UTC 
The change described in comment 2 has now been made in the status quo documents, so I'm marking this issue resolved.

The originator of this issue (Kevin Braun) should receive an email notification of this status change.  If you are happy with the WG's disposition of your comment, please so indicate by closing the bug report; if something has gone wrong and you're not happy, please reopen it.  If we don't hear from you in the next two weeks, we'll assume you are happy with the change being made.  

Thank you in any case for catching this error.