Here is another strange one:
http://en.wikipedia.org/wiki/Cloud_computing#Private_cloud
Private cloud
Private cloud and internal cloud are neologisms that some vendors have recently used to describe offerings that emulate cloud computing on private networks. These (typically virtualisation automation) products claim to "deliver some benefits of cloud computing without the pitfalls", capitalising on data security, corporate governance, and reliability concerns. They have been criticized on the basis that users "still have to buy, build, and manage them" and as such do not benefit from lower up-front capital costs and less hands-on management[56], essentially "[lacking] the economic model that makes cloud computing such an intriguing concept".[58][59]
This is a highly strange concept... the idea that the definition of a thing depends on the perspective from which that thing is being viewed. This definition of private clouds essentially makes the claim that the cloud ceases to be cloudy if you get too close to the underlying technology (e.g. having to physically manage a server on your intranet).
Let's think about this. Cloud services have to be managed at the hardware level somewhere along the chain. For consumers the cloud is a cloud because they are far away from the hardware. For the IT personnel managing the cloud it is not a cloud because they are too close to the hardware. So the cloud is both a cloud and not a cloud at the same time depending on your perspective.
This also supports my theory that ignorance is part of the definition of cloud computing.