Relationship Icon: We need one

From IIW
Revision as of 12:59, 7 February 2011 by WikiSysop (talk | contribs) (Undo revision 3121 by Igiwydijok (Talk))

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

Convener: Joe Andrieu

Notes-taker: Charles Andres

Attendees:

  • Drummond Reed,
  • Doc Searls,
  • ex AOL guy,
  • Charles Andres,
  • Terry Hayes,
  • Paul Trevithick,
  • Nika Jones
  • Mike Osburn,
  • Phil Windley
  • eve maler (by phone),
  • ian Henderson,
  • Terry Hayes.

Technology Discussed/Considered: We can open a socket, remove some packets a. VRM – r-button – richer than a link button -- creating human relationship b. http – link (you know you were there or not) and where it goes c. tcp/ip – packet/socket/connection


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

We need a relationship icon – what people do with eachother Need to know everything complex about my relationship with….

Asa Hardcastle is creating examples for us to experiment with… we are learning as we go, trying to map the story to a process and code

C – vendor open to rel

D – buyer is open to rel

O – relationship formed

Varients – one magnet greyed out,

CRM – the relationship is some data trail. Period. Relationship means some action.


What are the actions and what state is displayed via the button?

Markup in the page to show (you, or your agent)

Actions associated with the button.

Architecturally significant thing; relationship actions and state both offered by the vendor and aggregated from your relationship services. (what Switchbook is doing) Adding richer value by providing enhanced services beyond the software that creates the relationship.

Third party Augmentation (relationship) Services – Adaptive Blue (Project Glue)

Data is not connected to services now.

Make it social – connect with friends about things you ‘visit’ – i.e. a fave movie – Blockbuster is a relationship service, but not VRMing it yet.

Data and service portability

Silos are ok as long as you can get your data out, and use it/link it somewhere else.

We are dealing with action and state (of relationship)

Given you have the rel-button, we can have richer semantics than just a link.

State, capture state, user agent renders metadata about that.

History.

So what is the VRM angle on this? What are the VRM Actions?

  • users have some control over (this) and you (vendor) should be interested in it.
  • Something that happens on the user customer side that the vendors need to adapt to, rather than the usual way of treating customers like cattle or worse.

Can it be used with “The Mine” ? (Adriana’s Alec Muffet’s project)

Can it be viral (like London war chalking)

Where does button appear?

Examples shown on i-phone by Doc – buttons – podcasting.

Streaming,

Live streaming

Podcasting (cached locally)

Non-live streaming (never cached locally)

Mike’s view:

  • what happens when you click on the r-button?
  • Shared model
  • Today you have hicost low value connections
  • Yellow page ads no relationship
  • Switch to low cost high value relationship (requires trust – or spiffs)
  • Here as I as a vendor are willing to offer to you
  • Customer selects

Actions you can take without the vendor (e.g. bookmark the relationship)

Actions that the vendor can take after you take some action to develop the relationship

Context:

    • bank is a vendor when you are interacting with the bank.
    • Bank is a partner when I write a check
  • What you can do unilaterally (customer)
  • Ditto (business)
  • What you can do together