-
Notifications
You must be signed in to change notification settings - Fork 1
Evaluation Rules
Joel Håkansson edited this page Nov 3, 2017
·
3 revisions
This section outlines a preliminary set of evaluation rules.
A path may only revisit validation parts.
A path that is successfully completed ends the process.
In the identification phase, the means of identification should be exhausted.
A shorter path might yield an inferior result in the identification phase.
file ?> xml !> xml -> obfl
would be shorter than
file ?> xml ?> dtbook !> dtbook -> obfl
but would not be as good as the latter.
In this example, ?> indicates identifying, !> indicates verifying and -> indicates converting.
In the transformation phase, a shorter path is preferred over a longer one.
- If a part of type verify, enhance or convert fails, the process fails.
- If a part of type identify or fix fails, other viable parts may be tried with the same input.
For more information, see the common wiki