- From: ianbjacobs <notifications@github.com>
- Date: Tue, 11 Apr 2023 12:23:05 -0700
- To: w3c/webpayments <webpayments@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 11 April 2023 19:23:11 UTC
I have an alternative proposal. It looks like there are four main issues. Rather than add this to the generic WG repo, how about instead we raise the issues on the relevant specification? For the background / assumptions, perhaps we could create a new document in the payment-handler repo on privacy assumptions and requirements. We could even model it after what we did for SPC: https://github.com/w3c/secure-payment-confirmation/blob/main/requirements.md I'm not suggesting that we do a full requirements exercise, only that we create a repository for them and start with what you've identified. I'm happy to create this document, which could then be referenced from the individual issues. Thoughts? Ian -- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/pull/261#issuecomment-1503973670 You are receiving this because you are subscribed to this thread. Message ID: <w3c/webpayments/pull/261/c1503973670@github.com>
Received on Tuesday, 11 April 2023 19:23:11 UTC