Stream: fhircast-github
Topic: fhircast-docs / Issue #210 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #210
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Errors
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: IMHO the sync-error should be mandatory: the hub should always know
Existing wording: If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber MAY respond with a 'sync-error' event. The Hub MAY use these events to track synchronization state and MAY also forward these events to other subscribers of the same topic.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #210
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Errors
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: IMHO the sync-error should be mandatory: the hub should always know
Existing wording: If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber MAY respond with a 'sync-error' event. The Hub MAY use these events to track synchronization state and MAY also forward these events to other subscribers of the same topic.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #210
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Errors
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: IMHO the sync-error should be mandatory: the hub should always know
Existing wording: If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber MAY respond with a 'sync-error' event. The Hub MAY use these events to track synchronization state and MAY also forward these events to other subscribers of the same topic.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #210
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Errors
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: IMHO the sync-error should be mandatory: the hub should always know
Existing wording: If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber MAY respond with a 'sync-error' event. The Hub MAY use these events to track synchronization state and MAY also forward these events to other subscribers of the same topic.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 23 2019 at 13:57):
isaacvetter commented on Issue #210:
Related to #99
Github Notifications (FHIRcast) (May 23 2019 at 14:12):
wmaethner labeled Issue #210:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Errors
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: IMHO the sync-error should be mandatory: the hub should always know
Existing wording: If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber MAY respond with a 'sync-error' event. The Hub MAY use these events to track synchronization state and MAY also forward these events to other subscribers of the same topic.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 23 2019 at 14:25):
wmaethner commented on Issue #210:
Proposed resolution:
Persuasive with Mod
- Remove describing how the Hub can track synchronization state (that is an internal implementation detail and shouldn't be described or dictated here).
- Change the sync-error event to be generated by the Hub in response to an HTTP error code received from a subscriber during an event notification.
New wording: If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber SHALL respond with an HTTP error status code as described in Event Notification Response. If the Hub does not receive a successful HTTP status from a event notification, it SHOULD generate sync-error events to the other subscribers of that topic.
Github Notifications (FHIRcast) (Jun 18 2019 at 15:35):
wmaethner labeled Issue #210:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Errors
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: IMHO the sync-error should be mandatory: the hub should always know
Existing wording: If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber MAY respond with a 'sync-error' event. The Hub MAY use these events to track synchronization state and MAY also forward these events to other subscribers of the same topic.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:35):
wmaethner commented on Issue #210:
## :landline: II Working Group Vote (6-18-2019)
Block vote@isaacvetter moved the following disposition, seconded by Ricardo Quintano Neira
Disposition: Persuasive
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 10 2019 at 18:45):
isaacvetter closed Issue #210:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Errors
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: IMHO the sync-error should be mandatory: the hub should always know
Existing wording: If the subscriber cannot follow the context of the event, for instance due to an error or a deliberate choice to not follow a context, the subscriber MAY respond with a 'sync-error' event. The Hub MAY use these events to track synchronization state and MAY also forward these events to other subscribers of the same topic.
_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
