Sylvain Wallez wrote:
Should we stick to our own CInclude, or should we go back to XInclude [2] which has reached its 2nd candidate recommendation last september (how slow : the first draft was written nearly 3 years ago !) ?
The PR will follow suit IIUC.
A quick look shows that XInclude allows attributes in other namespaces on <xi:include>, which we may use to give some parameters to the transformer for a particular resource, and also supports an <xi:fallback> in case the included resource isn't available.Testcases for XInclude: http://dev.w3.org/cvsweb/2001/XInclude-Test-Suite/
Is this enough for our needs ?
Let's aim for standards compliance. There won't be many implementations (yet), so being a frontrunner will be good PR for Cocoon.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
