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

[Id Coach]

Thanks Eve,

This is wonderful. I questioned/commented on things only a newbie is
likely to ask/care about.

It's also a useful template for other use cases. To your point about
explaining oAuth and other template terms, you're using a new language
and a new ecosystem to many, so I encourage those template terms to be
explained over and over again as needed and as appropriate.

It will be helpful to me to illustrate or diagram this process. I'll
take a crack at that in the next few days (I hope).

  judi

On 8/1/15 11:20 AM, Eve Maler 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 | Skype: xmlgrrl | Twitter: @xmlgrrl
> Join our ForgeRock.org OpenUMA <http://forgerock.org/openuma/> community!
>
>
>
> _______________________________________________
> Openid-specs-heart mailing list
> Openid-specs-heart at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-heart

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