Stream: fhircast-github
Topic: fhircast-docs / Issue #133 May 2019 Ballot Comment: Creat...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot opened Issue #133
## May 2019 Ballot Comment: Create a new field (variable) in the message to provide the response of subscription denial
Submitted by Ricardo Quintano Neira
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Create a new field (variable) in the message to provide the response of subscription denial
Comment: According to the specification, in case of subscription denial, the hub must return a message with hub.mode = "denied"
I would create a new field (variable) in the message to provide the response of subscription denial. In the way it is currently proposed in the specification it seems like mixing concepts.
I would send back the hub.model with the same content provided in the subscription request
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot labeled Issue #133
## May 2019 Ballot Comment: Create a new field (variable) in the message to provide the response of subscription denial
Submitted by Ricardo Quintano Neira
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Create a new field (variable) in the message to provide the response of subscription denial
Comment: According to the specification, in case of subscription denial, the hub must return a message with hub.mode = "denied"
I would create a new field (variable) in the message to provide the response of subscription denial. In the way it is currently proposed in the specification it seems like mixing concepts.
I would send back the hub.model with the same content provided in the subscription request
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot labeled Issue #133
## May 2019 Ballot Comment: Create a new field (variable) in the message to provide the response of subscription denial
Submitted by Ricardo Quintano Neira
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Create a new field (variable) in the message to provide the response of subscription denial
Comment: According to the specification, in case of subscription denial, the hub must return a message with hub.mode = "denied"
I would create a new field (variable) in the message to provide the response of subscription denial. In the way it is currently proposed in the specification it seems like mixing concepts.
I would send back the hub.model with the same content provided in the subscription request
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot edited Issue #133
## May 2019 Ballot Comment: Create a new field (variable) in the message to provide the response of subscription denial
Submitted by Ricardo Quintano Neira
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Create a new field (variable) in the message to provide the response of subscription denial
Comment: According to the specification, in case of subscription denial, the hub must return a message with hub.mode = "denied"
I would create a new field (variable) in the message to provide the response of subscription denial. In the way it is currently proposed in the specification it seems like mixing concepts.
I would send back the hub.model with the same content provided in the subscription request
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 21:06):
isaacvetter commented on Issue #133
Hi Ricardo,
We're following the existing WebSub exchange in allowing the hub.mode parameter to have a subscribe value in the request and a denied value in the response. Check out:https://www.w3.org/TR/websub/#subscription-validation
Github Notifications (FHIRcast) (May 06 2019 at 21:42):
isaacvetter commented on Issue #133
During conversation at the Montreal, May 2019 working group meeting, @RicardoQuintano, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to:
Propose Not Persuasive.
Github Notifications (FHIRcast) (May 21 2019 at 13:51):
wmaethner labeled Issue #133:
## May 2019 Ballot Comment: Create a new field (variable) in the message to provide the response of subscription denial
Submitted by Ricardo Quintano Neira
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Create a new field (variable) in the message to provide the response of subscription denial
Comment: According to the specification, in case of subscription denial, the hub must return a message with hub.mode = "denied"
I would create a new field (variable) in the message to provide the response of subscription denial. In the way it is currently proposed in the specification it seems like mixing concepts.
I would send back the hub.model with the same content provided in the subscription request
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 16 2019 at 14:27):
isaacvetter edited a comment on Issue #133:
During conversation at the Montreal, May 2019 working group meeting, @RicardoQuintano, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to:
Proposed resolution: Not Persuasive
Github Notifications (FHIRcast) (Jul 24 2019 at 14:05):
wmaethner commented on Issue #133:
## :landline: II Working Group Vote (7-24-2019)
Block vote 3Ricardo Quintano Neira moved the following disposition, seconded by @isaacvetter
Disposition: Persuasive
Disposition Comment: Will fix as described in the issue comments or by the commenter:+1: For: 11
:expressionless: Abstain: 1
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Jul 24 2019 at 14:05):
wmaethner labeled Issue #133:
## May 2019 Ballot Comment: Create a new field (variable) in the message to provide the response of subscription denial
Submitted by Ricardo Quintano Neira
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Create a new field (variable) in the message to provide the response of subscription denial
Comment: According to the specification, in case of subscription denial, the hub must return a message with hub.mode = "denied"
I would create a new field (variable) in the message to provide the response of subscription denial. In the way it is currently proposed in the specification it seems like mixing concepts.
I would send back the hub.model with the same content provided in the subscription request
_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 closed Issue #133:
## May 2019 Ballot Comment: Create a new field (variable) in the message to provide the response of subscription denial
Submitted by Ricardo Quintano Neira
Chapter/section: Subscription Denial
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Create a new field (variable) in the message to provide the response of subscription denial
Comment: According to the specification, in case of subscription denial, the hub must return a message with hub.mode = "denied"
I would create a new field (variable) in the message to provide the response of subscription denial. In the way it is currently proposed in the specification it seems like mixing concepts.
I would send back the hub.model with the same content provided in the subscription request
_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
