What's in a name(space)? That which we call a rose...
Well, religious beliefs apart, I'm not a man of immutable mind. Indeed I believe that you *have to* change your mind when a proof demonstrates that there's something wrong with an idea (hey, I'm not saying that it's *easy* to make me change my mind, but this is another story...).
But I didn't have any reason to change my mind about how a Java namespace should be created - and this is by far the most ancient Java belief I have, since namespaces were the first thing I learned about Java in 1995/1996.
So, if you look at my open source code, everything starts with it.tidalwave.* (which the exception of org.jdesktop.beansbinding that I inherited) - this is because Tidalwave is my container, my home on the Web. In many cases, I've also taken care of decoupling the name of a project from its namespace; for instance, jrawio is it.tidalwave.imageio.*, and Mistral is it.tidalwave.image.*. In this way I can always change the name of a project (e.g. because of marketing, or because it turns out somebody owns a trademark on one of my names) without breaking compatibility with the code.
Still, it appears it's not enough - the choice about jrawio namespace has been questioned a few days ago on the dev mailing list:
What if you sell tidalwave? The FLOSS licensing guarantees the openness, but the product name then will become absurd.
What if you discontinue tidalwave?
It's the same silly story with GlazedLists, where all of glazedlist[s].[org|com] are available - but they choose to use a name of a supersmall company whose primary business is selling guns and ammo - because that was where it got its initial funding when the primary author was some kid in highschool. (odell.ca)
I must confess I've never thought of it. Tidalwave is my own, one-man company, basically it's a