[Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

[Alan Kennedy]

[Alan Kennedy]
>> Looking at this in an MVC context .......

[Phillip J. Eby]
> As soon as you start talking about what templates should or should not 
> do (as opposed to what they *already* do), you've stopped writing an 
> inclusive spec and have wandered off into evangelizing a particular 
> framework philosophy.

Sorry if my message seemed unreasonable. My approach to such matters is 
to attempt to start from best design practice, keeping a keen focus on 
the best way to do things in the future, relegating poorly-architected 
legacy systems, e.g. active page systems, to being a secondary concern.

Also, my take on active page systems is that they could easily be 
encompassed by an MVC model. The View is the active page, the Model is 
the namespace in which the active page is rendered and the Controller is 
the thing that does the rendering.

[Phillip J. Eby]
 > At this point it has become clear to me that even if I spent my days
 > and nights writing a compelling spec of what I'm proposing and then
 > trying to sell it to the Web SIG, it would be at best a 50/50 chance
 > of getting through, and in the process it appears that I'd be burning
 > through every bit of goodwill I might have previously possessed here.

 > .. I'd rather save whatever karma I
 > have left here for something with a better chance of success.

I'm sorry to hear that.

[Phillip J. Eby]
> Good luck with the spec.

Well, I'm currently designing and implementing a View and ViewResolver 
in Spring for a customer, so I'll be keeping a note of requirements as I 
go, and will attempt to come up with a generic design which is suitable 
for a a templating standard. But it will be a few weeks before I can 
spec that, document it and start doing sample implementations which I 
can open source.

Regards,

Alan.