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 2978 - State XMLSPACE_DECL is obsolete
Summary: State XMLSPACE_DECL is obsolete
Status: CLOSED WONTFIX
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery/XPath Tokenizer (show other bugs)
Version: Candidate Recommendation
Hardware: Other Linux
: P2 normal
Target Milestone: ---
Assignee: Scott Boag
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-06 22:41 UTC by Frans Englich
Modified: 2006-04-04 16:23 UTC (History)
0 users

See Also:

Attachments

Description Frans Englich 2006-03-06 22:41:44 UTC 
State XMLSPACE_DECL says:

<quote>
This state occurs at places where the keywords "preserve" and "strip" is expected to support "declare xmlspace". QNames can not occur in this state.
</quote>

I guess it needs s/XMLSPACE_DECL/BOUNDARYSPACE_DECL/ and s/declare xmlspace/declare boundary-space/


Frans
Comment 1 Frans Englich 2006-03-07 00:20:33 UTC 
After further thinking:

Instead of letting <"declare" "boundary-space"> transit to state XMLSPACE_DECL, enter state OPERATOR. State OPERATOR already handles "strip"/"preserve" for 'declare construction'. This would render state XMLSPACE_DECL redundant.

One could also have a specialized state for 'declare boundary-space' and 'declare construction' which is identical to the current XMLSPACE_DECL although with a more generic name, but that wouldn't be consistent with how the other states are arranged.

Assuming I'm not wrong, of course.


Frans
Comment 2 Scott Boag 2006-03-29 22:08:01 UTC 
The document "Building a Tokenizer for XPath or XQuery" is obsolete.  If you do want to know what states we use to build our current test parser, the states are specified in the XML definition of the joint grammar, http://www.w3.org/XML/Group/xsl-query-specs/grammar/parser/applets/xpath-grammar.xml.
Note that the current test parser uses selective LL(2) or LL(3) lookahead, and the 
number of tokenizer states has been greatly decreased.