Stream: fhircast-github
Topic: fhircast-docs / Issue #247 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot opened Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot labeled Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot labeled Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot labeled Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot edited Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 20:41):
isaacvetter commented on Issue #247
Hey @euvitudo, how about:
Proposed wording: Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, and MAY be a GUID.
Github Notifications (FHIRcast) (May 05 2019 at 01:11):
NiklasSvenzen labeled Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 01:11):
NiklasSvenzen assigned Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 01:11):
NiklasSvenzen unassigned Issue #247(assigned to NiklasSvenzen)
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 14:52):
wmaethner labeled Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 18:42):
isaacvetter commented on Issue #247
Proposed wording: Event identifier used to recognize retried notifications. This id SHALL be unique for the Hub, for example a GUID.
Github Notifications (FHIRcast) (May 08 2019 at 18:42):
wmaethner commented on Issue #247
## Montreal May 2019 Working Group Vote
Isaac Vetter moved the following disposition, seconded by Anthony Julian
Disposition: Persuasive with mod
Disposition Comment: Will fix as described in Isaac Vetter's comment above:+1: For: 12
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (May 08 2019 at 18:42):
wmaethner labeled Issue #247
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 05 2019 at 14:15):
wmaethner unlabeled Issue #247:
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 02 2019 at 18:55):
wmaethner labeled Issue #247:
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:31):
wmaethner closed Issue #247:
May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Event Notification Request Details
Url: https://fhircast.hl7.org/specification/May2019Ballot/#event-notification
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reading this text from a subscriber perspective, I should be able to interpret the event id to determine whether it's a retry or a user action (does it matter?). Would prefer the implementation details be left up to the hub, unless this really needs to be mandated by the spec.
Existing wording: Event identifier used to recognize retried notifications. This id MUST be globally unique for the Hub, SHOULD be opaque to the subscriber and MAY be a GUID.
_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
