TPAC2016 BlockchainCG meeting report
Posted on:IRC Minutes
- minutes : https://www.w3.org/2016/09/20-blockchain-minutes.html
- minutes are incomplete
- IRC log : https://www.w3.org/2016/09/20-blockchain-irc
Agendas
- https://lists.w3.org/Archives/Public/public-blockchain/2016Sep/0084.html
- adding update mission statement
- use github issues with labels
- accepting proposals
share workshop report
- https://www.w3.org/2016/04/blockchain-workshop/report.html
- we will start to discuss
- what is missing point
- invite more stakeholders
- missing from the workshop: solid next steps, key stakeholders.
participants
- Jeff Jaffe, W3C
- Bruno Javary, Oberthur technologies
- Kaoru Maeda, Lepidum
- Rodolphe Marques, BigchainDB
- JP Abello – Nielsen & IoTC Privacy & Security
- Digital Bazzar
- Reuter
- NTT
- University of Oslo
- Blockstream
- W3C
- CITI
- Newcastle University
- Mtreecare
- Bocoup
- Riccardo Spagni, Monero
- see IRC history
relationship with other groups
- groups
- HyperLedger
- Digital Assets
- Verifiable Claims
- Web Payments
- goal : co-activity
Use Cases
- focusing to web only or wider?
- at least web-relevant
- not cut-off discussion
- check what members are doing
- will CG harmonize or collaborating with other groups?
- discuss at online first, then talk details at F2F meeting
- co-working with browser vendor at early stage (comment by harry)
- use workshop result
- usecases on IRC
- USE CASE calculating Weighted Centrality
- USE CASE anonymised deterministic passport real-time status validation on travel
- USECASE: hyper system centralized and de-centralized DB(permissioned)
- Use Case: for natural disasters/emergency skill systems: running a ledger with no “servers”- distributed networking. Network discovery/mngment from the browser, or maybe over BLE?
- USE CASE (Marta) Tracking data that’s shared on the Web, and measure who’s accessing it
- USECASE: Blockchain use by the Music industry: https://medium.com/cuepoint/how-the-blockchain-can-change-the-music-industry-part-2-c1fa3bdfa848#.m462v6ppa
- USE CASE Preventing fraud in the insurance industry (by registering insurance claims on a blockchain / shared database)
- Use Case: for natural disasters/emergency skill systems: running a ledger with no “servers”- distributed networking. Network discovery/mngment from the browser, or maybe over BLE?
- USECASE: WOT related BC components
- USE CASE (Marta) Things communicating within IoT
- USE CASE standardized data model for expressing primitives off of blockchain (returned when using a REST API)
- USECASE: rights management, trust management on WEB
- USECASE: Standardized REST API for blockchain access using normal JSON
- Use Case: for wallets, we want some way to store and opporate on keys in a secure way in the client. I believe web cryto is working on this. Will the web crypto group’s APIs suffice for wallets?
- USECASE verify a block is genuine inside a blockchain from a web application
- USE CASE Ensuring that a refugee that is onboarded at one camp can recover their refugee status determination paperwork.
- USE CASE Checking to see if a doctor has their license (or has been debarred)
- USE CASE Seeing if someone has the credentials (training/education) that they say they do
- USE CASE Seeing if a car insurance claim has already been processed (fraud)
- USE CASE Seeing if a digital coupon has already been redeemed (coupon fraud)
- USE CASE Checking to see if an IBAN number has been placed on a government watchlist
- USE CASE verifying if an emergency responder is currently authorized to be onsite
- USECASE: Access to bitcoin wallet securely in the browser for payments
- summarized at https://github.com/w3c/blockchain/wiki/Use-Cases
organization
- mailling list
- github
- homepage
- teleconference
- timing : CG will poll time
- possible two types of teleconference
- general
- technical
- preventing web payments concall time
- pre-notice agenda point at every wendsday
- tool : W3C will provide
- F2F meeting
- November?
- after preparing use-case first
- discuss use-case document
Chainpoint
- its standard format for reciepts
- http://www.chainpoint.org/
who is key stakeholder
- R3
- Banks
- Browser vendors
W3C Plenary Day
- use https://www.w3.org/wiki/TPAC2016/SessionIdeas
- blockchain CG proposal : https://www.w3.org/wiki/TPAC2016/SessionIdeas#Blockchain_Use_Cases
active participants
- encourage local maillinglist like public-blockchain-korean@w3.org
- develop usecases
deliverables
- 3 month : usecases
- **next 3 months** the document
- 6 month : workshop
- **workshop** after we describe the use cases
- then probably a workshop in January
- 9 month : ?
- 12 month : ?
- **next 6/9 months** actual plan for what use cases should be standardized and how these should be created. With that we can propose creating an actual working group or interest group