xml-dev - RE: Deprecating XSLT templates

[Tim McCune <timm@channelpoint.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, here's a super-quick example:

<xsl:template name="a">
	<xsl:message>Template a is deprecated.  Use template b
instead.</xsl:message>
</xsl:template>

<xsl:template name="b"/>

So, we _are_ talking, more or less, about an API.  Other stylesheets
can call into these named templates, and we're trying to discourage
them from using certain templates without breaking their
functionality.  We're not talking about overriding, and we're not
talking about overriding an entire stylesheet, just individual
templates.

- -----Original Message-----
From: Evan Lenz [mailto:elenz@xyzfind.com]
Sent: Thursday, October 05, 2000 3:54 PM
To: xml-dev@lists.xml.org
Subject: RE: Deprecating XSLT templates



I'm trying to figure out what you mean.  If you provide an example
with your
reference to <xsl:message>, perhaps some of us can get an idea of
what
you're getting at.

Are you talking about deprecating *particular* template rules in a
stylesheet?  "Deprecation" doesn't really make much sense here,
because
we're not talking about an API, as in "You're discouraged from using
this
template rule".  It's up to the stylesheet processor which template
rules to
apply.

Perhaps you wish to override a particular template rule?  This can be
done
using <xsl:import>, where the importing stylesheet template rules
override
otherwise matching rules in the imported stylesheet.  This might be
compared
to inheritance in Java, except that multiple inheritance is also
supported,
since you can import from more than one stylesheet (although we
normally
don't consider importing stylesheets to have an "is-a" relationship
with
imported stylesheets; "home.xsl is a page.xsl and is a navbar.xsl,
etc.").
Somehow, I don't think that's what you're after either.

Perhaps you're interested in "deprecating" entire stylesheets, which
at
least would make more sense from the perspective of an API.  When I
compile
something in Java, it may give me a message saying "this method has
been
deprecated".  In that sense, I suppose that <xsl:message> would be
the
appropriate route, except that I wonder why that stylesheet still
exists,
why you're calling it, or why you wouldn't want it anymore.

Please give more details!  What's the issue that made you raise this
question?

Thanks,

Evan Lenz
elenz@xyzfind.com
http://www.xyzfind.com
XYZFind, the search engine *designed* for XML
Download our free beta software: http://www.xyzfind.com/beta


- -----Original Message-----
From: xml-dev-errors@lists.xml.org
[mailto:xml-dev-errors@lists.xml.org]On Behalf Of Tim McCune
Sent: Thursday, October 05, 2000 11:49 AM
To: xml-dev@lists.xml.org
Subject: RE: Deprecating XSLT templates


- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The same way you would deprecate a method in Java.  Sorry, I didn't
consider the non-programmers here.

- - -----Original Message-----
From: Peter S. Housel [mailto:housel@home.com]
Sent: Thursday, October 05, 2000 12:12 PM
To: xml-dev@lists.xml.org
Subject: Re: Deprecating XSLT templates


Tim McCune <timm@channelpoint.com> wrote:
> The subject line sort of says it all.  Has anyone given any thought
> to this?  The only thing we've come up with so far is sticking some
> <xsl:message>s in them.

I can't make heads or tails out of the subject line.  Do you want to
"express disapproval of", "play down", or "disparage" XSLT templates?
 Are
you trying to compute your income taxes, and need to "lower their
price or
estimated value"?

Cheers,
- - -Peter S. Housel-   housel@acm.org  
http://members.home.com/housel/


- -----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use
<http://www.pgp.com>

iQA/AwUBOdzMfNUPOr8a7vy5EQJhzgCdG2eJyyQRH9yffqf3aIGfknFqKNsAoP+o
/HL2ssQceMPE9ZPdeUXxPNDb
=niWF
- -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBOdz6O9UPOr8a7vy5EQKOkACeKKhWUEPynNrQEU9doEPTs852eO8AoKOO
LPXHkQhf82iaFLO6ii4zcrAi
=VeSO
-----END PGP SIGNATURE-----