Difference between revisions of "CoronaRiskScoring (Q4684)"
Jump to navigation
Jump to search
(Changed claim: partner (P137): unknown value) |
(Created claim: prospect (P368): AlgorithmWatch (Q2217)) |
||
| Property / prospect | |||
| + | |||
| Property / prospect: AlgorithmWatch / rank | |||
| + | Normal rank | ||
| Property / prospect: AlgorithmWatch / qualifier | |||
| + | |||
Revision as of 07:41, 28 May 2020
project addressing risk scoring algorithms in contact tracing apps
| Language | Label | Description | Also known as |
|---|---|---|---|
| English |
CoronaRiskScoring
|
project addressing risk scoring algorithms in contact tracing apps
|
Statements
0 references
0 references
unknown value
0 references
unknown value
0 references
unknown value
while AppCensus can't really help with risk scoring directly, they can help with auditing the functioning: input data as well as what gets exfiltrated, both through the app and through Bluetooth
0 references