Its ultimately about organization of the events.

You can listen to albums in their linear order, or you can create playlists that explore multiple artists and albums. You can customize how you want the information to be organized.

Example: Suppose you want to replace a transmission for your car, but its hard to navigate and understand the several manuals that discuss replacing the transmission. With the event kinds we have, you would be able to navigate the manuals more easily to find the specific pages that discuss transmissions and find the one that you understand the best.

If you look at the feed on next-alexandria.gitcitadel.edu , you'll find everything organized like regular books and articles - closed, linear and isolated. Great for reading as we normally do.

When you click on the 'visualize' tab, you'll see something similar to an Obsidian knowledge graph, where ideas are scattered around.

In later versions, the individual events will have their own networks.

So again, these event kinds are helpful for data organization, and for future customization to create knowledge graphs and find ideas, books, aricles, etc, that are related to one another.

Kind 30041 is basically a bunch of scattered events that you can search through beyond a single book. Like regular text search of kind 1.

On the other hand, kind 30040 creates the structure of a book for regular reading.