FHIR Chat · fhircast-docs / Issue #343 STU2 cleanup tasks · fhircast-github

Stream: fhircast-github

Topic: fhircast-docs / Issue #343 STU2 cleanup tasks

Github Notifications (FHIRcast) (Nov 24 2020 at 15:15):

isaacvetter opened Issue #343:

• Run a spell-checker
• Run a broken link checker
• Find and remove content, like: "Feedback from implementers is requested here."
• I think this is a problem link: " HTTP [RFC7231] 200"

Github Notifications (FHIRcast) (Nov 24 2020 at 22:04):

isaacvetter edited Issue #343:

• Run a spell-checker
• Run a broken link checker
• Find and remove content, like: "Feedback from implementers is requested here."
• I think this is a problem link: " HTTP [RFC7231] 200"
• Some formatting issues, starting with: "* They can respond to the event notification with an HTTP error status code as described in Event Notification Response. * They can respond to the event notification with an HTTP 202 (Accepted) as described above, then, once experiencing the error, send a syncerror event to the Hub."

Github Notifications (FHIRcast) (Nov 24 2020 at 23:23):

isaacvetter commented on Issue #343:

https://www.w3.org/2002/01/spellchecker?uri=http%3A%2F%2Ffhircast.org%2Fspecification%2FSTU2%2F&lang=en_US

"APIs"
"FHIR"
"FHIRcast"
"HL"
"HTTPS"
"ImagingStudy"
"JSON"
"TLS"
"WSS"
"WebSocket"
"WebSockets"
"WebSub"
"hl"
"json"
"png"
"subsubscribing" <!-- fixed
"syncerror"
"userhibernate"
"userlogout"
"webhook"

Github Notifications (FHIRcast) (Nov 24 2020 at 23:25):

isaacvetter commented on Issue #343:

This random utility found zero broken links across all of fhircast.org: https://www.brokenlinkcheck.com/broken-links.php#status

Github Notifications (FHIRcast) (Nov 30 2020 at 22:18):

isaacvetter closed Issue #343:

• Run a spell-checker
• Run a broken link checker
• Find and remove content, like: "Feedback from implementers is requested here."
• I think this is a problem link: " HTTP [RFC7231] 200"
• Some formatting issues, starting with: "* They can respond to the event notification with an HTTP error status code as described in Event Notification Response. * They can respond to the event notification with an HTTP 202 (Accepted) as described above, then, once experiencing the error, send a syncerror event to the Hub."

Last updated: Apr 12 2022 at 19:14 UTC