• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
OExchange Technical Intro
 

OExchange Technical Intro

on

  • 541 views

A short technical introduction to OExchange

A short technical introduction to OExchange

Statistics

Views

Total Views
541
Views on SlideShare
523
Embed Views
18

Actions

Likes
1
Downloads
3
Comments
0

5 Embeds 18

http://www.slideshare.net 10
http://www.bagtheweb.com 4
http://bagtheweb.com 2
http://staging.bagtheweb.com 1
https://www.bagtheweb.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    OExchange Technical Intro OExchange Technical Intro Presentation Transcript

    • OExchange
      An Open Protocol Stack for URL-Based Content Sharing on the Web(Quick Geek Remix)
      May 2010
    • What are we trying to do here?
      The Web includes an unbounded number of services for sharing, posting, translating, printing, saving for later, and more
      Goal #1: Provide a simple, default way for users to send any URL-based content to any service on the web
      Goal #2: Allow users to personalize their choices, across tools, publishers, and machines
    • We Need an Open Protocol Solution
      Discover
      Personalize
      Exchange
      A means to associate preferred services with a user
      A way to interrogate and discover services that can accept content
      A common and simple way to send content, using its URI, to a service
      • Support forcurrently-deployed solutions, future new UX, and verbs beyond “share”
      Current-generation tools:
      Focus on sharing
      Take the form of buttons, rows of chiclets, popup menus, toolbars
      Present too many choices; may not even include what the user wants
    • The Basic Solution
      A standard endpoint, and a defined HTTP GET flow to send URLs to that endpoint
      An “Offer” endpoint takes standard arguments (always including URL); has browser control for the transaction
      An XRD-based resource that describes the service
      A “Target XRD” document includes the endpoint and related information about the service
      Host-Meta and page-level Link tags make the service discoverable
      I accept URLs at my Offer endpoint:
      http://<me>/<whatever>?url=<url>&<etc>
      That and some info for humans is in my XRD doc:
      http://<me>/<whatever>/target.xrd
      You can discover it from my host-meta or in-page Link tags:
      rel=“http://oexchange.org/…/related-target”
    • The Offer Flow
      Build on a deployed browser-based paradigm (add “headless” modes once discovery is adopted)
      Enforce URLs as primary content indicators (supporting any tagging schemes)
      Plan for extensibility of verbs (“offer” is the most generic)
      Content source, in a user’s browser
      Receiving service (social network, translator, whatever)
      HTTP GET, usually target=“_blank”
      http://<service>/<whatever>?url=<url>&<etc>
      Service-specific UI; browser session up to service
      Browser session continued
    • About Typing
      We’re ALWAYS sending URLs
      URLs which are viewable in a browser
      URLs which may use any embedded tags (OGP, microformats, etc.)
      We’re optionally sending extra stuff
      Iframe URLs, images, rich media objects
      This gives us
      guaranteed compatibility, without ANY negotiation
      an ability to offer a richer experience for services that support it
    • Personalizing Choices
      If you can send content to any service, and discover new services automatically…
      Let a user store their preferences
      Let all tools, including browsers, access it
      http://<service>
      http://<service>
      http://<service>
      WebFinger lookup
      Personal XRD with OExchange links
      http://<service>/target.xrd
      http://<service>/target.xrd
      http://<service>/target.xrd
      http://<service>/target.xrd
      mary@example.com
      Optional local cache
    • So What?
      For Services
      Receive more content, from a greater variety of tools and content providers
      For Users
      Get the right option at the right time for sharing, saving, blogging, whatever
      Engage with longer-tail communities of interest
      For Publishers
      Get more of your content out, through more efficient share-through
      Don’t have to decide between options
    • Taking it Forward
      Our strategy
      Codify the existing model for basic content exchange on the web, while adding a new discovery capability
      Add new exchange models once this foundation is deployed
      Additional exchange models
      With discovery in place, its easy to standardize more optimized exchange flows
      Headless and return-to-source are primary examples
      User addressing; mutual service negotiation in “Send to Mom” type use-cases
      Learn more at www.oexchange.org