Shipping graph around the building

What is the gtp: (graph traversal protocol) standard for shipping triples?

How about:
[byte count for key[]bytes of key][link][pointer]

Ship the thing around in binary. The default shipping syntax is:

URL$ReturnUrl(And what ever subgraph segment is being shipped)

So the shipping container is really an overload on the URL attribute, and the forward pointer identifies the 'object' of the overload, send away. So machines just launch and forget. Some time later, a machine is notified of an incoming graph, but the shipping container url key has all the info it needs to reconnect and restart convolution. So, TE uses the same script whether talking at gigabit speeds or human speeds. Graphs get launched and goes who knows were, but they return home, these graphs being quants of information, the machines the neuron.