FHIR Chat · fhircast-docs / Issue #173 May 2019 Ballot Comment: · fhircast-github

Stream: fhircast-github

Topic: fhircast-docs / Issue #173 May 2019 Ballot Comment:

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):

hl7-fhircast-bot labeled Issue #173

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):

hl7-fhircast-bot labeled Issue #173

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):

hl7-fhircast-bot opened Issue #173

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):

hl7-fhircast-bot edited Issue #173

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 21:15):

isaacvetter commented on Issue #173

Hey Yunwei,

It's because we're following WebSub, which even has this callout:
![image](https://user-images.githubusercontent.com/60514/56993816-16cd5300-6b63-11e9-9065-b42e0ce755b9.png)

https://www.w3.org/TR/websub/#verification-details

Do you think we should duplicate this callout in the FHIRcast spec?

Isaac

view this post on Zulip Github Notifications (FHIRcast) (May 07 2019 at 22:16):

isaacvetter commented on Issue #173

During conversation at the Montreal, May 2019 working group meeting, @wdbr, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to propose:

We committed to WebSub and shouldn't break it without a really good reason.

Proposed resolution: Not Persuasive

view this post on Zulip Github Notifications (FHIRcast) (May 07 2019 at 22:16):

isaacvetter labeled Issue #173

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (May 07 2019 at 22:17):

isaacvetter assigned Issue #173

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 15:01):

NiklasSvenzen labeled Issue #173(assigned to isaacvetter)

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 15:01):

NiklasSvenzen labeled Issue #173(assigned to isaacvetter)

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (May 09 2019 at 14:01):

isaacvetter commented on Issue #173

FHIRcast is modeled on the webhook design pattern and specifically the W3C WebSub RFC and build

Should we investigate also updating the Overview section to better emphasize WebSub compatibility and subsequent limitations/details.

view this post on Zulip Github Notifications (FHIRcast) (May 09 2019 at 14:03):

isaacvetter edited a comment on Issue #173

Note that the Overview section currently explains:

FHIRcast is modeled on the webhook design pattern and specifically the W3C WebSub RFC and build

Should we investigate also updating the Overview section to better emphasize WebSub compatibility and subsequent limitations/details.

view this post on Zulip Github Notifications (FHIRcast) (May 09 2019 at 14:03):

wmaethner commented on Issue #173

## Montreal May 2019 Working Group Vote

Will Maethner moved the following disposition, seconded by Reinhard Egelkraut

Disposition: Not persuasive with mod
Disposition Comment: Will clarify in the spec that we follow the web sub design pattern in various ways such as using GET vs POST. We will update the Overview section to better emphasize this point.

:+1: For: 7
:expressionless: Abstain: 0
:-1: Against: 0

:tada: The motion passed! :tada:

view this post on Zulip Github Notifications (FHIRcast) (May 09 2019 at 14:03):

wmaethner labeled Issue #173(assigned to isaacvetter)

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Jun 05 2019 at 14:15):

wmaethner unlabeled Issue #173 (assigned to isaacvetter):

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Aug 06 2019 at 15:28):

wmaethner labeled Issue #173 (assigned to isaacvetter):

## May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Aug 19 2019 at 15:06):

wmaethner closed Issue #173 (assigned to isaacvetter):

May 2019 Ballot Comment:

Submitted by Yunwei Wang
Chapter/section: Subscription Denial
Url:
Type: NEG :exclamation: Correction

Summary:

Comment: Why is this HTTP GET? HTTP GET "means retrieve whatever information (in the form of an entity) is identified by the Request-URI". Hub tries to notify subscriber about the denial not retrieving anything from call-back URL. Shouldn't this be HTTP POST?

Existing wording: the Hub MUST inform the subscriber by sending an HTTP GET request to the subscriber's callback URL

_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


An HL7 Website -