Stream: fhircast-github
Topic: fhircast-docs / Issue #203 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_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 #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_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 #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_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 #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 06 2019 at 13:21):
isaacvetter commented on Issue #203
Use SHALL instead of MUST per HL7 FHIR
Github Notifications (FHIRcast) (May 07 2019 at 12:41):
wmaethner labeled Issue #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:20):
NiklasSvenzen unlabeled Issue #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:20):
NiklasSvenzen labeled Issue #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_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 #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_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 #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:32):
wmaethner unlabeled Issue #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_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 #203
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 02 2019 at 18:55):
wmaethner labeled Issue #203:
## 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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:39):
wmaethner closed Issue #203:
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: Confusing: The text says "method=signature where method is one of the See note on ANSI modal Verbswhere method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature." Also, see note on ANSI modal Verbs
Existing wording: Using the hub.secret from the subscription request, the hub MUST generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value MUST be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature MUST be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
Proposed wording: Using the hub.secret from the subscription request, the hub SHALL generate an HMAC signature of the payload and include that signature in the request headers of the notification. The X-Hub-Signature header's value SHALL be in the form method=signature where method is one of the recognized algorithm names and signature is the hexadecimal representation of the signature. The signature SHALL be computed using the HMAC algorithm (RFC6151) with the request body as the data and the hub.secret as the key.
_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
