Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
18Activity
0 of .
Results for:
No results containing your search query
P. 1
HP Gloe API Documentation (an HP Labs experiment)

HP Gloe API Documentation (an HP Labs experiment)

Ratings: (0)|Views: 7,955|Likes:
Published by Hewlett-Packard
API documentation for www.hpgloe.com
API documentation for www.hpgloe.com

More info:

Published by: Hewlett-Packard on May 07, 2010
Copyright:Traditional Copyright: All rights reserved

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

08/18/2011

pdf

text

original

 
 geo- tggi ng e x pe r i me n t  f  r o m  H  P  L  b s
hpgloe.com
 API DocumentAtIon
 
HP GLOE
 API DOCUMENTATION
2
GenerAl Protocol
 
 All APIs support JSONP, that is a callback HTTP GET parameter may be passed and theresult is then the string:
callback(json data);
 All operations may be called using HTTP GET with the format:
http://www.hpgloe.com/
json
/operation/?param1=val1&param2=val2…
In this document we describe the API for the HP Gloe service, ageo-tagging experiment from HPLabs. The goal of this document isto promote mashup services andcustomized clients to be writtenon top of Gloe and to allowsyndication of Gloe content.The API also allows native clientsto be built for platforms that Gloecurrently does not support, suchas a Firefox extension or iPhoneapp. For a general description ofGloe see the separate HP GloeOverview document.For further information andtechnical support, please contactgloecontact@hp.com.
 AuthentIcAtIon
 
Most operations can be called without requiring authentication. There are two waysof authenticating a user, with Facebook Connect, and with the native GLOEauthentication protocol.To initiate a Facebook Connect login a browser should be opened with the URL:
http://
www.hpgloe.com 
/json/
 mobilefblogin/
This will direct the user to the Facebook login page and set the cookies in the browser that arerequired to link the users’ Facebook account with a corresponding GLOE
account. For rst time
logins a new GLOE account will be created dynamically.For more information about Facebook connect see http://developers.facebook.com/connect.php. To login to a native GLOE account (without requiring a Facebook identity) the user must
rst register an account using the register operation (see below) to obtain a
GLOE
nickname 
and
recommendation
key. Authenticated requests must contain a timestamp parameter withthe current time using the time format %Y%m%d%H%M%S, e.g. 20091231235959. Therequest must also contain a user parameter with the nickname of a registered GLOE user. Theparameter values must then be signed in alphabetical order using the HMAC/SHA1 algorithm(See e.g., the Authentication section in http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?using-query-api.html for implementation details) with therecommendation key. Note GLOE uses the AWS signature version 1 scheme. The differenceto v2 are: we don’t include the parameter names in the data to sign, we order by parametername alphabetically, and we only support SHA1. The signature must then be passed in a
signature 
parameter. All operations apart from the friend management operations supportboth authenticated and anonymous users. Anonymous users should not pass any signature
parameter. Anonymous users are identied by their IP and will have a much stricter quota for
making recommendations.
 
HP GLOE
 API DOCUMENTATION
3
operations
getrec
lat
– latitude (required)
lon
 – longitude (required)
radius
– search radius
hits
– # result items
tag
– channel name
filter 
– me, all, friends
ref 
– url reference (usedby notes attached to Webpages)
q
– string to search for in titleor urlReturn recommendationsbased on a geolocation and
various lters. Defaults are
radius: 10 miles and hits:10 recommendations and
no lters.
 JSON array of 10-tuple withelements [<rank>,<url>,<title>,<thumburl>,<sample>,<tags>,<latitude>,<longitude>, <clicks>,<distance>] thumburl, sampleand tags are all deprecated,latitude and longitude areaverages. All text is inunicode compatible URLencoding.
 
If lter is not all
authentication is required.rec
lat
– latitude (required)
lon
– longitude (required)
url
– url to recommend(required)
tags
– channel torecommend on
ref 
– url that thisrecommendation is inreference to
notes
– used instead of url tocreate notes
title
– title ofrecommendation
click 
– true/false
 
Recommend and geotag Web sites or comments/notes on Web sites. JSON object withattribute message set toRECOMMENDATION_RECORDED if all went welland attribute quote set tothe remaining quota
.
If the url parameter is used itis a regular recommendationfor an existing site. If thenotes parameter is used theurl of the recommendationwill be created dynamicallyand hosted on the GLOEserver. If click=true therecommendation doesnot count towards torecommendation quota andit is not taken into accountwhen ranking Web sites.
nAme commentoutPut formAtPArAmeters DescrIPtIon
Parameters that need to be part of the signature apart from username and timestamp are marked in pink.

Activity (18)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Charlie Bess liked this
Moine Frederic liked this
tejiabraham liked this
Luciano Silva liked this
hak2310 liked this
prasadblv liked this
testuserhere5944 liked this
rkrish67 liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->