Traceability Use Case


Aaron Benningfield <aaron.b.benningfield@...>
 

Hi Folks, 


The document link follows. There were a number of good comments provided in the document's critique by Clive, Mahesh and Oleg. I have left the critique embedded in the document and tried to annotate how I addressed the critique. The main way I responded was to ensure the context of the critique was answered at a high level. There are too many permutations, complexities etc. that prohibit a more granular response and I believe the reviewers agreed with me on this point.


Please review once more and let me know if you feel the critique has been properly addressed by Tuesday 11APR. Otherwise, I would like to have this promoted to the appropriate use case status (e.g., Milestone 1) and continue driving it to completion.  


https://docs.google.com/document/d/1V0WpEggrHrBNaCL_gQrynqqmFaT3cNQw6hj1AhfkTPk/edit?usp=sharing


@Oleg,

Do you have a few minutes to discuss on moving this forward.


Thank you,

Aaron Benningfield

208.585.1798



Aaron Benningfield <aaron.b.benningfield@...>
 

Hi Folks,


Will be a little late to the meeting today. I have a client meeting that will spill over somewhat.


From: hyperledger-requirements-wg-bounces@... <hyperledger-requirements-wg-bounces@...> on behalf of Aaron Benningfield <aaron.b.benningfield@...>
Sent: Thursday, April 6, 2017 8:35:44 PM
To: hyperledger-requirements-wg@...
Subject: [Hyperledger-Requirements-WG] Traceability Use Case
 

Hi Folks, 


The document link follows. There were a number of good comments provided in the document's critique by Clive, Mahesh and Oleg. I have left the critique embedded in the document and tried to annotate how I addressed the critique. The main way I responded was to ensure the context of the critique was answered at a high level. There are too many permutations, complexities etc. that prohibit a more granular response and I believe the reviewers agreed with me on this point.


Please review once more and let me know if you feel the critique has been properly addressed by Tuesday 11APR. Otherwise, I would like to have this promoted to the appropriate use case status (e.g., Milestone 1) and continue driving it to completion.  


https://docs.google.com/document/d/1V0WpEggrHrBNaCL_gQrynqqmFaT3cNQw6hj1AhfkTPk/edit?usp=sharing


@Oleg,

Do you have a few minutes to discuss on moving this forward.


Thank you,

Aaron Benningfield

208.585.1798