comment-Namespace-19 Namespace

I played a little bit with namespaces in my snipsnap installation. Here are my impression about namespaces.
At first I was very enthusiastic. I set up some namespaces, reorded some snips and wrote some macros for namespaces (see ThoMo - sorry for the spam ;-). Then I realize some drawbacks.

• create a new snip/edit a snip
  Enter a link to a snip is very arduous.
• If it links to a existing snip you have to determine (and enter) its namespache. Copy and Paste the namespace is not so easy because in the snip it is not printed in the right style (name > space > snip). But you can copy it from the link (and have to replace encoded spaces).
• If not existing ([create snip]) you have to think about its likely namespace and enter it. If later the correspondig snip is created at another namespace the link "is dead". (not realy dead but not link to the snip). Example: The snip "programming languages" point to [create programming languages/jdk]. Later the snip [java/jdk] will be created. The first one does not point to the second one.
• search a snip (like "aaa")
  if snip "aaa" exists in a namespace it is listed in the result but (if you are logged in) there is also a link to create a snip "aaa". (As long as snip /"aaa" does not exist.)

In summary, it is difficult to deal with namespaces and more difficult to explain new users how to deal with it. IMHO namespaces should be used only internally in snipsnap like for comments, webblogs but not to put any structure to the snipspace. Likely labels are more suitable to do this. But I have no idea about the meaning of the different label types. (If anyone can explain it please fill out the table at label.)
Perhaps I have not understand the concept of namespaces and misuse namespaces (in this case see my summary above).