Stream: fhircast-github
Topic: fhircast-docs / Issue #209 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context 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:53):
hl7-fhircast-bot labeled Issue #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context 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:53):
hl7-fhircast-bot labeled Issue #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context 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:53):
hl7-fhircast-bot labeled Issue #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 03:00):
isaacvetter commented on Issue #209
NOTE on ANSI modal verbs: The usage of ANSI modal verbs consistently provides a vehicle for quickly discerning the conformance criteria.
HL7 adheres to ISO/IEC directive, Appendix G: ANSI modal verbs ("SHALL", "SHOULD", "MAY", "SHALL NOT", "SHOULD NOT", "MAY NOT") SHALL be capitalized. See FHIR conformance rules, section 2.1.0.1 "Conformance Language". http://hl7.org/implement/standards/fhir/conformance-rules.html
Github Notifications (FHIRcast) (May 06 2019 at 13:19):
isaacvetter commented on Issue #209
Use SHALL instead of MUST per HL7 FHIR
Github Notifications (FHIRcast) (May 07 2019 at 12:40):
wmaethner labeled Issue #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:19):
NiklasSvenzen unlabeled Issue #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:19):
NiklasSvenzen labeled Issue #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_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 #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_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 #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_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 #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_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 #209
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Aug 14 2019 at 13:48):
wmaethner labeled Issue #209:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context request.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Aug 19 2019 at 15:16):
wmaethner closed Issue #209:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Request Context Change
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: See note on ANSI modal Verbs
Existing wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub MUST either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber MUST be capable of gracefully handling a rejected context request.
Once a requested context change is accepted, the Hub SHALL broadcast the context notification to all subscribers, including the original requestor.
Proposed wording: Similar to the Hub's notifications to the subscriber, the subscriber MAY request context changes with an HTTP POST to the hub.topic url. The Hub SHALL either accept this context change by responding with any successful HTTP status or reject it by responding with any 4xx or 5xx HTTP status. The subscriber SHALL be capable of gracefully handling a rejected context 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
