-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[EMAIL PROTECTED] writes:
> "Kevin A. Burton" <[EMAIL PROTECTED]> wrote:
> > Realisitically xalan could reduce code complexity by automatically
> detecting namepaces which start with xalan:// and make them extensions.
>
> It's a requirement in the XSLT recommendation that extension-element-prefixes
> be used, so I don't think it makes sense to automagically detect xalan:
> namespaces.
True... but why?
I mean when a developer writes a Xalan extension there is NO gaurantee that this
will be portable to other transformers.... I believe the spec even warns of
this ( I would quote directly but I don't have Internet access right now ).
Since these extensions are already non-portable I believe we should adompt an
approach where we make it *easy* to plug in extensions via a namespace which
begins with xalan://
If no one agrees... no big deal. I think that it would just be slightly more
elegant to reduce the maintenance of the extensions-element-prefixes attribute.
Kevin
- --
Kevin A. Burton ( [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] )
Cell: 408-910-6145 URL: http://relativity.yi.org ICQ: 73488596
Calm you fury, oh mighty lord. Whatever you may be, god or demon, please leave
us in peace.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
iD8DBQE7bGgaAwM6xb2dfE0RAplmAKCvj5ApZEnIWdGMC/itBTfS+4VAagCgkkXl
kbgrHosrJ4/s/8DEMiTpH5o=
=XFXM
-----END PGP SIGNATURE-----
