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

Stream: fhircast-github

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


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

hl7-fhircast-bot opened Issue #235

## May 2019 Ballot Comment:

Submitted by @euvitudo
Chapter/section: Intent Verification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: A-S

Summary:

Comment: RFC 2818 is a bit buried at this point in the document. It is referenced in the overview, and is likely sufficient there. Additionally, placement of the reference appears to be in the "GET" context, but it is not.

Existing wording: (RFC 2818)


_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:54):

hl7-fhircast-bot labeled Issue #235

## May 2019 Ballot Comment:

Submitted by @euvitudo
Chapter/section: Intent Verification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: A-S

Summary:

Comment: RFC 2818 is a bit buried at this point in the document. It is referenced in the overview, and is likely sufficient there. Additionally, placement of the reference appears to be in the "GET" context, but it is not.

Existing wording: (RFC 2818)


_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:54):

hl7-fhircast-bot edited Issue #235

## May 2019 Ballot Comment:

Submitted by @euvitudo
Chapter/section: Intent Verification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: A-S

Summary:

Comment: RFC 2818 is a bit buried at this point in the document. It is referenced in the overview, and is likely sufficient there. Additionally, placement of the reference appears to be in the "GET" context, but it is not.

Existing wording: (RFC 2818)


_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:34):

isaacvetter commented on Issue #235

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

Proposed resolution: Persuasive

Remove reference to RFC 2818 from the Intent Verification Request

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 14:56):

NiklasSvenzen labeled Issue #235

## May 2019 Ballot Comment:

Submitted by @euvitudo
Chapter/section: Intent Verification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: A-S

Summary:

Comment: RFC 2818 is a bit buried at this point in the document. It is referenced in the overview, and is likely sufficient there. Additionally, placement of the reference appears to be in the "GET" context, but it is not.

Existing wording: (RFC 2818)


_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 18:51):

wmaethner commented on Issue #235

## Montreal May 2019 Working Group Vote

Isaac Vetter moved the following disposition, seconded by Niklas Svenzen

Disposition: Persuasive
Disposition Comment: Will fix as described (in Isaac's comment above)

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

:tada: The motion passed! :tada:

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 18:51):

wmaethner labeled Issue #235

## May 2019 Ballot Comment:

Submitted by @euvitudo
Chapter/section: Intent Verification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: A-S

Summary:

Comment: RFC 2818 is a bit buried at this point in the document. It is referenced in the overview, and is likely sufficient there. Additionally, placement of the reference appears to be in the "GET" context, but it is not.

Existing wording: (RFC 2818)


_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 #235:

## May 2019 Ballot Comment:

Submitted by @euvitudo
Chapter/section: Intent Verification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: A-S

Summary:

Comment: RFC 2818 is a bit buried at this point in the document. It is referenced in the overview, and is likely sufficient there. Additionally, placement of the reference appears to be in the "GET" context, but it is not.

Existing wording: (RFC 2818)


_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 27 2019 at 13:43):

wmaethner labeled Issue #235:

## May 2019 Ballot Comment:

Submitted by @euvitudo
Chapter/section: Intent Verification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: A-S

Summary:

Comment: RFC 2818 is a bit buried at this point in the document. It is referenced in the overview, and is likely sufficient there. Additionally, placement of the reference appears to be in the "GET" context, but it is not.

Existing wording: (RFC 2818)


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

view this post on Zulip Github Notifications (FHIRcast) (Jul 23 2019 at 14:09):

wmaethner closed Issue #235:

## May 2019 Ballot Comment:

Submitted by @euvitudo
Chapter/section: Intent Verification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/#subscribing-and-unsubscribing
Type: A-S

Summary:

Comment: RFC 2818 is a bit buried at this point in the document. It is referenced in the overview, and is likely sufficient there. Additionally, placement of the reference appears to be in the "GET" context, but it is not.

Existing wording: (RFC 2818)


_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