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.

Sign up for GitHub

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

Improving description of contribution limits #85

Merged
merged 1 commit into from
Jul 13, 2023
Merged

Improving description of contribution limits #85

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -446,10 +446,12 @@ propose the following structure. See [below](#implementation-plan) for the
specific choices we have made in our current implementation.

First, each user agent will limit the contribution that it could make to the
output of a query. In the case of a histogram operation, the user agent could
bound the L<sub>1</sub> norm of the _values_, i.e. the sum of all the
contributions across all buckets. The user agent could consider other bounds,
e.g. the L<sub>2</sub> norm.
outputs of aggregation service queries. (Note that this limitation is a rate
over time, not an absolute number, see [Partition choice](#partition-choice)
below.) In the case of a histogram operation, the user agent could bound the
L<sub>1</sub> norm of the _values_, i.e. the sum of all the contributions across
all buckets. The user agent could consider other bounds, e.g. the L<sub>2</sub>
norm.

The user agent would also need to determine what the appropriate
'partition' is for this budgeting, see [partition choice](#partition-choice)
Expand Down