Topics in the TopicMap need multiple inheritance

[KnowledgeGarden]

Is your feature request related to a problem? Please describe. A proper topic map, one which is capable of representing real-world topics, must support multiple inheritance. That is, a given topic can be a subclass of several parent topics.

Describe the solution you'd like The solution is two part:

• Add the UX required.

• Ensure that conversation.hooks.js can handle this (likely can, but must be validated)

UX is the primary issue. A simple solution is like the one used for generating connections. In that solution, a user first selects a node to participate in a connection by clicking that node's New Connection link. The system remembers that selection in localstore. After selecting a second node for the connection, the system now changes behavior and presents the UX for choosing a relation type.

Mapping that idea to multiple inheritance, you need:

• A way to Remember a Topic node (not available to other node types). The idea being: save this node so it can be made a SubClass of some other Topic.

• A way to recognize the remembered node when visiting another Topic's Subclasses section. In that case, in addition to showing the New Subclass link, show an Add Subclass link. Clicking that link adds the remembered topic as a subclass.

[KnowledgeGarden]

I am showing this in the MVP project but do not think it's critical to the first presentation of that platform; it can be added in the coming weeks.