awkward MHD Push wording about hie-whitepaper HOT 2 CLOSED

John, It distinguishes three cases and does not repeat at all. Simply structure as three bullets: "In addition, the MHD can be used as an API in push mode in various configuartions: * The MHD push request could be handled by an intermediary that further pushes the content using XDR or XDM. * On the XDR or XDM recipient side of an intermediary, the MHD api could be used to forward a push to a Recipient using MHD; * The MHD push request could be handled by an intermediary, that could store in an XDS registry/repository allowing via another intermediary an MHD Document Consumer to query and retrieve the content." How does that feel ? Charles De : John Moehrke <[email protected]> Envoyé : mardi 22 décembre 2020 14:02 À : IHE/HIE-Whitepaper <[email protected]> Cc : Subscribed <[email protected]> Objet : [IHE/HIE-Whitepaper] awkward MHD Push wording (#116) Section Number PUSH Issue The current wording is very awkward and repeats "In addition the MHD can be used as an API in push mode. In this use case the MHD push request could be handled by an intermediary that further pushes the content using XDR or XDM. On the recipient side the MHD api could be used by an intermediary to forward a XDR or XDM push is further pushed to a Recipient using MHD; or the intermediary could store in a registry allowing a MHD Document Consumer to query and retrieve the content." Proposed Change simplify Priority: low — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#116> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/APOZ2DGQKPYL7QLJG3PGNZDSWDUL5ANCNFSM4VGARYOQ> . <https://github.com/notifications/beacon/APOZ2DFTDMHSUAL4DLRBBD3SWDUL5A5CNFSM4VGARYO2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4LQVW6SQ.gif>