The current guidance on versioning is that the namespace URI should remain constant for all minor revs of a major version. That's fine, but I think the added feature of having that URI be a URL to the latest schema version is more confusing than convenient.
The biggest problem for VOTable is that the schema now has to allow multiple version attributes (e.g., 1.3 and 1.4) to support backward compatibility, while at the same time allowing 1.4-only features like TIMESYS. This makes the schema somewhat inaccurate as it allows version="1.3" and TIMESYS in the same document.
I would be happy to remove the convenience of having the namespace URI point to the latest schema. For VOTable writers that want to specify the schema (not required), they may as well point to the specific version. They know the version since they already must specify the version="1.x" attribute.
That discussion is outside the scope of VOTable itself, so if that remains unchanged, I propose that we recommend using the specific version schema URL instead of the namespace URI if referencing the schema.