Syntax:
peer://<domain>/contact-id [/<resource>][?<query>][#<fragment>][;protocol=<protocol>][;request=<request>]
<domain> - the domain service where the Bootstrapped Network is introduced, e.g. “foo.com” or “bar.com”.
<resource> - and optional resource within the peer that is being requested.
<query> - an optional component which identifies non-hierarchical information about a resource.
<fragment> - an optional component which identifies direction towards a secondary resource.
<protocol> - the default value of “peer-dialog” is presumed, other extensions like “peer-http” are possible and might be presumed depending on the “lookup-type” requested
<request> - this allows control over the action required which this URI is requested, e.g. “call” might be used to establish an audio/video call to the peer or “get” might be used (or even assumed) in combination with a protocol type of “peer-http” to indicate performing an HTTP request over Open Peer.
Examples:
peer://foo.com/e852191079ea08b654ccf4c2f38a162e3e84ee04
peer://example.org/3b0056498dc7cdd6a4d5373ac0860f9738b071da
peer://example.org/3b0056498dc7cdd6a4d5373ac0860f9738b071da/index.php;protocol=peer-http
peer://hookflash.com/3b00564d6a4d5373ac0860f9738b071da/;protocol=peer-http;request=get
peer://foo.com/e852191079ea08b654ccf4c2f38a162e3e84ee04;request=call