The immediate next goal is to verify properties of render nodes generated by the builder framework; two kinds of validations can be distinguished * structural aspects of the wiring * the fact that processing functionality is invoked in proper order Looking into the structural aspects brings about the necessity to identify the actual processing function bound into some functor. Some recapitulation of goals and requirements revealed, that this can not be a merely technical identity record — because the intention is to base the ''cache key'' on chained processing node identities, so that the key is stable as long as the user-visible results will be equivalent. And while structural data can be aggregated, at the core this information must be provided by the scheme embedded into the domain ontology, which is tasked with invoking the builder in order to implement a ''specific processing-asset'' |
||
|---|---|---|
| .. | ||
| application | ||
| steam | ||
| vault | ||
| DIR_INFO | ||