This HTML5 document contains 13 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n2:import

rdf:type

schema:EntryPoint

schema:httpMethod

GET

schema:contentType

text/xml

n3:isWebServiceOf

n5:this_ODSUserModuleAPI

n3:endPointURL

n7:import

schema:shortDescription

<p>Import profile data from another service or from a data stream. </p>

n3:hasParameter

n4:_serviceId n4:_target n4:_service n4:_keepGraph

schema:name

EntryPoint - user_profile_import

schema:description

<p>ODS supports profile import from a variety of services thanks to the power of Virtuoso's Sponger cartridges. This API method uses the Sponger to fetch profile details from another service and optionally merge them into the ODS profile.</p><p>The method has two modes of operations:<itemizedlist> <listitem><p>Clients can either provide a <computeroutput>serviceId</computeroutput> which is already connected to the authenticated user account (see <ref kindref="member" refid="group__ods__module__user_1gad6f02a38ce0b890ad56c35888e33eed8">user.authenticate.authenticationUrl()</ref>) to import the data directly from the third-party service.</p></listitem><listitem><p>Or they can provide a blob of FOAF or VCard data in any of the supported RDF serializations in the request body.</p></listitem></itemizedlist> </p><p>Be aware that the method will signal an error if no profile data can be found, ie. if there is no Sponger cartridge available to handle the given service.</p><p><parameterlist kind="param"><li> <parameternamelist> <parametername>service</parametername> </parameternamelist> <parameterdescription> <p>The service type like "facebook" or "webid" </p></parameterdescription> </li> <li> <parameternamelist> <parametername>serviceId</parametername> </parameternamelist> <parameterdescription> <p>The identifier like the facebook profile URL or the actual WebID. If empty, the data is read from the HTTP request body. Before being able to import profile details the service ID first has to be connected to the authenticated ODS account. This is typically done via <ref kindref="member" refid="group__ods__module__user_1gad6f02a38ce0b890ad56c35888e33eed8">user.authenticate.authenticationUrl()</ref>. </p></parameterdescription> </li> <li> <parameternamelist> <parametername>target</parametername> </parameternamelist> <parameterdescription> <p>Where to import the profile data to. This can be one of <computeroutput>personal</computeroutput>, <computeroutput>business</computeroutput>, or <computeroutput>none</computeroutput>. In the latter case the data is only imported into a private data graph but not into the ODS profile. </p></parameterdescription> </li> <li> <parameternamelist> <parametername>keepGraph</parametername> </parameternamelist> <parameterdescription> <p>If <computeroutput>keep</computeroutput> then the profile data will be kept in a private data graph in addition to storing it in the ODS profile. If <computeroutput>clear</computeroutput> then the original data will be thrown away after import. Be aware that a <computeroutput>target</computeroutput> value of <computeroutput>none</computeroutput> in combination with a <computeroutput>keepGraph</computeroutput> value of <computeroutput>clear</computeroutput> does not make much sense.</p></parameterdescription> </li> </ul> On error an appropriate HTTP status code will be set.</p><p><simplesect kind="see"><p><ref kindref="member" refid="group__ods__module__user_1gad6f02a38ce0b890ad56c35888e33eed8">user.authenticate.authenticationUrl()</ref>, <ref kindref="member" refid="group__ods__module__user_1gaa383784d1c31a23a5687ddc25485e4e4">user.dataGraphs.list()</ref> </p></simplesect> </p>

schema:url

n7:import