Sequence Diagrams Sample Clauses

Sequence Diagrams. 2.1.1 Sender Intent Based Receiver Pull (notified pull) The sequence diagram below depicts the flow for the Sender Intent Based Receiver Pull (SIBR Pull) using OAuth 2.0 and HL7-FHIR, also known as "notified pull". The flow contains the following sections: • Invite the Receiver; • Cancellation by Sender (option), this block is only to be used when the Sender needs to withdraw the pull invitation, e.g., when the Sender invited a wrong Receiver; • Receiver performs pull interaction(s). Each section consists of several steps. The steps correspond to the numbers in the sequence diagram. Section Step Description Invite the Receiver 1 Optional reference to a request-Type resource that produced this event. If a workflow has been initiated, this should be referenced.
AutoNDA by SimpleDocs
Sequence Diagrams. A.1.1 Selecting Wetlands User G-A Client + WPS NWI WFS Select wetlands on map Query wetlands Query Wetlands WFS Return wetland features Return wetlands results Display selected wetlands NHD WFS Requirements
Sequence Diagrams. ‌ Configuration Phase Before the system can enter normal operations, some setup will be necessary – mostly concerning components registering themselves with the Global Resource Directory, so their IPv6-addresses can be queried on demand. The following manual configuration setup steps will be necessary:

Related to Sequence Diagrams

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Outputs 11. The objectives and outcomes of this Agreement will be achieved by:

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Housing.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • OGS Centralized Contract Modifications OGS, an Authorized User, or the Contractor may suggest modifications to the Centralized Contract or its Appendices. Except as specifically provided herein, modifications to the terms and conditions set forth herein may only be made with mutual written agreement of the Parties. Modifications may take the form of an update or an amendment. “

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Class Specifications The Human Resources Division shall determine:

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

Time is Money Join Law Insider Premium to draft better contracts faster.