Creating Needs and Establishing Connections Sample Clauses

Creating Needs and Establishing Connections. A need is created by sending a Create message containing the need description along with a public key to a WoN node. The need creator mints two URIs in the URI space of the WoN node in the process, the message URI (as explained above) and the Need URI. The latter is used as the root resource of the need description. Upon receiving the message, the WoN node makes the need description available as Linked Data and responds with a SuccessResponse.3 Need owners can ask other needs to establish a Connection by performing a handshake of a Connect and an Open message (or a Close message to deny the connection). Matching services can suggest a connection by sending a Hint message to one or both of the needs involved. In that case, the connection is created by the WoN node, but the owners still have to establish the connection by an Open/Open handshake. In an established connection, the need objects can freely exchange ConnectionMessage messages.3 The exchanged messages form two parallel signature chains on both WoN nodes as new messages refer to signatures of earlier (formerly unreferenced) messages. Moreover, these chains reference each other since each transferred message contains a reference to its remote copy. The message chain structure resulting from connecting two needs is depicted in Figure 2.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs

Related to Creating Needs and Establishing Connections

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Access to Property Borrower shall permit agents, representatives and employees of Lender to inspect the Property or any part thereof at reasonable hours upon reasonable advance notice.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Commingling of Resold Services with Unbundled Network Elements and Combinations of Unbundled Network Elements 6.7.1 To the extent it is Technically Feasible and pursuant to the terms of Section 9.1, CLEC may Commingle Telecommunications Services purchased on a resale basis with an Unbundled Network Element or combination of Unbundled Network Elements.

  • Member Access to Vendor Proposal Notwithstanding any other information provided in this solicitation or Vendor designation of certain documentation as confidential or proprietary, Vendor’s acceptance of this TIPS Contract constitutes Vendor’s consent to the disclosure of Vendor’s comprehensive proposal, including any information deemed confidential or proprietary, to TIPS Members. The proposing Vendor agrees that TIPS shall not be responsible or liable for any use or distribution of information or documentation by TIPS Members or any other party. By submitting this proposal, Vendor certifies the foregoing.

  • Use of Interconnection Facilities by Third Parties 6551 Error! Hyperlink reference not valid.9.9.1 Purpose of Interconnection Facilities. 6551

  • Secure Information Handling and Transfers 7.1 Physical and electronic handling, processing and transferring of DWP Data, including secure access to systems and the use of encryption where appropriate.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Cost Responsibility for Interconnection Facilities and Distribution Upgrades 4.1 Interconnection Facilities 4.2 Distribution Upgrades

  • Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures.

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