refer to graph blending
@@ -256,6 +256,14 @@ In our example the taxi service bot would combine the data graphs of both needs
Each side can use `agr:proposeToCancel` and try to cancel an agreement and thereby try to roll back actions that may be started after the agreement was formed (e.g. canceling the taxi order by calling the driver). However as stated before the request has to be accepted by the counterpart if an agreement should be canceled.
+### Blending data graphs
+
+As mentioned above a proposed data graph that is meant to fulfill goals is usually generated by one of the agents by combining the data graphs of one goal from each side of a connection. We call the process of combining two data graphs "blending".
+
+Blending is neccessary since both side describe their goals from their own perspective and usually use other node URIs to describe concepts that should be the same to talk about the same thing in a mutual agreement. For instance in the above examples the taxi service describes the ride it wants to organize as `ex1:myRide`, the client describe it as `ex2:myRide` and the proposed data graph may even use another URI `ex3:myRide` for the ride node. The point is to come up with a name of the ride that both participants can agree on. Since both participants have not used any restrictions on the ride node name/URI (only refering to the ride as a node of class `taxi:Ride`) in their goals shape graphs, the name of the ride can be changed to blend the data graphs together and satisfy both goals.
+
+Blending is described in [more detail here.](draft-graph-blending.md)
+
## Changes required in current system; design issues
1. Importing needs must be changed to allow for importing datasets (otherwise, we are not able to specify shapes graphs). This would also be required to specify multiple datasets with different access control settings, so this change might be useful for the future.
