Yes, this is a very good thing to do...

how do you want to do this? XSLT transformation?

regards,

Martin

On 8/4/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> You know, of course, that the prefix you mention in the TLD is mostly
> irrelevant, right?  It's up to the page to declare what prefix it is
> actually going to use.  The one in the TLD is merely a recommended
> default.

Yes I know this.  But its nice for the recommended defaults to be meaningful.

> The important issue is the tag library URI ... you will definitely
> want to maintain a (deprecated) version of the old TLD that contains
> this URI for some reasonable period of time.  And, from a mechanical
> viewpoint, you'll want the build process to generate both versions
> from some common source, so you don't have to worry about changing two
> TLDs every time you add a new tag or attribute.

Excellent idea concerning the build.  That was a problem the last time
we maintained two sets of TLDs like this.  Nobody every updated the
old one.  Lets just keep the single TLD in SVN and auto-generate the
legacy one in the build.

Thanks for the suggestion.

> Craig

sean

Reply via email to