WICG
[TAG] Naming and registry maintainence
Some operation names are common with the Permissions API. It'd be great to understsand how these will be maintained and kept in sync as new operations are added. Should the TAG be assisting?
Are there going to be operations that will be budget-able but wouldn't also be introspectable via the Permissions API? As registries are an open problem for web specs, we'll ping back when we come up with a solution.
The same values should be reused wherever possible. Using the same enumeration is impractical because, while there is some overlap, neither is a superset of the other, which would lead to exceptions.
The specification has a note on this: https://wicg.github.io/budget-api/#operation-type-enum
