TRPL

TRPL¶

I've read the docs about TRPL (mostly the Writing_TRPL_Rule-Sets chapter), and some questions remain unanswered:

1. I see multiple terms in the docs: profile document, master profile document, master document, profile, top-level, A PatternEngine profile, Pipeline profile documents, cfg. I suspect all they denote the same thing, correct?
2. Are absolute paths supported in named rule-sets and includes?
3. About load-condition attribute: the only value used in FWD for this attribute is "runtime-query". May be, the attribute semantics should be changed to boolean "is runtime query"?
4. About honor-hidden attribute: default value is not defined in the docs. Is there any default for this attribute?
5. The docs says "If this attribute is not provided, an inline ruleset definition is assumed." and "inline" rulesets are immediate children of the "profile" file. Is it valid to use a not-named ruleset inside other rule-set. If yes, how will it be processed? The relations between "top-level", "named", "inlined" and "merged" are not clean to me.
6. The docs mentions "filtered view". How this filteres view is defined in ".xml" and ".rules" files? Or somewhere else?
7. from where the profiles are run? In which sequence? Is conversion flow documented anywhere, starting from ConversionDriver and like?
8. "pattern path". Is this the value of "patpath" parameter in "p2j.cfg.xml"? This is not explayned in the docs.

Other notes:

1. The term "profile" is used in the docs. Sometimes it refers the files with <cfg> toplevel element only, sometimes also with <rule-set>. Which is correct?
2. "<ast-spec>" element is not used in FWD rules, so its support may be (if not already) dropped, and the description removed from the docs.
3. "<expression>" element is still used in FWD rules, but is never named, so the reference to named expressions can be removed from the docs (and support dropped).
4. "Pipeline profile documents always have a filename extension of .xml. Rule-Set profile documents always have a filename extension of .rules..."
   "A pipeline profile must use the .xml file name extension; a rule-set profile must use the .rules file name extension."
   This is not true: at least one file "schema/p2o_common.rules" is a profile document with the ".rules" extension.
5. According to the docs, "worker" elements can be used in profile scope only. Meanwhile, they are widely used in "rule-set" elements.

The docs say TRPL function parameters may have default values (like TRPL variables). But it is an error if I pass to expression compiler less parameter values than is declared for the function. So, either the docs or expression compiler needs fixing. Am I correct?