[Openid-specs-heart] HEART Agenda 2015-11-23

Debbie Bucci debbucci at gmail.com
Mon Nov 23 23:51:57 UTC 2015


The way it was explained to me ... standards/profiles are not really final
until they go through interoperability and have proven implementations.

Its good standards practice.  I understand that openid connect went through
2 Implementers draft and 3 interoperability testing before they became
final .  (John B please correct me if I have those stats wrong )

On Nov 23, 2015 6:28 PM, "Moehrke, John (GE Healthcare)" <
John.Moehrke at med.ge.com> wrote:

> so, not being an OpenID expert… yet someone that wants to inform the
> healthcare ‘security interested’ community…
>
>
>
> What does “implementers draft” and ‘not’ mean? Is there a specification
> somewhere that speaks to the lifecycle of openID specifications?
>
>
>
> John
>
>
>
> *From:* Justin Richer [mailto:jricher at mit.edu]
> *Sent:* Monday, November 23, 2015 5:26 PM
> *To:* Moehrke, John (GE Healthcare); Eve Maler
> *Cc:* openid-specs-heart at lists.openid.net
> *Subject:* Re: [Openid-specs-heart] HEART Agenda 2015-11-23
>
>
>
> Eve is correct -- we are very specifically *NOT* putting the "OAuth for
> FHIR" spec up for implementer's draft.
>
>  -- Justin
>
> On 11/23/2015 6:17 PM, Moehrke, John (GE Healthcare) wrote:
>
> Thanks for the clarification.
>
>
>
> *From:* Eve Maler [mailto:eve.maler at forgerock.com
> <eve.maler at forgerock.com>]
> *Sent:* Monday, November 23, 2015 5:16 PM
> *To:* Moehrke, John (GE Healthcare)
> *Cc:* Debbie Bucci; openid-specs-heart at lists.openid.net
> *Subject:* Re: [Openid-specs-heart] HEART Agenda 2015-11-23
>
>
>
> Very close. We are going through a review process of these three:
>
>
>
> HEART profile for OAuth 2.0.
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__openid.bitbucket.org_HEART_openid-2Dheart-2Doauth2.html&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=WszmQrRkhRd7JPxJrFwDlwE2aZySbtQv0mbSuqgkbsk&s=ylEoYlfAxzLFYhR-Ye1sBIwd7B4e4TipaFnBZAQ9GDg&e=>
>
> HEART profile for OpenID Connect.
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__openid.bitbucket.org_HEART_openid-2Dheart-2Doidc.html&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=WszmQrRkhRd7JPxJrFwDlwE2aZySbtQv0mbSuqgkbsk&s=THEUmknDPFvGXSNjIxA2nI1iydGla0tCLBlcsKVQGPM&e=>
>
> HEART profile for User-Managed Access (UMA).
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__openid.bitbucket.org_HEART_openid-2Dheart-2Duma.html&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=WszmQrRkhRd7JPxJrFwDlwE2aZySbtQv0mbSuqgkbsk&s=b8V9qAKvjn1GHivPC65T0SPQjNtnwAc-9CGugLERNy4&e=>
>
>
>
> Each succeeding one builds on the last, and none is particularly
> healthcare-specific. The approval process will be for Implementer's Draft
> status, which is still an interim status that has IPR review implications
> for those on the WG.
>
>
>
>
>
> *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
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__forgerock.org_openuma_&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=WszmQrRkhRd7JPxJrFwDlwE2aZySbtQv0mbSuqgkbsk&s=Sws29jXfadLec1pfIhWr4C7UxkYqzY0rUZ_C5U3oxhg&e=>
> community!
>
>
>
> On Mon, Nov 23, 2015 at 2:26 PM, Moehrke, John (GE Healthcare) <
> John.Moehrke at med.ge.com> wrote:
>
> so If I understood the discussion today, we want to ask for review,
> comment, and eventual approval of the existing three profiles. Specifically
>
> ·  HEART profile for OAuth 2.0.
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__openid.bitbucket.org_HEART_openid-2Dheart-2Doauth2.html&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=WszmQrRkhRd7JPxJrFwDlwE2aZySbtQv0mbSuqgkbsk&s=ylEoYlfAxzLFYhR-Ye1sBIwd7B4e4TipaFnBZAQ9GDg&e=>
>
> ·  HEART profile for OpenID Connect.
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__openid.bitbucket.org_HEART_openid-2Dheart-2Doidc.html&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=WszmQrRkhRd7JPxJrFwDlwE2aZySbtQv0mbSuqgkbsk&s=THEUmknDPFvGXSNjIxA2nI1iydGla0tCLBlcsKVQGPM&e=>
>
> ·  HEART profile for Fast Healthcare Interoperability Resources (FHIR)
> OAuth 2.0 scopes
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__openid.bitbucket.org_HEART_openid-2Dheart-2Dfhir-2Doauth2.html&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=WszmQrRkhRd7JPxJrFwDlwE2aZySbtQv0mbSuqgkbsk&s=rS3pe-l_SlZIPbiM9CyqyoxDO6rBXbNpd9ONniqk700&e=>
> .
>
>
>
> Where, as we reviewed today, the first two are really not specialized for
> healthcare, as they are foundational. The third one is a set of scopes that
> are proposed for use with FHIR DSTU2.  All three are important building
> blocks for the work we are currently developing.
>
>
>
> John
>
>
>
> *From:* Openid-specs-heart [mailto:
> openid-specs-heart-bounces at lists.openid.net] *On Behalf Of *Debbie Bucci
> *Sent:* Sunday, November 22, 2015 7:13 PM
> *To:* openid-specs-heart at lists.openid.net
> *Subject:* [Openid-specs-heart] HEART Agenda 2015-11-23
>
>
>
> *When: 1 PM PST/4 PM EST*
>
> *Where: Gotomeeting – *https://global.gotomeeting.com/join/785234357
>
> *US phone number*: +1 (619) 550-0003. Access Code 785-234-357
>
>
>
>
>
> *Agenda :*
>
> ·  Implementer's Draft  - Justin Richer
>
> ·  Update from MITFuture Commerce
> Hackathon & Symposium - Adrian Gropper
>
> ·  AOB
>
>
> _______________________________________________
> Openid-specs-heart mailing list
> Openid-specs-heart at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-heart
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openid.net_mailman_listinfo_openid-2Dspecs-2Dheart&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=WszmQrRkhRd7JPxJrFwDlwE2aZySbtQv0mbSuqgkbsk&s=xVY6SFS5-GPcB9vzAnUQJKs8LpWsY-9l4Uk10egzcN4&e=>
>
>
>
>
>
>
> _______________________________________________
>
> Openid-specs-heart mailing list
>
> Openid-specs-heart at lists.openid.net
>
> http://lists.openid.net/mailman/listinfo/openid-specs-heart <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openid.net_mailman_listinfo_openid-2Dspecs-2Dheart&d=CwMD-g&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=B4hg7NQHul-cxfpT_e9Lh49ujUftqzJ6q17C2t3eI64&m=vk43d5JA9xKnpMqtfkrMZzZ2d_2m1wJiHmJlmiw4cOs&s=t1nOUW91on-hOV93CeIo77vc5hxJadaSkGBhdQtWzLw&e=>
>
>
>
> _______________________________________________
> 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/20151123/09325558/attachment.html>


More information about the Openid-specs-heart mailing list