Paul is right - of course. And I have mentioned some possible methods on
this list before.
>
>XSL works because it has a single task: rendering (not necessarily on
>paper!). The interfaces between the snippets of XSL code are
>well-defined, because all they are doing is passing around rendered
>document sections. If you want the same for Java classes, then you must
>define what you want those Java classes to do, and define appropriate
>interfaces for them.
If we can define a handle of some sort we can take the discussion of
methods elsewhere. e.g.
<?XDEV MIME="application/java" CLASS="foo.bar.Baz" METHOD="display"?>
I would prefer the PI target to be agreed more widely than XDEV - and
that's probably what I'm asking for.
P.
>
> Paul Prescod
>
>
>xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
>Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
>To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
>(un)subscribe xml-dev
>To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
>subscribe xml-dev-digest
>List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
>
>
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
net connection
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
http://www.venus.co.uk/vhg