Syntax:
identity:[type:][//[<username>[:<password>]@]<domain>/]<identity-string>
If a “//” is not present after the “identity:” scheme, then the identity is assumed to be a specialized registered type that must be resolved in a specialized manner. If the “//” is present then the identity is resolved by the specified domain, with an optional username/password access credentials to the identity lookup service.
<username> - the username used for basic auth to the identity lookup service
<password> - the password used for basic auth to the identity lookup service
<domain> - the domain service where the identity is resolved, e.g. “foo.com” or “bar.com”.
<identity-string> - the string that represents the persona of the identity but the interpretation is specific to a particular domain.
Examples:
identity:phone:14165551212
identity:email:[email protected]
identity://foo.com/alice.78
identity://facebook.com/id3993232
identity://bar.com/linkedin.com/zs39923yf