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 8454 - Tokens in XPath subset for selectors/fields (editorial)
Summary: Tokens in XPath subset for selectors/fields (editorial)
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.0/1.1 both
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2009-12-08 08:19 UTC by Michael Kay
Modified: 2011-01-14 21:25 UTC (History)
1 user (show)

See Also:


Attachments

Description Michael Kay 2009-12-08 08:19:47 UTC
In the XPath subset described in XSD 1.1 Part 1 section 3.11.6.2, production [2] written as

[2]   	Path	   ::=   	('.//')? Step ( '/' Step )*

would be better written

[2]   	Path	   ::=   	('.' '//')? Step ( '/' Step )*

since the lexical rules that follow make it clear that ".//" is two tokens which may be separated by whitespace.

Conversely, production [4] which is written as 

[4]   	NameTest ::=   	QName | '*' | NCName ':' '*'

would be better written

[4]   	NameTest ::=   	QName | '*' | NCName ':*'

since no whitespace is allowed within ":*" (or indeed, between the NCName and the ":*").
Comment 1 C. M. Sperberg-McQueen 2011-01-11 23:13:12 UTC
Proposal:  make the suggested changes to productions [2] and [4].  Also to production [7], which also has the string './/'.
Comment 2 C. M. Sperberg-McQueen 2011-01-14 21:25:52 UTC
The changes proposed in comment 1 have been made and integrated into the status-quo documents at 

  http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.html
  http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.diff-wd.html
  http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.diff-1.0.html
  (member-only links)

Accordingly, I'm marking this issue as resolved.

Michael, if you would verify the fix and close or reopen the issue accordingly?  Thank you.