Well, yes. The reason is that using copy-of or something like it, the
tree returned by your extension can make it into the output document.
Pick a namespace that no one else can own like
"http://xml.apache.org/xalan/SQLExtension";.
Gary
John Gentilin wrote:
>
> Gary,
>
> Adding a new namespace works fine. One question though.
> Is a namespace only unique within a document. i.e. Since the
> SQLDocument is its own document do I have to worry about
> namespace clashes with any of the other documents ??
>
> Regards
> JohnG
>
> Gary L Peskin wrote:
>
> > You could also construct your elements in your own namespace so as to
> > avoid the problem with a user selecting the html output method.
> >
> > Gary
> >
> > [EMAIL PROTECTED] wrote:
> > >
> > > Regarding the fact that <col> is one of the elements subject to
> > > special treatment when the output method is HTML:
> > >
> > > >This is an interesting issue. The <col> element is being produced
> > > >by an extension function. So the output method of the extension
> > > >function is "xml" but the output of the transformation is "html".
> > > >To correct this problem, I would have to changed the output for
> > > >the whole transformation, which may produce invalid html.
> > > >Is this a bug or feature ??
> > > >JohnG
> > >
> > > I guess it's a bug somewhere, depending on the point-of-view of the
> > > beholder. Possible solutions:
> > > 1. Extension functions ought to be able to ascertain the "current"
> > > output method, which will be a dicey proposition in XSLT 2.0.
> > > 2. Pass in the name to be used, rather than assuming "col".
> > > 3. Assume a name that's not one of the special HTML names.
> > >
> > > I like (2).
> > > .................David Marston
