FHIR Chat · fhircast-docs / Issue #89 May 2019 Ballot Comment: Change... · fhircast-github

Stream: fhircast-github

Topic: fhircast-docs / Issue #89 May 2019 Ballot Comment: Change...

---

Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):

hl7-fhircast-bot opened Issue #89

## May 2019 Ballot Comment: Change name of cast-hub

Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-S Enhancement

Summary: Change name of cast-hub

Comment: We should change the name of the cast-hub SMART launch parameter to make it more consistent with the rest of the "hub." parameters.

Existing wording:  In either case, the app MUST request and be granted the fhircast OAuth2.0 scope. Accompanying this scope grant, the authorization server MUST supply the cast-hub and hub.topic SMART launch parameters alongside the access token. 

---

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):

hl7-fhircast-bot labeled Issue #89

## May 2019 Ballot Comment: Change name of cast-hub

Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-S Enhancement

Summary: Change name of cast-hub

Comment: We should change the name of the cast-hub SMART launch parameter to make it more consistent with the rest of the "hub." parameters.

Existing wording:  In either case, the app MUST request and be granted the fhircast OAuth2.0 scope. Accompanying this scope grant, the authorization server MUST supply the cast-hub and hub.topic SMART launch parameters alongside the access token. 

---

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):

hl7-fhircast-bot edited Issue #89

## May 2019 Ballot Comment: Change name of cast-hub

Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-S Enhancement

Summary: Change name of cast-hub

Comment: We should change the name of the cast-hub SMART launch parameter to make it more consistent with the rest of the "hub." parameters.

Existing wording:  In either case, the app MUST request and be granted the fhircast OAuth2.0 scope. Accompanying this scope grant, the authorization server MUST supply the cast-hub and hub.topic SMART launch parameters alongside the access token. 

---

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

Github Notifications (FHIRcast) (May 30 2019 at 03:27):

isaacvetter commented on Issue #89:

Proposed resolution: Persuasive
Proposed resolution comment: We will change the name of the SMART launch parameter to match the name of the same value in the subscription/notification.

Github Notifications (FHIRcast) (May 30 2019 at 03:27):

isaacvetter labeled Issue #89:

## May 2019 Ballot Comment: Change name of cast-hub

Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-S Enhancement

Summary: Change name of cast-hub

Comment: We should change the name of the cast-hub SMART launch parameter to make it more consistent with the rest of the "hub." parameters.

Existing wording:  In either case, the app MUST request and be granted the fhircast OAuth2.0 scope. Accompanying this scope grant, the authorization server MUST supply the cast-hub and hub.topic SMART launch parameters alongside the access token. 

---

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

Github Notifications (FHIRcast) (May 30 2019 at 14:00):

isaacvetter commented on Issue #89:

Should the hub.topic name be changed to simply hub? What exactly is the proposed name? @wdvr - do you recall this conversation?

Github Notifications (FHIRcast) (May 31 2019 at 03:48):

wdvr commented on Issue #89:

We discussed making hub.topic just any string, dropping the requirement for it to be a URI - so the hub.topic should no longer having to be "https://[hubSubscriptionURL]/[myTopic]", but simply "[myTopic]".

I don't recall discussing to rename hub.topic to hub, and that would also not make sense imo.

Github Notifications (FHIRcast) (Jul 15 2019 at 22:11):

isaacvetter commented on Issue #89:

@wdvr - yes, you're exactly right, that wouldn't make sense. I was confused. The comment here is to to rename cast-hub (not hub.topic). Any thoughts about the below? Is this consistency worthwhile?

Proposed resolution: Persuasive with Mod
Proposed resolution comment: We will change the name of the cast-hub SMART launch parameter to hub.url to more closely match the naming scheme in the subscription/notification.

Github Notifications (FHIRcast) (Jul 17 2019 at 19:06):

wdvr commented on Issue #89:

:+1: cast-hub --> hub.url makes sense to me.

Github Notifications (FHIRcast) (Jul 24 2019 at 14:08):

isaacvetter commented on Issue #89:

## :telephone_receiver: II Working Group Vote (7-24-2019)

Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences

@isaacvetter moved the following disposition, seconded by @wdvr

Disposition: Persuasive with Mod
Disposition Comment: We will change the name of the cast-hub SMART launch parameter to hub.url to more closely match the naming scheme in the subscription/notification.

:+1: For: 12
:expressionless: Abstain: 0
:-1: Against: 0

:tada: The motion passed! :tada:

Github Notifications (FHIRcast) (Jul 24 2019 at 14:09):

wmaethner labeled Issue #89:

## May 2019 Ballot Comment: Change name of cast-hub

Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-S Enhancement

Summary: Change name of cast-hub

Comment: We should change the name of the cast-hub SMART launch parameter to make it more consistent with the rest of the "hub." parameters.

Existing wording:  In either case, the app MUST request and be granted the fhircast OAuth2.0 scope. Accompanying this scope grant, the authorization server MUST supply the cast-hub and hub.topic SMART launch parameters alongside the access token. 

---

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

Github Notifications (FHIRcast) (Sep 03 2019 at 21:58):

isaacvetter closed Issue #89:

May 2019 Ballot Comment: Change name of cast-hub

Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-S Enhancement

Summary: Change name of cast-hub

Comment: We should change the name of the cast-hub SMART launch parameter to make it more consistent with the rest of the "hub." parameters.

Existing wording:  In either case, the app MUST request and be granted the fhircast OAuth2.0 scope. Accompanying this scope grant, the authorization server MUST supply the cast-hub and hub.topic SMART launch parameters alongside the access token. 

---

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

---

Last updated: Apr 12 2022 at 19:14 UTC