(all in one file)
=== 30 Mar 2022===
- attendants: vitor jesus (Unlicensed) Tadej Fius (Unlicensed) Salvatore D'Agostino (Unlicensed) Crt Ahlin jim pasquale Former user (Deleted)
- calls will take a break until (expected) mid/end of May to progress offline work
- core spec
- software proof of concept
=== 17 Mar 2022===
- attendants: vitor jesus (Unlicensed) Tadej Fius (Unlicensed) Salvatore D'Agostino (Unlicensed)
- apologies: Crt Ahlin Jan Lindquist (Unlicensed) jim pasquale
- architecture of the proof-of-concept as a web3 application
=== 10 Mar 2022===
meeting postponed, due to lack of availability of members.
===3 Mar 2022===
- attendants: vitor jesus (Unlicensed), jim pasquale Salvatore D'Agostino (Unlicensed)
- apologies: Jan Lindquist (Unlicensed) Crt Ahlin Tadej Fius (Unlicensed)
- google doc has now some content: https://docs.google.com/document/d/1McwATIvRBBO7GJruWT5PmbHO1QKEjn9tYyP3GOI0NM0/edit#
- WG/project housekeeping
- CRWeb receipt as an extension of PDUR?
- demo of a browser extension abel to detect a receipt opportunity, web semantics (JSON-LD) and generate + display a user receipt
===24 Feb 2022===
- attendants: vitor jesus (Unlicensed), Salvatore D'Agostino (Unlicensed) , Jan Lindquist (Unlicensed)
- apologies: jim pasquale
- google doc leading to the spec at https://docs.google.com/document/d/1McwATIvRBBO7GJruWT5PmbHO1QKEjn9tYyP3GOI0NM0/edit#
- allocation of tasks on the doc
- discussion on terminology and workflows/lifecycles
===17 Feb 2022===
- attendants: vitor jesus (Unlicensed), Jan Lindquist (Unlicensed), Salvatore D'Agostino (Unlicensed), Jeff Corrigan. Tadej Fius (Unlicensed)
- apologies:
- welcoming Jeff Corrigan and pointing out formalities
- there's now a working json of the receipt structure
- current list of fields (xls)
- notion that a next gen receipt needs two components:
- bidirectionality, so a protocol user/controller can be devleoped (e.g., signing)
- hooks to external services (e.g., obtaining keys, identities, risk rating)
- open sourcing code is supported by all
- Jeff suggests posting code + docs under AWS but not locked to AWS (as a reference implementation and forkable) - similar to this.
- forward: procude some text in the spec --> code --> finish spec
- list of fields
- dev team will do code outside the regular calls and report back
Actions:
- create spec structure in gdocs
- setup meeting with devs
===10 Feb 2022===
- attendants: Jan Lindquist (Unlicensed) Črt Ahlin, Salvatore D'Agostino (Unlicensed) jim pasquale
- apologies: vitor jesus (Unlicensed) Former user (Deleted) Former user (Deleted) Former user (Deleted)
Agenda
1) intros
2) review active deliverables
AP: create a document that can be used for a hackathon for the next meeting
https://www.wearemillions.online
4. Receipt format (Vitor)
5. Event handling (Tadej)
6. Security (Tadej)
- Use Case (Črt)
3) demo preparation
4) other topics of interest
Notes ahead of the meeting
- a new file with fields with an added column about
- where each field is sourced from
- whether it is independently obtained by the user (or browser user-agent) such as "on Behalf of PII Principal", "keys")
- whether it comes directly from the Controller via JSON in the HTNL (that the add-on detects)
- whether it is mutually agreed using a protocol (complexity of it to be discussed) - e.g., the Privacy Notice hash needs to be sent by the Controller bu verified by the User - both do hashes and confirm they match)
- whether the information could/must come from a third-party (a directory, registry, blockchain, etc)
- where each field is sourced from
===3 Feb 2022===
- attendants: vitor jesus (Unlicensed), Jan Lindquist (Unlicensed), Črt Ahlin, Salvatore D'Agostino (Unlicensed)
- apologies: Former user (Deleted), jim pasquale, Former user (Deleted)
- The call was moved to a different time (2pm/GMT, 9am/ET) which caused agenda conflicts
- Brief catch-up on the work
===27 Jan2022===
call did not happen due to agenda conflicts
===20 Jan2022===
- attendants: vitor jesus (Unlicensed) , Former user (Deleted) , Črt Ahlin, tadej.fius@datafund.io,jim pasquale,Salvatore D'Agostino (Unlicensed), Tadej Fius (Unlicensed)
- apologies: Jan Lindquist (Unlicensed)
- continue the overview of 1st draft receipts field (link TBA)
- reviewed and scoped with group comments CRWeb receipt format (13jan22 version - crweb-receipt-format-20220113.xlsx)
- Tadej Fius (Unlicensed) to create a first iteration of the data model → the data model will raise missing details and specifics (e.g., what is excatly a "key")
- IIW will be the end of April (show whatever we'd like) This session will be in-person what to present?
- How does the lifecycle get addressed (Vitor will elaborate in the roadmap) Lifecycle manager not part of the receipt
- the record or receipt should only include key information per the kind of consent as an extension of CR 1.1
- @Črt There will also be work done on registries as part of Fair Data Protocol; juyst FYI at this point, but at one stage I see the structure of the receipt "registered" in this way: https://github.com/fairDataSociety/FIPs/blob/master/text/0001-fdp-roadmap.md
- rough roadmap for the essentials of the spec:
- Working prototype (in the sense of "Minimum Viable Concept/Product") by mid Feb. This is a website, add-on, html semantics, receipt record
- This work to feed ideas (by end of Feb) and a potential participation in https://www.wearemillions.online (1-21 March)
- from here we develop the more advanced concepts such as lifecycle etc
===13 Jan2022===
- attendants: vitor jesus (Unlicensed) , Salvatore D'Agostino (Unlicensed) , Former user (Deleted) , Črt Ahlin, jim pasquale
- continue the overview of 1st draft receipts field (link TBA)
- reviewed and scoped with group comments CRWeb receipt format (13jan22 version - crweb-receipt-format-20220113.xlsx)
- vitor jesus (Unlicensed) to create a template JSON of the current iteration of the receipt spec
===06Jan2022===
- to clarify: no meetings on the 23rd and 30th
- attendants: vitor jesus (Unlicensed) , Jan Lindquist (Unlicensed) , Salvatore D'Agostino (Unlicensed), Former user (Deleted) , jim pasquale
- Regrets Former user (Deleted), @crt.ahlin@datafund.io, tadej.fius@datafund.io
- overview of 1st draft receipts field (link TBA)
- reviewed and scoped with group comments CRWeb receipt format (crweb-receipt-format-20220112.xlsx)
===23 & 30Dec2021===
No meetings over the Christmas New Year Holiday
===16dec2021===
- attendants: vitor jesus (Unlicensed) , Jan Lindquist (Unlicensed) , Salvatore D'Agostino (Unlicensed), Former user (Deleted) , jim pasquale
- clarifications about roadmap and scope
- admin and housekeeping
- Jan's presentation to DIF: https://youtu.be/Mq4oXEaOTwg
- next week:
- clarify the status of the group
- create a working document with fields for the CRWeb Receipts
===9dec2021===
Review CR 1.1
https://github.com/KantaraInitiative/consent-receipt-v-next/issues/13
...
Consent lifecycle What and How (open item to be fleshed out)
===2dec2021===
...
- attendees - VJ, TF, SA, CA
- discussion around security and authenticity in receipts
===25nov2021===
- CRWeb’s specification and companion docs – CRWeb-ToC-20211125.pdf shows an outline
- CRWeb will also deliver a proof-of-concept to demonstrate the concepts. A kick-off proposal for the architecture is in the attachment as well
- Browser add-on listens to events
- HTML contains metadata (e.g., Controller info) in JSON-LD
- JSON-LD contains the name of the html artifact associated with the receipt event
- A discussion on the protocol itself, considering authenticity and accountability: how to authoritatively architect the transactions?
- Andrew to circulate a doc with ideas
- VJ’s paper on that: “Web of receipts”: https://ieeexplore.ieee.org/document/8974193
- Next week we’ll take some time to advance this particular aspect
- Event id, with provable order, will need nonces, timestamps, UUIDs, versioning, etc.
- This will further support the notion of a Consent Lifecycle
- Decentralised approaches of high interest to the group – they should be seamlessly supported as a use-case (including to facilitate auditability)
- Receipts should be aligned with what is expected from ISO 27560 (and ideally feed into it)
- VJ to send an early schema of a receipt to get started. CR1.1+datafund extension should be a starting point.
...