Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extra Guidelines #5

Open
zicklag opened this issue Jul 21, 2024 · 0 comments
Open

Extra Guidelines #5

zicklag opened this issue Jul 21, 2024 · 0 comments

Comments

@zicklag
Copy link
Collaborator

zicklag commented Jul 21, 2024

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant