URL-Sharing Using the OExchange Protocol Stack

From IIW
Revision as of 13:26, 7 February 2011 by WikiSysop (talk | contribs) (Undo revision 3234 by Igiwydijok (Talk))

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Conference: IIW 10 May 17-19, 2009 this is the complete Complete Set of Notes


Issue/Topic: Sharing URLs with the OExchange Open Stack

Tuesday – Session 3 - G

Convener: Will Meyer

Notes-taker(s): Charlie Reverte

Tags for the session - technology discussed/ideas considered:

OExchange, XRD, XRDP, XAUTH, Host-Meta, Sharing, NASCAR


Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:

trying to enable sharing to long tail services from content publishers. few goals, standardize way to send urls (exchange) to any site on the web, discover new services and allow users to personalize services that they see. services won't always be known at design time, use a late binding so new services can be discovered.

exchange: the service has an "offer" endpoint, standardize the params for passing an url, title, etc.

discovery: xrd document that describes the service, the name, "share" verb (send to, tweet this, translate). the service xrd is linked to from the site's host meta and via link tags in the page head (similar to rss).

personalization: publisher can offer you sharing options to the set of sites that you actually use including long tail sites they wouldn't normally link to. niche communities often have higher engagement and drive more traffic than general purpose social networks.

multiple options for persisting a user's service preferences, xauth, cookie, browser local storage, webfinger. webfinger is preferable as it persists across machines and allows others to discover services you use (and interact with you on those networks).

goals are to first codify how sharing is done today, later try to add options for new flows like popups, headless sharing, etc.

questions about splitting the personalization, personal discovery part into a separate spec; the exchange and service discovery parts are ready to go but webfinger etc aren't deployed yet.

there are roles for the browser here, to help discover new services and store preferences for services that you don't want to be public

Related Slides:

[Nascar for Sharing] [OExchange Technical Intro]