search

corona-warn-app / cwa-documentation

Project overview, general documentation, and white papers. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
3.28k stars 346 forks source link

Outdated links in transmission_risk document #838

Closed MikeMcC399 closed 1 year ago

MikeMcC399 commented 2 years ago

Where to find the issue

Describe the issue

Some links in the document Epidemiological Motivation of the Transmission Risk Level from the CWA Team, dated 2020-10-12 are outdated.

Document body

The link CWA Architecture is supposed to go to the anchor #risk-score-calculation which no longer exists, so the document is opened at the top.

Literature section

The link Apple, and Google. 2020a. “Exposure Notifications Android Api Documentation V1.3.2.” 2020. produces a 404 error.

Suggested change

In general it needs to be decided whether this document is frozen or should be updated.

If it is to be updated, then the following changes could be considered:

  1. Change links to https://github.com/corona-warn-app/cwa-documentation/blob/main/solution_architecture.md#risk-score-calculation to use the renamed anchor #risk-calculation.

  2. The document Apple, and Google. 2020a. “Exposure Notifications Android Api Documentation V1.3.2.” 2020. is no longer available online and has been replaced by the web documentation on https://developers.google.com/android/exposure-notifications/exposure-notifications-api.

MikeMcC399 commented 2 years ago

It would be good for the Open Source Team to comment how this should be handled, for instance:

ahodzic2 commented 2 years ago

@MikeMcC399

Is this still needed, would like to assist if there has been any update on how to approach this.

MikeMcC399 commented 2 years ago

@ahodzic2

if there has been any update on how to approach this.

Thank you for your offer. There is no update. If there had been an update, then it would have been posted here.

There will be no progress unless the Open Source Team (of which I am not a member) responds to the issue and gives an opinion. Lack of comment so far means no change.

ahodzic2 commented 2 years ago

@MikeMcC399 Understood!

@dsarkar - Are you able to provide input on how you see fit to proceed?

svengabr commented 2 years ago

I will discuss this internally

GisoSchroederSAP commented 2 years ago

I'll take over this issue and discuss with the PO and DEV team lead. Will post the decision and further steps here as soon as I have news.

GisoSchroederSAP commented 2 years ago

Document links, affected documents and this GitHub issue have been named to responsible RKI team. They are taking this over. It sounds to me, they will make small adjustments and will post the updated document version then.