Re: Use Case Refactoring v1.0

There's a couple of XML structures http://en.wikipedia.org/wiki/List_of_XML_schemas (ie retailxml) that give more detail to the needs of a digital receipt, however. Should it just be required to include transactional information in a linked-data format? 

Perhaps in-turn encouraging industries to build their own ontologies for use in local markets...?

Timh
Sent from my iPad

> On 25 Apr 2014, at 12:51 am, Andrew Mackie <andrew@supplydemand.info> wrote:
> 
> Following a conversation with Manu and Brent last week, I've started the task of categorizing the use cases from a conceptual standpoint in order to ensure that a) we include every use case that we need and b) the final set of use cases is well structured to aid understanding. 
> 
> To do that, I have taken all of the current use cases (from https://www.w3.org/community/webpayments/wiki/ClassifiedWebPaymentsUseCases_r1) and put them into a mind map to determine and map out their structure. 
> 
> The first version of this mind map file (.mm) and an XHTML export of that file can now be found here - http://www.supplydemand.info/blog/web-payments/
> 
> As you can see, I've added a number of comments and questions and I've identified a number of gaps that we need to fill in. I will continue to play with the structure - in the meantime I appreciate your comments, answers, identification of gaps and so on. Once I've cleaned it up some more and incorporated this initial feedback I'll find a way to open it up for a more immediate / open form of collaboration (and any suggestions on the best format are welcome!).
> 
> Cheers,
> Andrew 
> 
> -- 
> Andrew Mackie
> website: www.supplydemand.info
> twitter: @SupDemand