Stream: fhircast-github
Topic: fhircast-docs / Issue #244 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot opened Issue #244
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_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 #244
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_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 #244
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_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 #244
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_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 #244
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 01:26):
NiklasSvenzen commented on Issue #244
Other external factors, outside of the control of the implementer may give this behavior (firewalls, layered networks etc). We should update the text to acknowledge this.
Github Notifications (FHIRcast) (May 05 2019 at 01:26):
NiklasSvenzen labeled Issue #244
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 01:32):
NiklasSvenzen edited a comment on Issue #244
Other external factors, outside of the control of the implementer may give this behavior (firewalls, layered networks etc). We should update the text to acknowledge this.
Also, this is taken directly from the WebSub specification:
https://www.w3.org/TR/websub/#verification-details
Github Notifications (FHIRcast) (May 23 2019 at 12:33):
lbergnehr assigned Issue #244:
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 23 2019 at 13:37):
wmaethner labeled Issue #244 (assigned to lbergnehr):
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 23 2019 at 13:37):
wmaethner commented on Issue #244:
Proposed resolution:
Not persuasive
- The intention is to dictate what the client should send, but have the hub be robust enough to handle other responses.
Github Notifications (FHIRcast) (Jun 18 2019 at 15:33):
isaacvetter commented on Issue #244:
## :telephone_receiver: II Working Group Vote (6-18-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
@singhashish moved the following disposition, seconded by Chris Carr
Disposition: Not Persuasive
Disposition Comment: Overall, it's a good thing for the client's response to be strictly mandated and for the hub to be able to handle multiple responses. For example, lack of communication would result in a timeout, not a 404.:+1: For: 12
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Jun 18 2019 at 15:53):
wmaethner labeled Issue #244 (assigned to lbergnehr):
## May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:32):
wmaethner commented on Issue #244:
Closing since this was labeled not persuasive
Github Notifications (FHIRcast) (Sep 11 2019 at 20:32):
wmaethner closed Issue #244 (assigned to lbergnehr):
May 2019 Ballot Comment:
Submitted by @euvitudo
Chapter/section: Intent Verification Response
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: NEG :exclamation:
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: The two paragraphs are inconsistent. A 404 is expected (MUST) while the Hub must consider other response codes.
Either the Hub expects a 404, or the client MAY/SHOULD return a 404 but MAY return other 3xx, 4xx or 5xx codes.
Existing wording: If the subscriber does not agree with the action, the subscriber MUST respond with a 404 "Not Found" response.
The Hub MUST consider other server response codes (3xx, 4xx, 5xx) to mean that the verification request has failed.
_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
