|
From: Timo V. <sic...@gm...> - 2004-06-28 12:38:47
|
Am Montag, 28. Juni 2004 10:21 schrieb j=FCrgen h=F6ller [werk3AT]: > For a start, we need to decide: > - custom "include" element or XInclude support? I'd suggest a mix: Implement the custom solution as a single simple=20 filter class, which turns the parsed infoset into a new infoset=20 including includes, now. The syntax should be real XIncude but the=20 functionality only a subset (i.e. no XPointer, no parse as text, no=20 fixups [see spec] etc.), until a blackbox solution is available=20 somewhere else or until somebody writes it for spring. Then the filter=20 could simply be replaced, provding full XInclude support, while=20 retaining backwards-compatibility. Regards, Timo |