Re: Use Cases document

Thanks for sending this out, Marta. I am preparing a list of use case elicitation questions whereby I hope to interview as many business partners as possible for viable use cases in Financial Services (Insurance/Annuities in my case). I don't know if these really belong in the document attached, but here is a start of the things I'd ask. This may help others seeking viable use cases. Tried to make these questions semi-business friendly. If it makes sense to the group, perhaps a 5 minute discussion next time will help expand upon this starter set. 
Thanks, Colleen
Do you/we have a need for:
Transactions that are irrevocable? (Transactions that can be proven to be irreversible?)Transactions that where we need to prove that nothing was altered?Where everyone who is a part of a “community” or block can see what has transpired?Where we need to track tangible or intangible items/assets?Where we want to drastically reduce the number of “middle men” and toll gates required in a current transaction?Where there is a fixed pool of assets/objects that we want to ensure are not “spent” twice?Where we want to transcend the jurisdictions of geography when transacting?Where we care about highly secured methods of transacting? 

    On Friday, February 10, 2017 11:26 AM, Marta Piekarska <marta@blockstream.io> wrote:
 

 Weekly snapshot

Please contribute. I have added the role diagram.

Have a great day
m



—
Security Architect @ Blockstream

mp@blockstream.com

+491703311307 (Germany)
+14159608938 (U.S.)
Signal, Wickr (martap)

> On Jan 11, 2017, at 9:45 PM, Lemieux, Victoria <v.lemieux@ubc.ca> wrote:
> 
> Many thanks for sending this out Manu.
> 
> Best wishes,
> Vicki.
>> On Jan 11, 2017, at 10:26 AM, Manu Sporny <msporny@digitalbazaar.com> wrote:
>> 
>> Hi all,
>> 
>> As promised in the Blockchain CG call, here is a template for our Use
>> Cases document:
>> 
>> https://docs.google.com/document/d/1BNKQ-hNFIpROyzQRig7a7kTBcmclAQlbv3MCCZfhHiE/edit#
>> 
>> We will eventually move this content into a proper W3C spec format, but
>> have found it useful to collaborate in Google Docs at the beginning
>> (instead of wiki or ReSpec) because:
>> 
>> * It's easier to comment on text and make suggestions
>> * It's easier to suggest changes w/o changing the document text
>> * It's easier to get participation from non-technical contributors
>> 
>> Anyone may make comments on the document above. Marta, Vicki, Vagner,
>> and I are editors of the document right now, but if you want to be added
>> as an editor, just ask.
>> 
>> -- manu
>> 
>> -- 
>> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
>> Founder/CEO - Digital Bazaar, Inc.
>> blog: Rebalancing How the Web is Built
>> http://manu.sporny.org/2016/rebalancing/
>> 
> 
>