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

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

Subject Item

n52:this

foaf:made

n2:VirtCartConfigGooglePlus

Subject Item

n9:this

sioc:creator_of

n2:VirtCartConfigGooglePlus

Subject Item

n19:item

n20:services_of

n2:VirtCartConfigGooglePlus

Subject Item

n13:this

sioc:creator_of

n2:VirtCartConfigGooglePlus

Subject Item

n10:VOS

sioc:container_of

n2:VirtCartConfigGooglePlus

atom:entry

n2:VirtCartConfigGooglePlus

atom:contains

n2:VirtCartConfigGooglePlus

Subject Item

n2:VirtCartConfigGooglePlus

rdf:type

atom:Entry sioct:Comment

dcterms:created

2017-06-13T05:38:39.748883

dcterms:modified

2017-06-29T07:36:07.031760

rdfs:label

VirtCartConfigGooglePlus

foaf:maker

n7:this n52:this

dc:title

VirtCartConfigGooglePlus

opl:isDescribedUsing

n59:rdf

sioc:has_creator

n13:this n9:this

sioc:attachment

n21:png n22:png n23:png n24:png n25:png n26:png n27:png n28:png n29:png n30:png n31:png n32:png n33:png n34:png n35:png n36:png n37:png n38:png n40:png n41:png n42:png n43:png n44:png n45:png n46:png n47:png n48:png n49:png n50:png n53:png n54:png n55:png n56:png n57:png

sioc:content

%META:TOPICPARENT{name="VirtSpongerCartridgeSupportedDataSourcesVendorNonRDF"}% ---+Google+ Cartridge - Configuration Guidelines %TOC% Virtuoso's Sponger cartridge for Google+ allows you to fetch a Google+ user's profile and the Activities they post. These notes, intended for a 'Sponger Administrator', provide brief configuration guidelines for the cartridge. The cartridge is written to the [[https://developers.google.com/+/api/][Google+ API]]. The cartridge can be configured to use either: 1 VAL OAuth (the recommended option) to provide per-user access tokens or 2 Google API key (plus an optional OAuth key/secret for Google+ ID detection by the /sponger endpoint) Option 2 pre-dates option 1. VAL OAuth is the preferred option. Whether configured using OAuth or an API key, only public data is available from the Google+ API. --++Configuring the Cartridge for VAL OAuth Support for OAuth is provided through the Virtuoso Authentication Layer (VAL). All cartridges using VAL as the basis for their OAuth support are configured in a similar manner. For an overview of how to configure a cartridge's VAL OAuth binding, see topic [[SpongerOAuthSupport][Sponger OAuth Support via VAL]]. You will need to register OAuth application keys for the Google+ OAuth service in Conductor's 'Login Authentication Keys' panel, accessible through the 'Linked Data' and 'OAuth Service Binding' tabs. %BR%<img src="%ATTACHURLPATH%/conductor_login_auth_keys_panel.png" style="wikiautogen"/> ---+++Obtaining and Setting Google+ OAuth Keys 1 Go to the [[https://console.developers.google.com][Google Developers Console]]. Create a project if you don't already have one, then open it. 1 Under the 'APIS & AUTH' section of the side menu, click on the 'APIs' link and ensure the Google+ API is enabled with status set to 'ON'. 1 Click on the 'Credentials' menu item, again under the 'APIS & AUTH' section of the side menu. 1 In the 'OAuth' area, click the 'Create new Client ID' button. Set the application type to 'Web application' and ensure the Authorized Redirect URI is of the form <nowiki>http://{virtuoso-host}/val/api/thirdparty_callback</nowiki>. Note the generated client ID and client secret before signing out of the console. %BR%%BR%<img src="%ATTACHURLPATH%/google_dev_console_client_id_val.png" style="wikiautogen"/>%BR%%BR% 1 In Conductor's 'Login Authentication Keys' panel, add Google+ as a service, then enter the client ID and client secret in the 'Key' and 'Secret' fields. ---++Configuring the Cartridge to Use an API key #AncObtainApiKey ---+++Obtaining and Setting the API Key 1 Go to the [[https://console.developers.google.com][Google Developers Console]]. Create a project if you don't already have one, then open it. 1 Click on the 'Enable an API' button then ensure the Google+ API is enabled.. 1 Click on the 'Credentials' menu item under the 'APIS & AUTH' section of the side menu. 1 Scroll down the page to the section 'Public API access'. 1 Click on 'Create new Key'. In the 'Create a new key' dialog, select 'Server key'. List the IP addresses requests will be accepted from, or leave this field blank as appropriate, then click 'Create' and note the generated API key. %BR%%BR%<img src="%ATTACHURLPATH%/google_dev_console_api_key.png" style="wikiautogen"/>%BR%%BR% 1 Now go to your local Conductor at http://your-virtuoso-host:port/conductor 1 Go to Linked Data -> Sponger -> Extractor Cartridges: %BR%%BR%<img src="%ATTACHURLPATH%/conductor_extractor_cartridges_panel.png" style="wikiautogen"/>%BR%%BR% 1 Find "<nowiki>Google+</nowiki>" and click on its link in order to edit its properties. 1 As result the cartridge's configuration details should be shown (with the 'Cartridge Name' <nowiki>DB.DBA.RDF_LOAD_GOOGLE_PLUS</nowiki>): %BR%%BR%<img src="%ATTACHURLPATH%/googleplus_cartridge_config_panel.png" style="wikiautogen"/>%BR%%BR% 1 Enter the API key that was generated from above: %BR%%BR%<img src="%ATTACHURLPATH%/googleplus_cartridge_config_panel_with_key.png" style="wikiautogen"/>%BR%%BR% 1 Click 'Update" to save the "Options" settings. ---++View Your Google+ Profile as Linked Data Default installations of a Virtuoso Sponger instance include a Sponger front page, located at <nowiki>http://{virtuoso-host}/sponger</nowiki>, which includes a number of buttons for generating sample Sponger links for particular, typically social site, cartridges. %BR%%BR%<img src="%ATTACHURLPATH%/sponger_frontpage_buttons.png"/>%BR%%BR% You can sponge your Google+ profile, and transform it to Linked Data, by clicking on the Google+ button. If the cartridge has been configured to use OAuth, you will be asked to authenticate via your Google+ login, after which the Sponger can determine your Google+ ID. If the cartridge has been configured to use an API key, you will be prompted to enter your Google+ ID (unless a global OAuth token has been set in the cartridge options solely to enable automatic Google+ ID retrieval for /sponger - see the section [[#AncUserIdDetectionWhenApiKey][Configuring Google+ User ID Detection when Using an API Key]] for details). Once your Google+ ID is known, the Sponger creates sample Sponger links through which you can sponge your Google+ profile. The cartridge is configured to trigger on the URI pattern <nowiki>https://plus.google.com/.* </nowiki>, i.e. the expected starting point for sponging a Google+ user's profile is a URL of the form <nowiki>https://plus.google.com/{<i>user-id</i>}</nowiki>. The generated sample links proxy this base URL. For example: 1 Sponging [[http://uriburner.com/about/html/https://plus.google.com/112399767740508618350][http://uriburner.com/about/html/https://plus.google.com/112399767740508618350]] using the Sponger proxy /about/html/ yields: %BR%%BR%<img src="%ATTACHURLPATH%/gplus12.png" /> %BR%<img src="%ATTACHURLPATH%/gplus13.png" />%BR%%BR% 1 Clicking on the primary topic value link "Kingsley Idehen" displays: %BR%<img src="%ATTACHURLPATH%/gplus14.png" /> %BR%<img src="%ATTACHURLPATH%/gplus15.png" /> %BR%<img src="%ATTACHURLPATH%/gplus16.png" /> %BR%<img src="%ATTACHURLPATH%/gplus17.png" />%BR%%BR% ---++Alternative Follow-Your-Nose friendly view of a Google Data Object that represents a Person We can take a look at the /fct variant of the primaryTopic object page: 1 Click the <b>Facets</b> link from the footer section "Alternative Linked Data Views" of the page from above: %BR%<img src="%ATTACHURLPATH%/gplus18.png" /> %BR%<img src="%ATTACHURLPATH%/gplus19.png" /> %BR%<img src="%ATTACHURLPATH%/gplus20.png" /> %BR%<img src="%ATTACHURLPATH%/gplus21.png" />%BR%%BR% 1 Click "Next" to view the rest of the Attributes and their Values: %BR%<img src="%ATTACHURLPATH%/gplus22.png" /> %BR%<img src="%ATTACHURLPATH%/gplus23.png" />%BR%%BR% ---++Paging Options Because some Google+ user profiles can include hundreds of Activities and associated Comments, the following cartridge options are available to set configurable limits on the number of items returned. <nowiki>items_per_activity_page:</nowiki> * Sets the maximum number of activities returned per page of activities, where 1 &lt;= <nowiki>items_per_activity_page</nowiki> &lt;= 100. (Default: 50) <nowiki>max_activity_pages:</nowiki> * Limits the number of pages of activities returned. (Default: 1) * A value of 0 indicates no limit; all the user's activities will be returned. * A value of -1 turns off fetching of activities. <nowiki>items_per_comment_page:</nowiki> * Sets the maximum number of comments returned per page of comments, where 1 &lt;= <nowiki>items_per_comment_page</nowiki> &lt;= 100. (Default: 50) <nowiki>max_comment_pages:</nowiki> * Limits the number of pages of comments returned for a particular activity. (Default: 1) * A value of 0 indicates no limit; all available activity comments will be returned. * A value of -1 turns off fetching of activity comments. #AncUserIdDetectionWhenApiKey ---++Configuring Google+ User ID Detection when Using an API Key When the Google+ cartridge is configured to use an API key, setting a client ID and secret (for Google+ user ID detection by the /sponger endpoint) is optional. If not set, the /sponger Google+ button requires a user to enter their Google+ ID in order to generate the sample Sponger links. %BR%%BR%<img src="%ATTACHURLPATH%/googleplus_id_entry.png"/>%BR%%BR% When configured, the user's Google+ ID can be determined automatically. The user must simply log into Google (if not already) and grant the Sponger access to their profile. Note: When the cartridge is using VAL, entering a client-id and secret in the cartridge options as described below is *not* required. ---+++Configuring Sponger / Google OAuth Handshaking To obtain a client-id and secret, return to the 'Credentials' section of the Google Developers Console where you obtained an API key as detailed above. In the 'OAuth' area, click the 'Create new Client ID' button. Set the application type to 'Web application' and ensure the Authorized Redirect URI is of the form <nowiki>http://{virtuoso-host}/google_oauth</nowiki>. Note the generated Client ID and Client Secret before signing out of the console. %BR%%BR%<img src="%ATTACHURLPATH%/google_dev_console_client_id_non_val.png" style="wikiautogen"/>%BR%%BR% Next, the Client ID and Client Secret must be saved as option values in the Google+ cartridge configuration. Select the Google+ cartridge from the Extractor Cartridges tab under the Linked Data / Sponger tab in the Conductor UI. In the Options text area, enter options <nowiki>client_id=xxx client_secret=yyy</nowiki>, substituting the Client ID and Client Secret values just noted. Click the 'Update' button to save the new options. %BR%%BR%<img src="%ATTACHURLPATH%/google_oauth_options.png"/>%BR%%BR% Now, when a user clicks on the Google+ button on the Sponger front page, they should be prompted to log into Google and asked to grant access to the Sponger. If granted, the Sponger accesses their profile, determines their Google+ ID and generates sample Sponger links for the Google+ cartridge. ---++Google Access Token Retention and Use In most cases, OAuth-enabled Sponger cartridges retain access tokens for future use to allow an incremental sponge or complete re-sponge of the user's data (i.e. those portions of their data the user has granted access to). Google access tokens are always expiring tokens (even if offline access is specified when requesting a token) and must be refreshed through refresh tokens. They typically expire after 1 hour. Access tokens obtained through VAL are automatically refreshed as needed. Those obtained through a client id and client secret configured in the cartridge options are used only for the initial profile retrieval to build the sample Sponger URIs and are not saved for future use by the cartridge. ---++Related * [[VirtSponger][Virtuoso Sponger]] * [[VirtConfigureCartridges][Configure Sponger Cartridges Guide]] * [[http://ode.openlinksw.com/][The OpenLink Data Explorer Extension]] * [[http://ode.openlinksw.com/GooglePersonProfile.html][Google to Linked Data Transformation Examples]] * [[http://delicious.com/kidehen/goodrelations][Meshups (links and lookups across Web 2.0 Services and LOD Cloud]] * [[VirtSpongerCartridgeSupportedDataSources][OpenLink-supplied Virtuoso Sponger Cartridges]] * [[VirtSpongerCartridgeSupportedDataSourcesVendorNonRDF][Complete list of supported Vendor-specific Non-RDF Data Formats]] * [[VirtSpongerCartridgeSupportedDataSourcesNonRDF][Complete list of supported Standard Non-RDF Data Formats]] * [[VirtSpongerCartridgeSupportedDataSourcesMeta][Complete list of supported Meta Cartridges]] * [[VirtSpongerCartridgeSupportedDataSourcesMetaREST][Meta Cartridge Usage via REST Request]] * [[VirtSpongerCartridgeSupportedDataSourcesMetaRESTExamples][Parametrized Examples of Meta Cartridge Usage via REST Request]]

sioc:id

12f049fc4e93c3687ce28e01ae29b9df

sioc:link

n2:VirtCartConfigGooglePlus

sioc:has_container

n10:VOS

n20:has_services

n19:item

atom:title

VirtCartConfigGooglePlus

sioc:links_to

n4:com n2:VirtSpongerCartridgeSupportedDataSources n2:SpongerOAuthSupport n12:conductor n14: n15:html n16:goodrelations n17:112399767740508618350 n18: n2:VirtConfigureCartridges

atom:source

n10:VOS

atom:author

n52:this

atom:published

2017-06-13T05:38:39Z

atom:updated

2017-06-29T07:36:07Z

sioc:topic

n10:VOS

Subject Item

n2:VirtSpongerCartridgeSupportedDataSourcesVendorNonRDF

sioc:links_to

n2:VirtCartConfigGooglePlus