2978 2006-03-06 22:41:44 +0000 State XMLSPACE_DECL is obsolete 2006-04-04 16:23:27 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery/XPath Tokenizer Candidate Recommendation Other Linux CLOSED WONTFIX P2 normal --- 1 frans.englich scott_boag public-qt-comments oldest_to_newest 8601 0 frans.englich 2006-03-06 22:41:44 +0000 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 8602 1 frans.englich 2006-03-07 00:20:33 +0000 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 8959 2 scott_boag 2006-03-29 22:08:01 +0000 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.