Stream: fhircast-github
Topic: fhircast-docs / Issue #204 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #204
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reworded - clumsy, additionally IMHO the timestamp and Event ID should be SHALL, not should.
Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp should be used by subscribers to establish message affinity through the use of a message queue. The event identifier should be used to differentiate retried messages from user actions.
Proposed wording: The notification to the subscriber MUST a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity through the use of a message queue. The event identifier SHOULD be used to differentiate retried messages from user actions.
_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 #204
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reworded - clumsy, additionally IMHO the timestamp and Event ID should be SHALL, not should.
Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp should be used by subscribers to establish message affinity through the use of a message queue. The event identifier should be used to differentiate retried messages from user actions.
Proposed wording: The notification to the subscriber MUST a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity through the use of a message queue. The event identifier SHOULD be used to differentiate retried messages from user actions.
_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 #204
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reworded - clumsy, additionally IMHO the timestamp and Event ID should be SHALL, not should.
Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp should be used by subscribers to establish message affinity through the use of a message queue. The event identifier should be used to differentiate retried messages from user actions.
Proposed wording: The notification to the subscriber MUST a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity through the use of a message queue. The event identifier SHOULD be used to differentiate retried messages from user actions.
_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 #204
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reworded - clumsy, additionally IMHO the timestamp and Event ID should be SHALL, not should.
Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp should be used by subscribers to establish message affinity through the use of a message queue. The event identifier should be used to differentiate retried messages from user actions.
Proposed wording: The notification to the subscriber MUST a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity through the use of a message queue. The event identifier SHOULD be used to differentiate retried messages from user actions.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 30 2019 at 02:18):
isaacvetter commented on Issue #204:
Proposed resolution: Persuasive with Mod
Proposed resolution comment: will accept proposed language with some corrections (use of word include).
Github Notifications (FHIRcast) (Jun 04 2019 at 13:20):
wmaethner labeled Issue #204:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reworded - clumsy, additionally IMHO the timestamp and Event ID should be SHALL, not should.
Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp should be used by subscribers to establish message affinity through the use of a message queue. The event identifier should be used to differentiate retried messages from user actions.
Proposed wording: The notification to the subscriber MUST a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity through the use of a message queue. The event identifier SHOULD be used to differentiate retried messages from user actions.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:36):
wmaethner labeled Issue #204:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reworded - clumsy, additionally IMHO the timestamp and Event ID should be SHALL, not should.
Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp should be used by subscribers to establish message affinity through the use of a message queue. The event identifier should be used to differentiate retried messages from user actions.
Proposed wording: The notification to the subscriber MUST a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity through the use of a message queue. The event identifier SHOULD be used to differentiate retried messages from user actions.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:36):
wmaethner commented on Issue #204:
## :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) (Jun 18 2019 at 15:40):
wmaethner edited a comment on Issue #204:
## :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) (Jul 02 2019 at 18:55):
wmaethner labeled Issue #204:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reworded - clumsy, additionally IMHO the timestamp and Event ID should be SHALL, not should.
Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp should be used by subscribers to establish message affinity through the use of a message queue. The event identifier should be used to differentiate retried messages from user actions.
Proposed wording: The notification to the subscriber MUST a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity through the use of a message queue. The event identifier SHOULD be used to differentiate retried messages from user actions.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 23 2019 at 14:15):
isaacvetter commented on Issue #204:
Do note that #159 changed this proposed SHOULD to a MAY.
Github Notifications (FHIRcast) (Sep 11 2019 at 20:39):
wmaethner closed Issue #204:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Reworded - clumsy, additionally IMHO the timestamp and Event ID should be SHALL, not should.
Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp should be used by subscribers to establish message affinity through the use of a message queue. The event identifier should be used to differentiate retried messages from user actions.
Proposed wording: The notification to the subscriber MUST a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity through the use of a message queue. The event identifier SHOULD be used to differentiate retried messages from user actions.
_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
