Versioning XRID

["Dave McAlpin" <Dave.McAlpin@epok.net>]

Comment below.

> -----Original Message-----
> From: Wachob, Gabe [mailto:gwachob@visa.com]
> Sent: Friday, June 04, 2004 9:59 AM
> To: Fen Labalme; Dave McAlpin
> Cc: xri@lists.oasis-open.org
> Subject: RE: [xri] Possible changes to XRI 1.0
> 
> Fen-
> 
> 	Let me respond inline
> 
> 
> <snip>
> > Versioning -
> >
> > As not all resolvers will be updated simultaneously, it seems
> > to me that
> > it would be useful to have a <ProtocolVersion> element that could
> > envelope new (or old) elements and tags.  Or is the xmlns tag
> > supposed
> > to be versioned?
> 
> The xmlns tag is supposed to be versioned, BUT this *may* be a
different
> thing than versioning the Protocol. In other words, to promote
backwards
> compatability, a newer version may use the basic structure of the
original
> XRIDescriptor schema, with added extension elements. This would allow
an
> older implementation to still interoperate at a 1.0 semantic level.
> 
> Having a ProtocolVersion tag may be useful for pointing out XRI
> Authorities that speak newer versions of the protocol - and this would
be
> independent of a rev'd version of the core XRIDescriptor namespace.

I intended to add version to the XRID on our next rev as two attributes
to on the top level XRIDescriptor element, one attribute for major
version and one for minor. Major rev would indicate a version that for
whatever reason was not backward compatible. Absence of the version
attributes would imply 1.0.

Dave