The horse has bolted for XML 1.0 implementations, so clarifying that an XML 1.0 implementation should barf when faced with another number will not cause trouble, I expect. However, I suggest that for future versions of XML the Core WG adopt three part version numbers: major.minor.tweak with the policy that an XML processor *must* reject a major version number it doesn't know about *should* reject a minor number it doesn't know about *must not* reject a tweak number if it knows the major and minor If processors have this policy in place, it would give the WG a richer vocabulary to work with, and therefore greater flexibility and compatability, for future versions. So, to extract the requirement, I think the WG should adopt some numbering policy for non 1.0 versions of XML which gives them enough flexibility to maintain and evolve XML with least disruption. Cheers Rick JelliffeReceived on Saturday, 20 July 2002 01:47:40 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:32 GMT