It's a fundamental fact that the entire calendar will exist in data as a string of bits, and, as the algorithm exists in my mind, that string of bits will be subdivided to form a string of bytes, or, more properly, letters, numbers, and punctuation marks. By "in data" I mean that the string of bytes will be stored in some form of computer memory, and it will have an address, so, giving that address to a utility designed for the purpose, that utility will be able to retrieve the string of bits. Dividing the string of bits into bytes is a step towards making the string human readable. Doing so presupposes, or suggests, in a way, that "we" are going to interact with the string directly, which would seem to be for programming purposes, as the end user will interact with it through the graphic representation introduced previously (as an abstract concept).
Moving forward, when I write about the string I will be writing about the string of bytes, that is, the string of characters the bytes record.
When I write about the calendar, I will be writing about the graphic representation.
An uncomfortable realization: the string is probably XML.
