My only thought on this is: if this is used simply as a variable naming convention, does the com.domain part need to be a real domain? If not, why not save your fingers and just go with com.slap.whatever?
While you don't have to use a domain as the Java package name, if you do use a domain it is good form to own, or have permission to use that domain name. While it is highly unlikely that the people that own slap.com or slapstick.com will release Java code for TKOH/A3, it is a good idea not to encroach on other people's property.
If I don't use a real domain name, say I just use slapstick.*
for my packages, there is nothing that prevents others from using that package name as well; I'm not the only Slapstick in the world. At least if I use a domain I own, or have permission to use, I have a little more justification telling any encroachers to stop using my namespace.
So no-one really had a lot to say, unfortunately.
No news is good news
I don't suppose you could type down a few words as to how this thing would work the best in terms of tags, namespaces and whatnot, so that we could produce some kind of guideline for people to follow?
I would be happy to, but I'm not sure what exactly you want. It would probably suffice to post a statement to the effect:
Authors who have a registered OFPEC tag are authorized to use the com.ofpec.<tagName> domain for their Java package names. All other uses of the com.ofpec Java namespace are reserved and may not be used for any purpose without prior written permission of the OFPEC administrators.
Also, do the OFPEC admins have any plans for setting up a Java Depot
sometime in the future? I have several suggestions for what that should entail as well