Page Comparison

• Discussing uses
  
  • uses of exploring
  • use of operations
    • info on practices or assert
• Data Action - 

  • Proposal action

    Discovery action

    Data collection action

    Transfer action

    Use action

    Disposal action

    Memorializing action

    Audition action

  • memoralising action
    • need historical records
      • for purposes of auditing, enforceability, transparency
      • subset of metadata
• Legal Duties
• Look for
• Development Vision
  • a human readable layer
  • machine readable layer
  • legal layer
• Mediation built

• context of sensitive personal information for a schmea
• Mary brings up Swift as a simple version of a Data Schema
  • Need a mid party to memorialise the data transfer
  • SWIFT holds the schemas
• Brings up the Email model
  • Open Standard
• MRSS (Media RSS)
  • as a bad example
• Propose this as a v.1 schema
• Security of the Map
  • leave open until hackathon then make read only
• Does this work into API - or a privacy a protocol

1. Keep

1. Feedback put into all three layeres: Tech, Legal, Machine
2. Feed Forward (should be looked into)
3. Weighted response comes from asking questions like : How much of that happened> Did the contract get fullfilled

Scott: Function of the receipt

• notice and consent is not a negotiation or an empowerment
• Or --> offer and acceptance
• If I am offerring and acceptance,
• Invitation to bid
• What are the dances in the different jurisidictions
• recognising a matter of leal.
• Need consistent interaction around that dance.

Mark - Hack for the issue of notice and consent dance that keep N&C a non empowering structure.

Create the option to show that there is a time limited consent to address the traditional notice and consent problem described above

Mary - (from experience) ability to make a line by line consent agreements for different - System - Purpose, re-use and administration

Logging the Purpose in the UE