<red40_> Yes. I'm here.

<mountie_> scribe: mountie

<mountie_> marta: now we start F2F meeting. working building document

<mountie_> marta: competition is good. but good standard will increase echo or unified system.

<mountie_> marta: started at Lisbon, during the TPAC, decided to make usecase document

<mountie_> marta: collected usecases. created document. hope to finalize the document today.

<mountie_> scribe: mountie_

marta: thanks to Jean hosting this meeting.

jean: talking about today's schedule.

favier: french association for blockchain, Le Cercle Du Coin
... launched association in Dec 2015

webex link : https://meetings.webex.com/collabs/#/meetings/detail?uuid=MD6NHOIUEEBQ6JAFG0B7PBCUYZ-101R9&rnd=463103.03375

marta: introduce each other.
... security architect at blockstream. working on HyperLedger also.

allen: principle architect in blockstream

jean: canton-consulting

adrianS: Czam

<marta> https://docs.google.com/document/d/1BNKQ-hNFIpROyzQRig7a7kTBcmclAQlbv3MCCZfhHiE/edit?usp=sharing

members are introducing himself

marta: now the topic is Use Cases

allen: can we talk about high-level of use case document?

<nba> I missed the link to it, just joined (Nicolas)

<Jean-Yves> https://docs.google.com/document/d/1BNKQ-hNFIpROyzQRig7a7kTBcmclAQlbv3MCCZfhHiE/edit?usp=sharing

<nba> thanks

allen: considering other case append-only database. what is different?

nicolas: talking public/private blockchain

adrian: suggest sharing interests

<ChristopherA> https://www.w3.org/2016/04/blockchain-workshop/report.html

<ChristopherA> From that report, in particular the "commitments" graphic.

<ChristopherA> two sources for others who have worked on use case: https://wiki.hyperledger.org/groups/requirements/use-case-inventory

<ChristopherA> https://www.linkedin.com/pulse/84-known-blockchain-use-cases-mark-morris

<Adrian_SAuzade> Here te list i was refering : https://www.linkedin.com/pulse/84-known-blockchain-use-cases-mark-morris

<mountie> mountie: we are talking about the blockchain that is implemented, proved, verified at cryptocurrencies

<mountie> scribe: mountie

allen: approach from top to down

jean: don't use too much time for definition. touch usecase first, comeback to definition.

moving to Introduction part of usecase

nicolas: any scopes limited?

marta: it depend on CG's decision

https://www.w3.org/2016/04/blockchain-workshop/report.html

allen: summarize commitments of workshop : https://www.w3.org/2016/04/blockchain-workshop/report.html#commitments

usecases of hyperledger is different

marta: summarize levels of use cases: https://lists.w3.org/Archives/Public/public-blockchain/2017Mar/att-0012/Blockchain_Use_Case_Development_W3c.pdf

usecase Level1 : user needs based on key blockchain characteristics

level2: common features - architecture backbone for sectors and domains
... identity management, audit trail, time stamp, linking

jean: confused level1 and level2

level3 is for vertical sectors

trying to add consensus, autonomus vs real world assisted, transaction proofs, micro service architecture with decentralized ledger to Level 2 as common feature

vertial sectors as level3 : telecom, financial, government, manufacturing, retail, utilities, healthcard, hospotality, other

adding more to level3: investment banking(stock issue), Trade Finance, Consumer Banking

adding "investment banking(stock issue), Trade Finance, Consumer Banking" to level4 (not level3)

level4 is sub domains of vertical sectors

level4: Financial(Investment banking (stock issue), Trade Finance, Consumer Banking (P2P payment), Insurance)
... Government (public records, non public records, compliance)
... Supply Chain under Manufacturing sector

at level4: Energy, telecom, Water & Waste, Emission Reduction under Utilities sector

at level4: Insurance payment, manufactured products, professional services under Healthcare sector

at level4: Tracking, Coupons & Discounts under Marketing sector

jean: is compliance subdomain of Government?

at level4: Compliance, Certification under Legal sector

marta: moving to Level5

allen: I have over 85 use cases for level5

marta: agenda: 1. usecase, 2. prioritization of usecase, 3. terminology and definitions, 4. collaboration with ISO, 5. plan for the next 6 months

adli: what blockchain should be?

allen: wallet, data formats, protocols...

marta: after creating use case document, try to set priority from the cases
... we have chance to collaborate with ISO

<ChristopherA> https://wiki.hyperledger.org/groups/requirements/use-case-inventory

mountie: is the usecase for hyperledger specific?

allen: not true

marta: narrow to internet applicable

<ChristopherA> https://www.linkedin.com/pulse/84-known-blockchain-use-cases-mark-morris

<ChristopherA> https://bravenewcoin.com/news/moodys-new-report-identifies-25-top-blockchain-use-cases-from-a-list-of-120/

talking selected potential blockchain usecases from moodys

adrian: the usecases of moodys are for corporate.

allen: need more peer-to-peer or user centric usercases

mountie: user agent can be the center of transactions or block transfers of nodes.

collecting more P2P usecases

mountie: solving same-origin policy restriction of Web with blockchain

talking more for P2P usecases

<scribe> scribe: mountie

mountie: by the today morning's discussion, we need to focus more on user centric, p2p use cases. i think

allen: suggesting Self-Sovereign Blockchain Principles
... the principles will help to user centric use cases
... peer means server and user

working on use case document focusing on user centric cases

continue work on use case ( https://docs.google.com/document/d/1BNKQ-hNFIpROyzQRig7a7kTBcmclAQlbv3MCCZfhHiE/edit# )

user centric use cases under discussion are

scribe: .hold people accountable & present accountability
... discover information that enables me to communicate while preserving privacy
... choose the level at which I reveal my identity
... be a subject in the loop of the transaction
... have independence from the other parties
... preserve my resilience
... create cooperative organizations
... have censorship resistance
... choose the level of participation ->permissioned/private/public blockchain
... have low economic barrier
... be able to exchange any kind of asset
... choose appropriate context/reputation
... be able to cross the organizational and jurisdictional domain origins with preservation of the privacy and access to data rules set by me (the user)

marta: now we have direction
... we have no concall at this week.

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: mountie marta adrian adli favier jean floreng nicolas colin robic adrianS antoine red40_ fabrice allen
Found Scribe: mountie
Found Scribe: mountie_
Inferring ScribeNick: mountie_
Found Scribe: mountie
Inferring ScribeNick: mountie
Found Scribe: mountie
Inferring ScribeNick: mountie
Scribes: mountie, mountie_
ScribeNicks: mountie_, mountie

WARNING: No "Topic:" lines found.

Got date from IRC log name: 24 Apr 2017
Guessing minutes URL: http://www.w3.org/2017/04/24-blockchain-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report