[Openid-specs-heart] Vote to Approve Implementer’s Drafts of OpenID HEART Specifications

Mon Feb 8 19:05:50 UTC 2016

Thanks for the corrections, Mike! (I did mean to send out some
"get-out-the-vote" notes last week to everyone, but was taking some time
semi-off, and also using the time to get my inbox under control -- very
glad the process allows for a ballot extension. :-)

For future ballots, I'll make a note to apply my more traditional GOTV
efforts (UMAnitarians will know what I mean...) to ensure rapid/efficient
success.

*Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
New ForgeRock Identity Platform <https://www.forgerock.com> with UMA support
<https://www.forgerock.com/platform/user-managed-access/> and an OpenUMA
community <https://forgerock.org/openuma/>!

On Mon, Feb 8, 2016 at 10:50 AM, Mike Jones <Michael.Jones at microsoft.com>
wrote:

> If you’re joining as an individual member, it’s not a manual process.
> It’s instantaneous and fully self-service.  The price of individual
> membership is US $25.00.
>
>
>
> The manual steps Eve are describing are for first-time association of an
> OpenID with an organizational membership.  For what it’s worth, the
> foundation has contracted for updates to our membership software to make
> this process smoother, but they’re not in place yet.
>
>
>
> But please do vote ASAP.  Don’t take my note above as a reason to wait!
>
>
>
>                                                           -- Mike
>
>
>
> *From:* Eve Maler [mailto:eve.maler at forgerock.com]
> *Sent:* Monday, February 8, 2016 10:26 AM
> *To:* Mike Jones <Michael.Jones at microsoft.com>
> *Cc:* openid-specs-heart at lists.openid.net
> *Subject:* Re: [Openid-specs-heart] Vote to Approve Implementer’s Drafts
> of OpenID HEART Specifications
>
>
>
> Everyone, please note that you will be required to acquire an OpenID and
> register it as being associated with your OpenID Foundation membership in
> order to complete your ballot (because you have to log in with that OpenID
> to vote). This is an easy process, since Yahoo, Google+, etc. work as
> OpenIDs. However, it can take as much as two business days for the
> registration/association process to be completed because it's a manual
> process. So please don't wait until the last minute if you intend to vote.
>
>
>
> *Instructions:*
>
>    1. Go to the ballot page
>    <https://openid.net/foundation/members/polls/101> or the members page
>    <https://openid.net/foundation/members> and click the “Log In with
>    your OpenID” link.
>    2. Choose the account you want to associate with your impending
>    membership and log in with it, authorizing the OpenID Foundation connection.
>    3. You’ll get a message in a yellow box like this one:
>
>
>
> * Uh oh. The OpenID {URL} doesn’t match any in our records. We invite you
>    to register <https://openid.net/foundation/members/registration> and become
>    a member of the OpenID Foundation today. *- If you haven't joined the
>    Foundation yet, click on the "register" link and fill in the form there.
>    - In any case, e-mail the displayed URL to help at oidf.org saying what
>    membership account to link your OpenID to.
>
> (Thanks to Mike for his help on this! My registration/association is still
> in process...)
>
>
>
> *Eve Maler *ForgeRock Office of the CTO | VP Innovation & Emerging
> Technology
> Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
> New ForgeRock Identity Platform <https://www.forgerock.com> with UMA
> support <https://www.forgerock.com/platform/user-managed-access/> and an OpenUMA
> community <https://forgerock.org/openuma/>!
>
>
>
> On Sun, Feb 7, 2016 at 9:54 PM, Mike Jones <Michael.Jones at microsoft.com>
> wrote:
>
> 17 people voted out of 190 currently active members – 9% of the
> membership.  There’s a 20% quorum requirement for the ballot to pass.
>
>
>
> The procedures allow the voting to be extended.  The voting period has
> been extended until Friday.  Another 21 votes are required to reach
> quorum.  If any of you have not voted, I encourage you to do so now.  If
> you’re not currently a member of the OpenID Foundation, you can join at
> https://openid.net/foundation/members/registration and vote.
>
>
>
> -- Mike, writing as OpenID Foundation Secretary
>
>
>
> *From:* Mike Jones
> *Sent:* Wednesday, January 27, 2016 10:30 AM
> *To:* openid-specs-heart at lists.openid.net
> *Subject:* Vote to Approve Implementer’s Drafts of OpenID HEART
> Specifications
>
>
>
> I’ve created the poll for the approval vote.  See
> https://openid.net/foundation/members/polls/101.  Voting will open
> tomorrow and close on Thursday, February 4th.  My apologies for not
> starting the vote on Monday, as planned.  Next time I’ll plan to put a
> reminder in my calendar so I stay on top of it!
>
>
>
> -- Mike, writing as OpenID Foundation Secretary
>
>
>
> *From:* Openid-specs-heart [
> mailto:openid-specs-heart-bounces at lists.openid.net
> <openid-specs-heart-bounces at lists.openid.net>] *On Behalf Of *Mike Jones
> *Sent:* Thursday, December 10, 2015 6:29 PM
> *To:* openid-specs-heart at lists.openid.net
> *Subject:* [Openid-specs-heart] FW: Review of Proposed Implementer’s
> Drafts of HEART Specifications
>
>
>
>
>
>
>
> *From:* Mike Jones
> *Sent:* Thursday, December 10, 2015 6:27 PM
> *To:* specs at lists.openid.net
> *Subject:* Review of Proposed Implementer’s Drafts of HEART Specifications
>
>
>
> The OpenID HEART Working Group recommends approval of the following
> specifications as OpenID Implementer’s Drafts:
>
> ·       Health Relationship Trust Profile for OAuth 2.0
>
> ·       Health Relationship Trust Profile for OpenID Connect 1.0
>
> ·       Health Relationship Trust Profile for User Managed Access 1.0
>
>
>
> An Implementer’s Draft is a stable version of a specification providing
> intellectual property protections to implementers of the specification.
> This note starts the 45-day public review period for the specification
> drafts in accordance with the OpenID Foundation IPR policies and
> procedures.  This review period will end on Sunday, January 24th, 2016.
> Unless issues are identified during the review that the working group
> believes must be addressed by revising the drafts, this review period will
> be followed by a seven-day voting period beginning on Monday, January 25th,
> 2016 during which OpenID Foundation members will vote on whether to approve
> these drafts as OpenID Implementer’s Drafts. For the convenience of
> members, voting may begin up to two weeks before Monday, January 25th,
> with the voting period still ending on Monday, February 1st, 2016.
>
>
>
> The specifications are available at:
>
> ·       http://openid.net/specs/openid-heart-oauth2-2015-12-07.html
>
> ·
> http://openid.net/specs/openid-heart-openid-connect-2015-12-07.html
>
> ·       http://openid.net/specs/openid-heart-uma-2015-12-09.html
>
>
>
> The HEART working group page is http://openid.net/wg/heart/.  Information
> on joining the OpenID Foundation can be found at
> https://openid.net/foundation/members/registration.  If you’re not a
> current OpenID Foundation member, please consider joining to participate in
> the approval vote.
>
>
>
> You can send feedback on the specifications in a way that enables the
> working group to act upon your feedback by (1) signing the contribution
> agreement at http://openid.net/intellectual-property/ to join the working
> group (please specify that you are joining the “HEART” working group on
> your contribution agreement), (2) joining the working group mailing list at
> http://lists.openid.net/mailman/listinfo/openid-specs-heart, and (3)
> sending your feedback to the list.
>
>
>
> -- Michael B. Jones – OpenID Foundation Board Secretary
>
>
>
> (This notice has also been posted at
> http://openid.net/2015/12/10/review-of-proposed-implementers-drafts-of-heart-specifications/
> .)
>
>
>
>
>
>
> _______________________________________________
> 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/20160208/7e97ceee/attachment.html>