Different strategy (strict top down) for grammar simplification as alternative or replacement of the current one.
Basically:
<---- <------- <----- (attempt to shrink in all rules referenced by remaining level 1 rules)
<---- <---- <------ <----- <---- (attempt to shrink in all rules referenced by remaining level 2 rules)
Processing one rule (=attempt to shrink) maintains the information about other rules (level) occuring
within the components of the current rule.
I have a prototype.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- High
- Drafter:
- Matthias Leich
- Direction:
- Needs approval
- Assignee:
- Matthias Leich
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I already have a proof of concept prototype which works but needs some refinement.
So the next steps will be
1. Draft the specification
2. Refine the prototype so that it follows the specification
3. Experiments + some iterations of 1.+2.
4. Get an approval for the specification
5. A Perl expert improves or reworks my proof of concept prototype + pushes
