Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Conversation

pascal-brause
Copy link
Contributor

Description

First consent screen for ticket validation.

Link to Jira

Mainstory: https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-10350
Subtask: https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-10542

Screenshots

10542-1
10542-2
10542-3
10542-alert

10542-1-dark
10542-2-dark
10542-3-dark
10542-alert-dark

@pascal-brause pascal-brause added the task part of a feature label Nov 16, 2021
@pascal-brause pascal-brause added this to the v2.15.0 milestone Nov 16, 2021
@pascal-brause pascal-brause requested review from a team November 16, 2021 13:08
Copy link
Contributor

@CV113 CV113 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UA approved

@vaubaehn
Copy link

Hi @CV113 and @mlenkeit
I'm not 100% sure, but I think the consent is missing something important:
There may be 3 different parties involved: CWA, vendor and the authorized validation service (public or private). (See: https://ec.europa.eu/health/sites/default/files/ehealth/docs/covid-certificate_traveller-onlinebooking_en.pdf#%5B%7B%22num%22%3A25%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22XYZ%22%7D%2C62%2C440%2C0%5D)
From the text of the consent, it looks like data is only processed by app (CWA) and vendor.
Could you check whether it's necessary to integrate information about the validation service, too?
Thank you ❤️

@mlenkeit
Copy link
Member

I think the consent is missing something important: There may be 3 different parties involved: CWA, vendor and the authorized validation service (public or private).

@vaubaehn the legal relationships between all involved parties for the Ticket Validation feature have carefully been reviewed by legal experts and were taken into consideration by them when the legal texts were created. 😉

@vaubaehn
Copy link

vaubaehn commented Nov 16, 2021

@mlenkeit

@vaubaehn the legal relationships between all involved parties for the Ticket Validation feature have carefully been reviewed by legal experts and were taken into consideration by them when the legal texts were created. 😉

Thank you for having a look - then I don't want to be more papal than the pope 😁

…r' into feature/10350-ticketvalidation-consent/10542-consentScreen

# Conflicts:
#	src/xcode/ENA/ENA/Resources/Localization/de.lproj/Localizable.strings
…r' into feature/10350-ticketvalidation-consent/10542-consentScreen
…r' into feature/10350-ticketvalidation-consent/10542-consentScreen
…r' into feature/10350-ticketvalidation-consent/10542-consentScreen

# Conflicts:
#	src/xcode/ENA/ENA/Resources/Localization/de.lproj/Localizable.strings
@pascal-brause pascal-brause merged commit 74570c5 into feature/10350-ticketvalidation-consent/10405-coordinator Nov 17, 2021
@pascal-brause pascal-brause deleted the feature/10350-ticketvalidation-consent/10542-consentScreen branch November 17, 2021 16:20
@vaubaehn
Copy link

Could you check whether it's necessary to integrate information about the validation service, too?

Just realized that my question was a valid one, and that there is additional information regarding the validation service, when getting a seperate consent II to submit data to the validation service.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
task part of a feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants