Stream: fhircast-github
Topic: fhircast-docs / Issue #100 May 2019 Ballot Comment: How d...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #100
## May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_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 #100
## May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_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 #100
## May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_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 #100
## May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_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 #100
## May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 07 2019 at 21:37):
isaacvetter commented on Issue #100
During conversation at the Montreal, May 2019 working group meeting, @wdbr, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to propose:
Proposed Resolution: Persuasive
Will enhance the spec to clarify that a hub SHALL send a
mode=deniedto the subscriber when a subscription ends.
Github Notifications (FHIRcast) (May 07 2019 at 21:55):
isaacvetter edited a comment on Issue #100
During conversation at the Montreal, May 2019 working group meeting, @wvdr, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to propose:
We talked through 4 scenarios:
4) hub business logic - Hub denies existing subscription. Already covered, text could be more prominent.
3) unexpected end of session - in the case where the Hub crashes, no notification is possible.
1) lease_seconds expires - the subscribing client is responsible for tracking it the lease of it's subscription.
2) user_logout - this is an event and otherwise falls into the hub business logic category.Proposed Resolution: Persuasive
Do note that the spec already says:
The subscription MAY be denied by the Hub at any point (even if it was previously accepted). The Subscriber SHOULD then consider that the subscription is not possible anymore.
Will update the spec to clarify that a hub SHALL send a
mode=deniedto the subscriber when a subscription ends, including an expired .
Github Notifications (FHIRcast) (May 07 2019 at 21:55):
isaacvetter edited a comment on Issue #100
During conversation at the Montreal, May 2019 working group meeting, @wdvr, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to propose:
We talked through 4 scenarios:
4) hub business logic - Hub denies existing subscription. Already covered, text could be more prominent.
3) unexpected end of session - in the case where the Hub crashes, no notification is possible.
1) lease_seconds expires - the subscribing client is responsible for tracking it the lease of it's subscription.
2) user_logout - this is an event and otherwise falls into the hub business logic category.Proposed Resolution: Persuasive
Do note that the spec already says:
The subscription MAY be denied by the Hub at any point (even if it was previously accepted). The Subscriber SHOULD then consider that the subscription is not possible anymore.
Will update the spec to clarify that a hub SHALL send a
mode=deniedto the subscriber when a subscription ends, including an expired .
Github Notifications (FHIRcast) (May 07 2019 at 21:56):
isaacvetter assigned Issue #100
## May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 13:58):
isaacvetter edited a comment on Issue #100
During conversation at the Montreal, May 2019 working group meeting, @wdvr, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to propose:
We talked through 4 scenarios:
1) hub business logic - Hub denies existing subscription. Already covered, text could be more prominent.
2) unexpected end of session - in the case where the Hub crashes, no notification is possible.
3) lease_seconds expires - the subscribing client is responsible for tracking it the lease of it's subscription.
4) user_logout - this is an event and otherwise falls into the hub business logic category.Proposed Resolution: Persuasive
Do note that the spec already says:
The subscription MAY be denied by the Hub at any point (even if it was previously accepted). The Subscriber SHOULD then consider that the subscription is not possible anymore.
Will update the spec to clarify that a hub SHALL send a
mode=deniedto the subscriber when a subscription ends, including an expired .
Github Notifications (FHIRcast) (May 16 2019 at 06:51):
lbergnehr labeled Issue #100 (assigned to isaacvetter):
## May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:50):
wmaethner labeled Issue #100 (assigned to isaacvetter):
## May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:50):
wmaethner commented on Issue #100:
## :landline: II Working Group Vote (6-18-2019)
Block vote@isaacvetter moved the following disposition, seconded by Ricardo Quintano Neira
Disposition: Persuasive with mod
Disposition Comment: Will fix as described in the issue comments or by the commenter:+1: For: 10
:expressionless: Abstain: 2
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Sep 11 2019 at 20:51):
wmaethner closed Issue #100 (assigned to isaacvetter):
May 2019 Ballot Comment: How does the hub inform its subscribers that the subscription is ending?
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Unsubscribe
Url:
Type: NEG :exclamation: Correction
In Person requested: Yes :bust_in_silhouette:Summary: How does the hub inform its subscribers that the subscription is ending?
Comment: The unsubscribing section explains what happens when the subscribing app no longer wants to receive notifications, but doesn't explain what happens when the hub no longer wants to send out notifications (for example when the hub client closes or logs out and wants to end its subscriptions). Does this fall under the denial case? If so that should be clarified.
_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
