XUL:Templates Plan: Difference between revisions

the <bindings> block, but the Query Processor assigns the bindings.

Separating the query from the conditions would seem to remove efficiency, for example, for a server applying conditions to reduce a scoped data set to a managable size. The current template rules combine query and condition in the condition clause. Perhaps, rather than view this as a short hand for two separate things, let it stay atomic and let new mechanisms emulate the combination. Separating conditions also raises the bar for version 2. Certainly RDF templates could use better condition support, but is it a blocker before deploying a new data-format independent mechanism? Leaving conditions to the query mechanism would isolate this shortcoming in the RDF mechanism, an infrastructure that could be considered separately from making a data format agnostic template builder. Perhaps query-wise, it need never change as it may be superceded by a SPARQL query processor for comprehensive RDF processing.