Most (good) namespace conventions require a company name scoped namespace.
How well does this translate over to web applications? In many websites, the company is referred to by the website name (eg, Facebook, MySpace). Does this convolute namespaces, making them appear as if they can only apply to a single project?
For example, let's pretend a company creates WebsiteA(.com), and is henceforth referred to as 'WebsiteA'. WebsiteA creates a reusable authentication component for their project. They namespace it as such:
A year later, WebsiteA creates a new website, WebsiteB, and decide to use their previously created
Does this obscure the namespace? Should the company have used an alias separate from their website name as their CompanyName in their namespacing? Afterall,
WebsiteA.Auth isn't coupled directly to WebsiteA.com, and
WebsiteA is now more of a project of the company, rather than the entire company.