Yes, no one designs their KB perfectly the first time around, and a full hierarchical path would be stupendous. Otherwise we have to fake it with tags ... 😵‍💫

Already voted, but I want to add a few words:

The lack of inheritance is the main reason I am currently using Tana more than Capacities. It would be great to be able to implement a richer ontology with subclasses!

It would also make linking via properties way more powerful, since at the moment it's possible to link to a single object type. Linking to a superclass would allow for more flexibility

Thanks for voting on this ticket.

Object inheritance is currently not on our roadmap. While we agree that this is an important power user feature, we think that there are many more topics that should be added to Capacities first. While including more work you can always reach the same result by duplicating settings across object types.

We still encourage you to vote on this ticket to get a better idea of the importance to users and to stay updated on the topic.

Definitely also waiting for this :-)

A good example of how this works is in Anytype. Each type's objects can be displayed in views that use distinct filtering, sorting, and property/column selection. This way, use can effectively create subtypes. If only their sidebar and search tools were up to par with capacities.

I’ve been looking at all the apps in this space lately and I think Tana and Heptabase are the best examples of this. Both go beyond simple single inheritance with supertags. This approach attaches properties to supertags that can conceptually be thought of as a DAG. In Heptabase, any properties that appear in multiple supertags attached to an object (or their ancestors) are automatically shared by all of the supertags. I don’t know what the behavior is in Tana (maybe someone else does?).

This feature is extremely powerful. One example is that it enables creating a supertag for workflow-related properties that might apply to content of many different types.

I have many further thoughts on this feature space and would be happy to share more when you are ready to start thinking about it in more detail (which I hope will happen soon!).

I tend to agree with this. Originally, i just assumed this was going to be the functionality of the categories.

It would be great if capacities could inherit properties like tana, as this would allow us to better structure information.

Inheriting properties for capacities, similar to tana, would be a valuable feature for organizing structured data.