Re: Version vs. Namespace

[Dare Obasanjo <kpako@xxxxxxxxx>]

--- Tim Bray <Tim.Bray@xxxxxxx> wrote:
> 
> 
> OK.  I claim that a single fixed namespace plus a
> single version 
> attribute on the root element, plus an extensibility
> framework 
> involving the usual mustUnderstand/mustIgnore
> primitives, will provide 
> a nice efficient framework for the long term.  I
> further claim that 
> there is now enough experience with this kind of
> versioning 
> architecture that we understand the implementation
> issues.  

I tend to agree with you.

> 
> So...... those who want a more complex and abstract
> versioning set-up 
> should start, I think, from use-cases, so that we
> get a nice clean 
> clear sense of exactly what the complexity buys us. 
> -Tim

My primary use case for versioning is simple. How can
an aggregator which encounters a different version of
Atom from one its seen before know whether it is
backwards compatible or not? With RSS, the assumption
I use in RSS Bandit is that all feeds are RSS 2.0 and
the version attribute is ignored. I'd like Atom to
have something formal about what aggregators like RSS
Bandit should do to be able to distinguish Atom 0.3
from Atom 1.0 [for example]. 

=====
THINGS TO DO IF I BECOME AN EVIL OVERLORD #95
My dungeon will have its own qualified medical staff complete with bodyguards. That way if a prisoner becomes sick and his cellmate tells the guard it's an emergency, the guard will fetch a trauma team instead of opening up the cell for a look.


		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail