In the field of Computer Science, there are many sub-disciplines, and there are varying shades of technical opinion. One of the shadiest of these is that of the database managers. An outspoken group on many subjects, always willing to force academic ideals of data integrity on hapless junior programmers, critical of any engine that caters primarily to real-world use cases, and always willing to compromise any such principles in any situation that affects them personally. Phil Ochs fans are laughing, everyone else is confused.
To illustrate: Everybody knows C programmers can’t count to ten on their fingers, because they start at zero. But if you ask a C programmer to provide ten items, he will – they’ll just be numbered from zero to nine, that’s all. A Visual Basic or FORTRAN programmer will give you the same absolute number of items, although they’ll be numbered from one to ten. Two boxes twice is always four boxes, in the world of workers getting things done, no matter the language nor what the labels on the boxes say.
Perhaps only in the field of database management would a list of “Ted Codd’s 12 Rules” include 13 items numbered zero through twelve. I suspect that in any other field, this would be considered a typographical error and quickly corrected in the proofreading stage.