Framework Design Guidelines Names of Namespaces

  • Article

Continuing in the series of discussing topics from the Framework Design Guidelines…

 

Expert from 3.3 Names of Namespaces

 

DO use a stable, version-independent product name at the second level

of a namespace name.

DO NOT use organizational hierarchies as the basis for names in

namespace hierarchies, because group names within corporations tend

to be short-lived.

BRAD ABRAMS This means staying away from the latest cool and

catchy name the marketing folks come up with. It is fine to tweak the

branding of a product from release to release, but the namespace name is

going to be burned into your client’s code forever. Therefore choose something
that is technically sound and not subject to the marketing whims of the day.

 

I’d love to hear examples of this one… where have you seen a group name or marketing name change that made a namespace name meaningless or worse yet, misleading?