Lists Home |
Date Index |
Mark Baker wrote:
> I think bringing out the namespaces is a useful optimization for
> enabling ahead-of-time construction of a compound processor. But it's
> really an optimization for a mechanism that doesn't yet exist;
> standardized dispatch keyed off namespaces. I'm working on that right
> now, but it's a little more complicated than I thought it would be.
I'd like to point out that a compound processor works only if you know
what the task is. That is, the task is an important piece of processing
context that is not part of the document.
The classic example of this is a browser, for which the task is
displaying stuff. In the case of XML, you look at the namespace and feed
the relevant fragment to the processor that knows how to display
fragments headed by that element.
Are there any other generic tasks beside display? The only other one I
can think of is an editor, where you might load a different editor for
XHTML than for SVG. At least in the data-centric world, all other tasks
I can think of (storing data in a database, processing invoices,
generating work orders, etc.) are specific to a given application, since
what I do with a given document is probably different from what you do.
This is important because the notion of such generic processors sits
behind at least some of the resources enumerated by a RDDL document.
It's fine if you can use them to display/edit the document, but I'm a
bit skeptical that you can use them for anything else.