On Jun 12, 2012, at 10:38 PM, Gunnar Morling wrote:
> One scenario (but not necessary often used) is forward
"compatibility" where
> an BV 1.1 application run in an BV 1.0 implementation. With the version
> field in place, BV 1.0 implementor can check and handle the incompatibility
> easier and provided a more meaningful error message than taking an exception
> from the parser for any BV 1.1 syntax.
Hmmm, I think this would work if there was a "version" attribute in
the BV 1.0 schema. But as there isn't, a BV 1.0 provider would stumble
upon the unknown attribute when validating a 1.1 descriptor.
RIght. It would require new releases of the 1.0 implementations to handle this version
attribute.
I doubt existing implementation would be able to handle it.
--Hardy