A namespace, from a very broad point of view, is a top-level category under which other entities can be placed. Let’s imagine you have two namespaces, called magnet<\/em> and cat<\/em>, and that each contains the element gray<\/em>.<\/p>\n Now, magnet.gray<\/em> and cat.gray<\/em> can be absolutely different, and totally unrelated. The reason is that they’re from different namespaces. Families work the same: John Smith is expected to be a different person from John Jones. A family last name is a namespace.<\/p>\n A computer directory can be thought of as a kind of namespace. Yet, directories often use slashes, while namespaces use dots. Since both might be used simultaneously, the naming convention might need careful attention. Sometimes, for instance, a file might be located at “dir0\/f0”, but the API might refer to it as “dir0.f0”, in which case calling it “dir0\/f0” might lead to a “not found” error.<\/p>\n Source:<\/p>\n wikipedia<\/a><\/p>\nJack of Oracle Tutoring by Jack and Diane,<\/a> Campbell River, BC.\n","protected":false},"excerpt":{"rendered":" Self-tutoring about comp sci: the tutor mentions namespaces and directories. A namespace, from a very broad point of view, is a top-level category under which other entities can be placed. Let’s imagine you have two namespaces, called magnet and cat, …<\/p>\n