follow-up on notes on latest draft

In 1.6.4, add: 
(based on Pim feedback notes #10)

 

"The RoutingInput 
data may also be extracted from a PulRequest signal, in case the routing 
function must route such signals (as in 1.5.2.2, Case 3 – “end-to-end pulling”). 
In that case, and in the absence of any other header usable for routing (i.e. 
RoutingInput reference parameter header) the routing input MUST be reduced to 
the MPC attribute eb:PullRequest/@mpc and the routing function MUST be able to 
parse the eb:SignalMessage element, in order to access this MPC 
value. "

 

Jacques