Common use of Creating Needs and Establishing Connections Clause in Contracts

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.

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 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 All these exchanged messages form two parallel signature chains on both WoN nodes as because new messages refer to signatures of earlier former (formerly unreferenced) messages. Moreover, Also these chains reference have references between each other since each transferred message contains a reference exchanged messages refer to its remote copycopy received on the other side. The message chain structure resulting from connecting two needs is depicted in Figure 2.