v3 consent to attribute release : more than per entity ID ?

[Tom Zeller]

On a recent dev call, I asked if consent to release an attribute for a
given relying party would apply to other relying parties, and the
response was pretty much no, which is understandable given how I
asked. However, I came across IDP-96 again, which is a request for
consent to be applied to more than one entity based on some criteria,
probably from metadata.

I bring this up because of client-side storage concerns. If we
supported IDP-96, then it seems we could store the criteria for
matching a relying party in some way besides entity ID to reduce
storage size. But I'm not sure how to do that.

So, I guess my question is, should consent storage be keyed by entity
ID, or something else ? My assumption is that storage should be
per-entity ID, and applying consent to more-than-one entity would be
done by a configured predicate of some sort.

Thoughts ?