2016-02-25 AD-Hoc: Meeting Notes on Common Accord

Owned by Mark Lizar (Unlicensed)
Last updated: Feb 25, 2016
3 min read

Date

Feb 25, 2016

Attendees

Review Common Accord - For consent regulation and requirements

  • key problem in creating a consent management framework (beyond a standard record)  is to track all the regulations once consent moves attributes from domain to domain
    • a solution approach would be to make all regulations and requirements open, perhaps using common accord.  This would enable open validation of consent legal requirements
  • Jim :
    • describe what common accord is - way to capture legal regulations in open reusable, referencable way.
    • focus on legal documents - people take a regulation and write  a  policy/contract/ terms etc.
    • legal interaction - is always one or more documents.
    • common accord - allows to go to a common source and find the document - reference the url - then complete it with identity - via URL, competed non-discure.
  • Block chaining  - open sources the infrastructre of transacting.  - like an email thread - for persons to engage in commmunications by themselves , and move token of values on it, and program it to setup conditions.   - but cant do anything legal.  - add into record, a couple of key values and a link to something - then this can be chained to a smart contract - i.e.
  • Consent Receipt - could have an additional key value that referenced a common accord URL  - in the interface - which read the consents - could have a one button, that could expand the consent receipt into a full text.
  • Reverse way -
    • create a system that would generate consent based on criteria of legal regulation in a jurisdiction
    • Has text in it based on people completing a dialogue
  • Use case - a plugin - that can make a receipt at the button on the form
    • ppl may say where they are  - lets assume EU -
    • generate consent receipt based on information that the user has typed in
    • generate text provided to user and saved by the site
    • receipt has embedded links -  links go to resources that tells you things about the consent
    • we need a place for these legal references
    • restating the legal consent matrix, that is more granular can happen with Common Accord
  • Harry - brings up use acse about the T&C's contract for sale and return vs. privacy policy and its purpose for use with organisation backend
    • if this is distributed - will there be many version of this contract?
      • the two parties can make the changes to the text of the contract and then agree
      • converging - by not making a whole new document but having it in components it can be re-used
        • can be used with targets.
      • Open Source - how to use partially agreement to get to something like rolling convergence
    • Many purposes for data use - creative common example of boiling down 25 page policies into a set of icons
      • open cource is not such a straightjacket approach, the Common Accord way, enables that there is a policy, and that these policies can be changed and a button can show changes
  • Jim - privacy policies are documents written from regulation
  • Interesting - Privacy Policy
    • but the source code for the privacy policy
  • Mark - importantly for the MVCR
    • just having a data controller contact usable at point of consent to ask questions makes the consent more compliant than exists now - just through  receipt provision
    • but
      • in order to see if a consent receipt can validated against legal regulations, to show if it is compliant - is a minimum bar for an org to provide receipt (legally)
      • starting with linking to consent regulations by jurisdiction will open up this discourse and open innovation, with it, then the MVR can be verified against law as well as tech specification
  • Jim - up for making a repo for the MVCR and puttting in legal requirments across regiems
  • Mark - will send across spreadsheets, and we can make a document for - how to add requirements that the a consent receipt can be validated agains.

 

Discussion Items

TimeItemWhoNotes
    

Action Items

  •