10 likes | 93 Views
xdi2-connector-personal. The diagram below explains how the PersonalGemContributor is invoked by the XDI2 server for certain parts of the graph, in order to fetch data from the Personal.com API. $is. Most of the graph is handled by the GraphMessagingTarget. (=!1111). ().
E N D
xdi2-connector-personal The diagram below explains how the PersonalGemContributor is invoked by the XDI2 server for certain parts of the graph, in order to fetch data from the Personal.com API. $is Most of the graph is handled by the GraphMessagingTarget (=!1111) () +(https://personal.com/) !<username> This part of the graph is covered by the PersonalGemContributor $is =!1111 =!1111 $oauth $!($token) ! +(0000) “xxxxx” =!2222 +first $!(+(preferred_first_name)) $!(+name) +last +friend “Markus” +name $is $!1 $is $!2 Interceptors apply to all parts of a graph, independent of the GraphMessagingTarget and the PersonalGemContributor “Sabadello”