My 2 cents on DataVault standards (evolution)

Let me start this post by saying that I admit that standards are important. This is especially true for people that are new to the subject, didn’t get any proper education or have almost no experience.

But an evolution of those standards is just as important. Proof of this is given by Dan himself otherwise we wouldn’t have DV 2.0.

I agree that any proposed changes to the standard needs to be proven. Sometimes this can mathematically be done but with another cases it may just be a matter of time will tell.

Upfront statements saying that the change won’t hold over time without the necessary arguments to prove this are just as worthless as accepting a change without the proof it will hold.

Keep in mind that some of the proposed changes may not be valid in all circumstances but only within a certain context. Many of these changes are even proposed by people that do have the proper education, certification and experience.

I can’t help getting a feeling that if the proposed change wasn’t thought of by the inventor himself, it’s bad by default. That’s a shame because it prevents a wide adoption of a good methodology for building enterprise data warehouses.

So let’s evolve those standards together and know what the implications of each are.