[Openid-specs-heart] Proposal for reworked use case AND use case template

Sat Aug 1 23:33:46 UTC 2015

Eve

I am very grateful that you did this exercise as well.  It really gave me a reference framework to hang all of my comments and display my shortcomings in understanding the technology.  It is a great!

I really just put everything I could think of down in writing in the spirit of collaboration – I hope it helps forge a better document and gets me educated so I can be a more effective advocate of the content.  I realized as I went through the second half of the document that the comments I made in the first were being addressed later on so they may be irrelevant.

My most important opinion is that I feel like some of this is what we want the world to be and I tried to add some specific examples of how the world is today to make sure we weren’t fooling ourselves into believing this was more than it is.  I hope that I don’t come across as the last guy showing up to the party but as an earnest contributor with a fresh set of Policy-centric practical perspectives of how things are and what I am reading so that we can iterate and improve the output.

I think it is unclear at a first read that the solution is implementable in a way that the contents of the EMR are not modifiable by the consumer end user and I have some practical questions about how we establish trust that systems are implemented in the way we expect or would consider typical?

Make sense?

Warmest regards,

Aaron Seib

 <http://www.nate-trust.org/> NATE, CEO

@CaptBlueButton

(o) 301-540-2311

(m) 301-326-6843

From: Openid-specs-heart [mailto:openid-specs-heart-bounces at lists.openid.net] On Behalf Of Eve Maler
Sent: Saturday, August 1, 2015 2:34 PM
To: openid-specs-heart at lists.openid.net
Subject: Re: [Openid-specs-heart] Proposal for reworked use case AND use case template

Responding to myself: Regarding your opinions on the comments to the document, of course, you could also just use the GDoc mechanism to actually insert replies to the comments there instead -- duh. I encourage that. Please do that ASAP, and that way we can have an asynchronous "conversation" in the document and hopefully dispatch the comments quickly at the start of the next call where we have consensus.

Eve Maler
ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
Join our ForgeRock.org OpenUMA <http://forgerock.org/openuma/>  community!

On Sat, Aug 1, 2015 at 11:20 AM, Eve Maler <eve.maler at forgerock.com> wrote:

Completing my action item, you'll find our (well-worn :-) use case document here <https://docs.google.com/document/d/1IvbdWerdvMuA1dQ-KQvVKqIBrAas7FoenNVUtgpqYrw/edit?usp=sharing> . Following is my proposal. If we like what I've done here, I recommend that we:

*	Edit the doc title to match the use case title I've supplied (just below the horizontal line).

*	Resolve all the comments above my title (fear not, they're all accounted for in the comments I've inserted) and delete all the text above that point (I've retained all our existing text above the line, just in case).

*	Resolve all the comments I've inserted -- as quickly as possible! We don't have to take up call time to do the minor ones, if people take the initiative to review them offline and supply their feedback as responses to this note. Note that, in this new template, I have avoided the use of the comment mechanism for anything that should be a permanent part of the document.

*	Ask people to write their other use cases in GDoc using this style.

*	Obviously, if you have suggestions on how to improve the template, weigh in! If you want to make invasive suggestions, contact me and we can do a collaborative editing session together.

I'm extremely glad I finally did this exercise, because it caused me to understand more of what we need to consider profiling and more of the "health SME" point of view. And, to be honest (perhaps forestalling a comment from Justin ;-), I don't feel that it was wasteful to go to this degree of mapping to the technologies because it flushed out some mismatches that really didn't make sense to me all this time. I now feel we can go straight to the heart (ahem) of the profiling matter with as many future use cases as we want, and in fact, we can begin profiling and write more use cases in parallel.

Thanks to you all for letting me "get my OCD on".

Eve Maler
ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 <tel:%2B1%20425.345.6756>  | Skype: xmlgrrl | Twitter: @xmlgrrl
Join our ForgeRock.org OpenUMA <http://forgerock.org/openuma/>  community!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20150801/c31dec01/attachment.html>