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 16679 - [XP30] EBNF contains unused production
Summary: [XP30] EBNF contains unused production
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.0 (show other bugs)
Version: Member-only Editors Drafts
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL: https://www.w3.org/XML/Group/qtspecs/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-10 10:11 UTC by Tim Mills
Modified: 2012-07-23 14:45 UTC (History)
2 users (show)

See Also:

Attachments

Description Tim Mills 2012-04-10 10:11:38 UTC 
Following the change to EQName syntax, the production 

[93]    	URILiteral 	   ::=    	StringLiteral

is no longer used.  It appears in the EBNF appendix, and also in Section 2 Basics.

This has the consequence that text in 2.4.5 URI Literals is now probably also redundant.  Further reworking of the text may be required where URILiteral is mentioned e.g. 3.3.2.2 Node Tests.
Comment 1 Tim Mills 2012-04-10 10:20:01 UTC 
This also may mean that

err:XQST0046

    An implementation MAY raise a static error if the value of a URILiteral is of nonzero length and is not in the lexical space of xs:anyURI.

is no longer required to be reference in the XPath 3.0 document.  Since xs:anyURI now has the same lexical space as xs:string, it is presumably a redundant error anyway.
Comment 2 Jonathan Robie 2012-05-15 16:56:40 UTC 
BracedURILiteral has been added, it is not yet defined anywhere in the specifications. I will update the spec to match the new grammar.
Comment 3 Michael Dyck 2012-05-22 06:45:25 UTC 
I have modified the XPath 3.0 grammar so that it no longer includes the URILiteral production. It should disappear when the XPath 3.0 document is next built.
Comment 4 Tim Mills 2012-07-23 14:45:44 UTC 
Confirmed fixed in XPath 3.0.

Thanks.