Some guidelines for the Leaf protocol discussed in chat:
When multiple entities are under a subpath, that subpath should have it's "parent entity" describe the nature of the subpath with appropriate component such as NameDescription, Feed, etc.
When an entity wants to declare a relationship to another entity, such as Following or AuthorsFeed, it should use a component that contains a link to the Feed entity. The specification of the component containing the link explains the relationship that it represents.
We should incorporate URI standards into the Leaf protocol draft. We need to allow building URIs for content addressing, similar to ipfs://, as well as the equivalent to Links, which need to include the ability to specify link resolvers for namespaces and subspaces.
Markdown/HTML components can use the URI standards for links as well as relative paths that resolve to entities in the same namespace+subspace.
Some guidelines for the Leaf protocol discussed in chat: