Stream: fhircast-github
Topic: fhircast-docs / Issue #126 May 2019 Ballot Comment: How d...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #126
## May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_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 #126
## May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_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 #126
## May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 04 2019 at 14:18):
isaacvetter labeled Issue #126
## May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 16 2019 at 14:19):
isaacvetter commented on Issue #126:
Hey @bvdh,
I'm not sure what to do here. With the resolution to #127, we have an OAuth2 scope discovery protocol via SMART's .well-known/smart-configuration.
But:
1) scopes !== events.
2) OAuth2 is not a requirement.Can we "consider for future use"? Alternatively, would you be willing to draft up a more detailed proposal/documentation of how this GET on the cast-url should work?
Isaac
Github Notifications (FHIRcast) (Jul 23 2019 at 13:27):
isaacvetter commented on Issue #126:
Proposed resolution: Considered for future use
Proposed resolution comment: Bas, this is a solid idea and could really enable a fully dynamic client. Let's implement and consider as part of our potential STU2 ballot.
Github Notifications (FHIRcast) (Jul 23 2019 at 13:27):
isaacvetter labeled Issue #126:
## May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 24 2019 at 14:20):
isaacvetter commented on Issue #126:
During tcon conversation, @gkustas pointed out that a FHIRcast client could list the events that it supports receiving during the creation of the subscription. This would enable a "dumb", passthrough hub.
## :telephone_receiver: II Working Group Vote (7-24-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
@gkustas moved the following disposition, seconded by @wdvr
Disposition: Considered for future use.
Disposition Comment: This is a solid idea and could really enable a fully dynamic client. Let's implement and consider as part of our potential STU2 ballot as part of better enabling a standalone (aka "dumb"), pass-though Hub.:+1: For: 14
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Jul 24 2019 at 14:20):
wmaethner labeled Issue #126:
## May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 24 2019 at 14:54):
wdvr commented on Issue #126:
So to add to the proposed suggestion:
we could have our library of events, linked to scopes in OAuth (we would need to create hierarchy in the events though).
E.g. scope:
patient
events:
patient.open
patient.close
patient.*Scope
study:
events:
study.open
study.close
study.*So when having the OAuth 'study' scope, you could subscribe to any
study.*events (also events not yet in the library, such asstudy.foo).If you however do not have the study scope, you would not be able to register to this event.
events that are not in the library could be either always allowed - without specific scope, or have to fall under a certain umbrella, e.g.
other.*
or even
public.*- indicating that no authenticating is needed for this 'subgroup' of events.
Github Notifications (FHIRcast) (Sep 11 2019 at 20:46):
wmaethner commented on Issue #126:
Closed as not being addressed in STU1 ballot
Github Notifications (FHIRcast) (Sep 11 2019 at 20:46):
wmaethner closed Issue #126:
May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:47):
wmaethner reopened Issue #126:
May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:47):
wmaethner edited a comment on Issue #126:
Keeping open since this is an ongoing question
Github Notifications (FHIRcast) (Mar 17 2020 at 15:55):
isaacvetter commented on Issue #126:
Resolved in STU2 with: https://jira.hl7.org/browse/FHIR-25860 !
Closing.
Github Notifications (FHIRcast) (Mar 17 2020 at 15:55):
isaacvetter closed Issue #126:
May 2019 Ballot Comment: How does a client know what events are supported?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Subscribing and Unsubscribingt
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: How does a client know what events are supported?
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/79
"How does a client know what events are supported?
Maybe we should allow him to query the supported event using a GET on the cast-url."
Call to hub.topic could return the list of the events the topic supports and that the client may access. Alternatively, support any requests – this clashes with the authorization based on event types.
_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
