Yepp, now we're talking. It's the naturally the best way if we want to keep track of LDD version. But it's also possible to instead just track the date when the post was added or modified, because the brickset version is a direct function of date (since LDD is auto updating, we know that all people use the same brickset version at a given time).
To be honest, and digging into this even one more level, I have been even wondering what the need of tracking the LDD version OR brickset is in the first place. What does it give us? Sure, it can give some indication of which bricks are missing (and could possibly be available in a later brickset). But isn't that what we keep track of in the "notes/missing bricks" section of each post. And the same with collision errors etc that may have been fixed.
I'm not saying keeping track of LDD Version is a bad thing, just wondering what the good is (and being a bit of the devils advocate I suppose). We have to put the value of each increased piece of data we track in contrast to increased the threshold for people posting new sets in this topic.