You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Interlude</strong><br />
Redundant Array <strong>of</strong> Pyramid<br />
Hieroglyphics (RAPH)<br />
How do you store data so that it can be accessed a long, long<br />
time in the future? Like hundreds or thousands <strong>of</strong> years from<br />
now? On a trip to Egypt I learned how the ancient Egyptians<br />
accomplished this.<br />
Some temples in ancient Egypt were for the dead, but others<br />
focused on the living. Those temples were partly religious,<br />
but they also functioned as centers <strong>of</strong> learning and healing, a<br />
sort <strong>of</strong> combination church, university, and hospital. The temple<br />
<strong>of</strong> Kom Ombo was for the living, and it used an interesting<br />
data protection technique. When running a temple, priests must<br />
perform different procedures every day <strong>of</strong> the year—different<br />
prayers, different <strong>of</strong>ferings, different sacrifices. To ensure procedural<br />
compliance with data protection, the builders carved<br />
the operator’s manual, a large table with 365 different sets <strong>of</strong><br />
instructions, into stone walls.<br />
Then as now, personal information required extra protection<br />
to prevent identity theft. Pharaohs made colossal statues<br />
<strong>of</strong> themselves, but if it was a good statue, a later pharaoh would<br />
recut the hieroglyph to replace the old name with his own. In<br />
response, Ramses II developed write-protected hieroglyphs. He<br />
cut them inches deep into hard granite. Expensive, true, but<br />
thirty-five hundred years later, Ramses II is one <strong>of</strong> the bestknown<br />
pharaohs.<br />
41