Skip to content

More precisely define the contribution budget and window in the spec #141

Open
@alexmturner

Description

@alexmturner

The spec currently leaves the budget as fully implementation-defined (see here). The explainer, however, describes Chrome's implementation plan.

While it may be difficult to align on exact details across implementations, we should probably define the privacy unit more precisely while leaving some key parameters as implementation-defined (e.g. the precise epsilon/budget and perhaps the timespan used in the privacy unit).

Metadata

Metadata

Assignees

No one assigned

    Labels

    specRelated to specification/standardization

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions