Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Add cypress workflow
samkim
force-pushed
the
rebac-annotations
branch
from
2dc4316 to
1f17f37
Compare
samkim
force-pushed
the
rebac-annotations
branch
from
1f17f37 to
9aeb6cf
Compare
jakedt
left a comment
jakedt
left a comment
There was a problem hiding this comment.
One sentence per line in your markdown content please. I feel like overall this could use a few more iterations on annotation content and how it maps to the highlighted paper sections.
| page-1-col-1: | ||
| what-is-rebac: | ||
| content: | | ||
| What is ReBAC? Relationship-based access control. The term was first coined in 2006 by Dr. Carrie E. Gates in her paper: [Access Control Requirements for Web 2.0 Security and Privacy](https://www.researchgate.net/publication/240787391_Access_Control_Requirements_for_Web_20_Security_and_Privacy) |
There was a problem hiding this comment.
I would take these front-matter annotations, combine them, and just put them all on the Introduction section header.
| page-2-col-1: | ||
| nested-groups: | ||
| content: | | ||
| Authorization services that infer a relationship graph from an existing database schema or map a graph to database tables run into issues with nested groups. Directly storing relation tuples is a key decision that supports nested groups. |
There was a problem hiding this comment.
Citation needed. A group database table with a nullable FK reference to the parent is a perfectly acceptable way to represent a graph of group memberships.
| Authorization services that infer a relationship graph from an existing database schema or map a graph to database tables run into issues with nested groups. Directly storing relation tuples is a key decision that supports nested groups. | ||
| scaling: | ||
| content: | | ||
| Not all applications that use Zanzibar may have Google’s traffic and not all Zanzibar implementations will be scaled to the size of Google’s internal implementation. However, the techniques used in Google’s implementation are still applicable to accomplish the same goals: Correctness, Flexibility, Low latency, HA, and Large scale. |
There was a problem hiding this comment.
I would lower case the list elements and spell out high availability
There was a problem hiding this comment.
Maybe change large scale to future-proof scale
| page-5-col-2: | ||
| zanzibar-annotations: | ||
| content: | | ||
| The following section dives into the internals of the system. See the [Introduction to Zanzibar](#annotations/intro) annotations for commentary. |
There was a problem hiding this comment.
This link didn't do anything for me.
2 participants
No description provided.