Will fix the diagram, though all diagrams are expected to be refactored and clarified.   Will create a separate section that speaks to the requirements for HTTPS, OAuth and other security protocols.  We actually don't want to mandate the security protocols for all Da Vinci exchanges because some (e.g. registries) do not expose PHI and there may not be a need for encrypting the data in transit for those.  Instead, the section that explains all of the transport mechanisms will point to a the generic security section that sets base Da Vinci rules and also reminds implementers to adhere to additional state and federal rules. We will remove the post-condition reference to "tasks".  That language wasn't referring to the Task resource, but it also wasn't necessary language and it's better to avoid confusion.