ecordell05/19/2022, 1:37 AM
. This proposal makes a distinction between the policy/attributes associated with a relationship (which would be provided when the relationship is written) and attributes that you provide at query time to evaluate against the stored relations. > How are these attributes expressed? TBD, but ideally in a way that won't tank cache hit ratios. I would think something datalog-y so that rule evaluation is order-independent, but we don't have any concrete proposal yet. > Do you plan to support different data types for these attributes? Also TBD, but probably. Distinguishing time at a minimum seems valuable to me, but other folks may have other ideas.