Alan, thanks for the interest.
I had this idea, not strong, but I think it is an excellent idea.
It would solve couple of issues, I had. One is having multiple types, for example. The main benefit though is to be able for one Thought to participate in different hierarchical structures.
Let say, you buy a computer. That computer can participate in you accounting structure, business, and software, hardware, and maintenance structure.
Currently you have two options.
1. You create one Thought for the new computer and link all the different structure to it, accounting, business, and so on, ....
2. You create different Thoughts for each category, one for accounting, and so on.
Both are not perfect. The first having the problem of clattering each other space. When I focus my attention of computer administration; I don't want to see accounting aspects, like where I bought the computer, and so on.
The second option has the problem that some information may be over lapping, among the different categories. For example the type of computer, the model number may be prevalent for accounting and maintenance aspects of the computer, so I may store it one place. For that information I need to be able to easily flip to it. The spouse relationship would help to consolidate that information.
I didn’t say that PB can not be used for those issues without a spouse relationship, but having it would make it easier to use.