Open degregat opened 4 years ago
I'm fine with that. I think it would help to be able to refer to it from the high level blocks, so just a numbering for that column?
Some additional terms
A/G | DP-3T | PACT (MIT) | PACT (UW) | TCN | Description |
---|---|---|---|---|---|
Broadcasting rotation interval, based on Bluetooth MAC address change interval | Epoch length, variable | Same as Interval Secret rotation | Pseudorandom Identifier Rotation Interval | ||
Diagnosis key | Exposed key, known case key | Report | Key(s) shared publicly and synced locally | ||
Contact | Matching contact, known case key | Doesn't specify matches | Local match of a key shared publicly to a set of encountered pseudorandom identifiers |
I worry about introducing an extra set of terms for the common functionality
Maybe this column should be renamed to "description/definition" and moved to the right side?
Should we say Token, or Pseudorandom Identifier in the building blocks, to be sufficiently general?
Maybe "rolling beacon key" is sufficiently non-ambiguous?
Why not just use the TCN term, temporary contact number?
What's the essence of this term?
Some other ideas:
Google has renamed to DailyTracingKey
to TemporaryExposureKey
The table format is great but I worry about introducing an extra set of terms for the common functionality. Since the keys aren't actually used in precisely the same way in each scheme, I think that there's not a precise definition of what each of the new terms are, which makes me worried about introducing them. But the functionality is clearly analogous, so maybe just not including the first column of the table would highlight the similarity without having to define new terms?