Stream: fhircast-github
Topic: fhircast-docs / Issue #193 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #193
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_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 #193
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_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 #193
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_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 #193
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_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 edited Issue #193
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 06 2019 at 15:55):
isaacvetter assigned Issue #193
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 06 2019 at 15:59):
isaacvetter commented on Issue #193
Hey Tony,
I'm adding this into the proposed block vote as well, because I see it as a question and a ANSI modal verb update.
what are the criteria for denial?
The criteria for why a Hub denies a subscription is not explained by the spec. This is business logic of the Hub & driving application. Any number of security-related reasons could cause a Hub to deny a subscription. The Hub could determine that the
hub.topicisn't valid or even that the subscriber is requiredhub.eventsnot supported by the Hub or that the subscriber isn't authorized to join the particular user's session or ....Does that help?
Github Notifications (FHIRcast) (May 07 2019 at 13:10):
wmaethner labeled Issue #193(assigned to isaacvetter)
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:22):
NiklasSvenzen labeled Issue #193(assigned to isaacvetter)
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:22):
NiklasSvenzen unlabeled Issue #193(assigned to isaacvetter)
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:31):
wmaethner labeled Issue #193(assigned to isaacvetter)
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:31):
wmaethner unlabeled Issue #193(assigned to isaacvetter)
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:31):
wmaethner unlabeled Issue #193(assigned to isaacvetter)
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 17:54):
wmaethner labeled Issue #193(assigned to isaacvetter)
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Aug 06 2019 at 15:28):
wmaethner labeled Issue #193 (assigned to isaacvetter):
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Aug 19 2019 at 14:42):
isaacvetter edited a comment on Issue #193:
Hey Tony,
I'm adding this into the proposed block vote as well, because I see it as a question and a ANSI modal verb update.
what are the criteria for denial?
The criteria for why a Hub denies a subscription is not explained by the spec. This is business logic of the Hub & driving application. Any number of security-related reasons could cause a Hub to deny a subscription. The Hub could determine that the
hub.topicisn't valid or even that the subscriber's requiredhub.eventsare not supported by the Hub or that the subscriber isn't authorized to join the particular user's session or ....Does that help?
Github Notifications (FHIRcast) (Aug 19 2019 at 15:05):
wmaethner closed Issue #193 (assigned to isaacvetter):
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: So the real flow is that after the HUB returns success from the request, it SHALL either Deny or Verify Intent. I probably missed it, but what are the criteria for denial?
Existing wording: If (and when) the subscription is denied, the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
Proposed wording: If the subscription is denied, the Hub SHALL inform the subscriber by sending an HTTP GET request to the subscriber's callback URL as given in the subscription request. This request has the following query string arguments appended.
_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
