Changelist 13.6.2012 3.6 generating: improved 3.20 parsing: improved 3.22 right-hand-context: improved (constraining...during applying this grammar rule). (Deutsch: Fortsetzungskontext) 3.25 Improved wording of terminal-sequence, comprehensive (S0) 3.26 Improved wording of terminal-sequence, remaining (S) 6.2.1.1 Fixed syntactic stuff with directives 7.4.2 Completed semantic stuff of directives 7.14.3.3 Improved wording of Note1. 7.14.3.3 Jonathan improved wording of Note2. 7.14.3.3 Added Notes 4 and 5 7.14.4 Improved wording of Note2, links to 7.13 7.14.4 Removed non-terminal indicator seqence and ..list 7.14.5.2 Improved Explanation of the Example 7.14.5 Prolog goals in grammar rules Moved explanation (former) 7.14.6.6 to this place and omitted 7.14.6.6 7.14.8 N//A -> N/A': stated, that A' == A+2 8.1.2.4 Improved wording: prepared for execution. 11 Logical Expansion: Prolog Definition of phrase/3 Used the corrected latest version of Ulrich Neumerkel General: The error handling, and the interaction between prolog predicates in the database and expanded grammar rules which create prolog clauses should be handled much more radically (cf. 7.14.8: Executing procedures stemming from expansion of GR) But there is much current practice which resists. It's the old philosophical question: What is a Prolog Standard for? What is industrial use of Prolog, who uses Prolog in Industry? We have no more industrial applications contributors in WG17 (like during Pt 1). Who serves their interests?