In other words, century compliance does not mean necessarily that century digits must be explicit or that dates should follow a specific format. For practical reasons, century compliance means simply that Y2K events will not occur, however the software is designed or changed to achieve this. Naturally, a 4 digit year is one means toward this end. Yet many applications can operate successfully across the century change by inferring the century from 2 digit years. When performed correctly, either approach results in the desired century compliance, and the argument about whether the data was wrong or the code was wrong is a moot point.
Arguments supporting each approach typically presume that only one can be the right answer.
Supporters of the data solution will argue that the mathematics were always correct, but the data was incomplete. Supporters of the procedural solution will counter that the century is usually inferable and that the code should have been written better. It matters little whether you determine that the bridge was too low, or the load was too high, when altering either or both will get you past the obstacle. Each offers advantages and disadvantages. Rarely would either be categorically favorable for all of an organization's software.