Project VRM - User contributions [en]

Link to Drummond Reed explanation of each R-button state

2009-11-28T11:47:28Z

KruGer:

5Nov2008

On todayâs VRM Standards call, Joe and Asa explained to me the conclusion reached on the last R-Button call that an r-button should be tri-state:

1) Nothing lit up: open (off/completely greyed out)

2) Lit up: open

3) Lit up: closed

Having missed the end of last weekâs R-Button call and not knowing that tri-state was the conclusion, I had posted yesterday an endorsement of the idea that the Left-Side (User) and Right-Side (Vendor) halves of the button should be able to be lit up independently. That reflects the initial five-state conception:

1) Nothing lit up: open (off/completely greyed out)

2) Only left side lit up: open

3) Only right side lit up: open

4) Both sides lit up: open

5) Both sides lit up: closed

So I went into todayâs call thinking that five-state was still an option. Furthermore, one good use case for state #3 (right side lit up: open) was when a user wanted to initiate a relationship with a vendor but the vendor was not âin the systemâ yet, so the userâs only option was to initiate a âproxyâ relationship via a relationship service provider that could subsequently be âdiscoveredâ by the vendor.

However after talking it over with Joe and Asa, I now see why tri-state was the conclusion last week (and why we should stick with it). I volunteered to send this email to the list just to save others from having to run through the same analysis time after time.

What it comes down to is the question of âaffordanceâ: what does the button actually indicate to you, the user, what you can do? In the tri-state model, itâs very simple:

1) Nothing lit up: open ==> no relationship actions are available

2) Lit up: open ==> relationship actions are available but none have been taken yet

3) Lit up: closed ==> at least one relationship action has been taken

When you ask the same affordance question of the five-state model, the mental model gets much more complicated:

1) Nothing lit up: open ==> no relationship actions are available from either side

2) Only left side lit up: open ==> user-defined relationship actions are available but none have been taken yet

3) Only right side lit up: open ==> vendor-defined relationship actions are available but none have been taken yet

4) Both sides lit up: open ==> both user- and vendor-defined relationship actions are available but none have been taken yet

5) Both sides lit up: closed ==> at least one relationship action has been taken

Not only does this require the user to understand the conceptual difference between user-defined relationship actions and vendor-defined relationship actions, but the problem remains that once the user takes ANY action, the button closes and the user has no way of knowing whether it was a user-defined action or a vendor-defined action.

Net net: Joe, Asa, and I agreed that it would be much simpler to stick to the tri-state model for the r-button itself, and then present the range of actions â which may vary anywhere from simple user-defined options (âopen a proxyâ) to simple vendor-defined options (âbuy thisâ) to extremely rich options (an entire right-button menu) via a context-sensitive menu displayed by the local relationship agent.

Hope this helps,

=Drummond
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

Expressions of Relationships

2009-11-28T11:42:30Z

KruGer: /* Some interesting questions / thoughts */

These are my rough notes of what is being written on the flip chart during the VRM meeting breakout on 2006-01-25.

==Relationships vs. Expressions==
* [http://socialcustomer.typepad.com/vrm_expression_matrix.pdf Relationships v. Expressions (PDF)]

==Types of Relationships==
* marriage
* business partnership
* counselor
* subscription
* friendship
* family
* membership
* fanboy
* contract
* employment
* confucian
* mentor / advisor
* citizenship
* blacklist
* champion
* familiar stranger
* colleague
* teacher
* stalker
* neighbor
* patron
* customer
* vendor
* circle of trust
* sponsor
* priest / shaman / rabbi / ...
* advocate
* alumni
* nemesis
* cohorts
* shared experience
* enemy

==Expressions of Relationships==
You know it is a relationship when ...
* there are implications for the future
* expectations
* recognition
* subscription
* payment
* tipping
* genealogy
* hate sites
* strong feelings
* recommend
* contract
* employment
* ask advice
* expose yourself to vulnerability ("trust")
* blacklist
* conversation
* stalking
* repeat patronage
* badmouth
* reliance
* federation
* referral/introduction
* sponsor
* invite
* rebuff
* evaluate
* hug / PDA
* advocate
* commenting (e.g. blogs)
* give gifts
* find
* respond
* keep apprised
* request
* extend credit
* support
* vouch
* shared experience
* having coffee
* conferences

==Dimensions==
* Time
* Transparency
* Intensity
* Frequency
* Commitment
* Control
* Potential to real
* Latent to explicit
* Reciprocity
* Symmetry
* Frequency of interaction
* Cardinality

== Some interesting questions / thoughts ==
* Are we presuming that relationships are bidirectional? (e.g. crush) No ...
* Relationships are not boolean -- there is a degree, e.g. very close vs. "have heard of some guy.."
* Law/lawyers as a source of a relationship taxonomy
* Confucianism as a source of relationship taxonomy
* A social network that doesn't allow you to include your enemies isn't worth having.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

May 9 2007 Meeting notes

2009-11-28T11:41:36Z

KruGer: /* Action Items */

==Conference Call Notes==
Drafted by Joe Andrieu, May 2, 2007

==IRC==
#vrm at chat.freenode.net

==Other Calls==
[[Category:conference call]]
[[:Category:conference call]]

==Attendees==
* Joe Andrieu
* Iain Henderson
* Dean Landsman
* Kevin Barron
* Doc Searls
* Matt Terenzio
* Drummond Reed
* Nick Givitovsky

==Status==
{|
|'''what'''|| '''who'''||'''when'''||'''status'''
|-
|'''---------- '''|| ''' ---------- '''||''' ---------- '''||''' ---------- '''
|-
|open id on wiki||david ||no date
|-
|static website development||doc, dean, joe, chris ||no date
|-
|group blog/RSS to wiki (venus)||doc||no date||'''up, but only one author'''
|-
|project VRM definition||doc||1 week||'''still working on it'''
|-
|brainstorm Initiatives||all||ongoing
|-
|Set up Jabber Host for conference calls||doc||no date||''new''
|}

Joe: remind Dean about transcript.

==Notes==

===Agenda===
* Update from Doc on Brussels
* IIW
* June 4th Discussion
* Use cases
* VRM blog
* Web page
* Point from last call

===Brussels===
Identity Open Space, hosted by Bret McDowell and run by Kaliya Hamlin.

Great talk given by JP Ragaswami: "Because of" effect of making money "because of" rather than "with" a particular technology.

What Iain is working on is quite a detailed document on B2B VRM.

Ben Laurie invited Doc up to visit Google. He's one of the Apache leaders, now doing stuff for Google.

Good diagram that brought together a bunch of VRM-related concepts. The main thing that came out for Iain was the interest by the Liberty Alliance guys to contribute to VRM. He agreed to join the Liberty Alliance. His hope is that we will join him.

Doc mentions Paul Madsen (of Liberty) had already contributed to the wiki, but it went away.

Paul had presented a working framework that is already workable, using standards-based exchanges for VRM. Liberty is probably the most down-stream of the identity systems for data to be trustably exchanged in an enterprise framework.

One thing we should explore is how to match up technologies like Liberty, like what Iain is working on, with particular use cases and how that would play out. Doc is going to be talking tomorrow/Friday morning with some of the Higgins folks. Higgins is a framework for multiple identity systems. I'd like to outline where some of these different technologies fit in.

Adriana was also there. Iain and she will be meeting tomorrow to continue the conversation. She works with J&J among other companies. Doc met with them last October at a meeting. They are interested in exploring VRM and Adriana is the link into them.

===IIW===
Let's try to set up a call-in conference at one of the break-outs so that folks who can't be there in person can join in for a session.
===June 4===
At Berkman in Harvard, we've set up to have a meeting on VRM. Berkman has an affiliation with the Internet Study Center (or something like that) at Oxford. And they have a really good teleconference set up that might be useful for folks in the UK.

We'll be discussing VRM in the AM and public radio/media in the afternoon.

===Public Media/Public Radio===
On the ride back from Brussels, Doc & Ben had an interesting conversation about the public media effort and Ben thinks that particularly use case has a viable solution using a relatively small number of use cases.

The interesting challenge there is pulling apart transaction and relationship. Generally, it works today by buying membership from a station, which in part means an unending supply of junk mail and solicitations.

What I'd like to do for the Berkman meeting is to come up with ideas for how that might be done. How we might separate the membership relationship from a simple, targeted contribution to a particular program.

So, perhaps we can create a solution cobbling together some technologies, then start working through organizational and political issues to get the solution deployed. There's a national organization, each station has its own issues, and then each producer of the individual shows. All of three have their own concerns and challenges.

Even if it doesn't work... Doc would like to see it fail for political rather than technical reasons. So lets find the technical solution and then work through the politics.

Keith Hopper of Public Interactive suggested that what we need is a new public station or make a new Internet-only national station, in order to try out whatever it is that we are going to do. That could be a working test-bed. It could have its own problems, but since Keith suggested, he might have a better idea of what might be involved with that. PI handles pretty much all the technology for public radio.
===Use Cases===
* Public Radio
* Personal Data Silos
** Customer retain the memory of prior interactions with a particular supplier

Stories: Doc told story about problems with a vendor where the history of the customer service was problematic.

We need a totally agnostic body, a clearinghouse where both vendors and users can go without fear of mining, spamming, or fishery--not Google or Yahoo, etc. But somewhere that vendors & users have equal, shared control of the relationship-related data.

Drummond Reed mentioned his own efforts to solve this problem (commercially).

Looking at the customer-history tracking, what is the minimal set of data-types that need to be presented to each other?

As the customer, you have a specific memory, while the vendor has a general system of data that may not be well-focused or accessible. In helping the end-customer, it is about taking customer knowledge and sharing it with the vendor in such a way to plug it into their system.

Example: in a service relationship, where you appeared in person. So you had to represent that in person and represent that problem coherently. Nick got sent a wrong part by a refigerator company. And had to call a bunch of people. He documented that on his website, and was able to send that information to the next individual.

Another option is how Nordstom's attaches a return-UPC to the item.

The challenge is that each company may or may not accept anyone else's UPC. Which suggests that the easy, semi-automatic documentation of service history controlled by the user, we have a lot more viability, especially with adversarial vendors.

On top of that, we can also record whatever lookup code or case #, that might be provided by the vendors, allowing a hook back into the vendor system, should the vendor be able to respond to it.

Interestingly, the hook provides the fastest way for the vendor to pull up the countervailing evidence to compare with the customer-provided history.

In terms of adoption, this is in some ways related to the web. Somebody had to be first.

Perhaps this is essentially a digital receipt. So, to the extent that we can request digital receipts go to a specific identity. And these "digital receipts" could cover service transactions just as readily as purchases.

Staples is actually pretty forward thinking in this way. Dean shared a frustrating experience that he escalated to the president--cold calling his voice mail--and they actually bent over backwards to fix it.

This may also provide some interesting advantage as an early adopter if they can provide these "digital receipts" back to enterprise customers who might be able to more easily track that as corporate expenses.

===VRM Flowchart===
Someone asked for a VRM flowchart. I think that could be a useful tool, if we can figure out what it means.

There was one Johannes Ernst drew at IIW 2006b. Paul Madsen drew another one at IOS in Brussels.

===Dictionary/Glossary===
It is critical that we have a common terminology, common glossary so as we move forward, we can actually have a clear understanding of what we are doing.

==IIW 2007==
The next major live even for VRM development, evangelizing, and camaraderie is the [http://www.windley.com/events/latest/announcement.shtml Internet Identity Workshop] in Mountain View, May 14-16. Many of us will be there. We hope you can join us.

==Action Items==
{|
|'''what'''|| '''who'''||'''when'''||'''status'''
|-
|-
| || || ||
|}
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

==Next Meeting==

Misc

2009-11-28T11:40:39Z

KruGer:

== Categories of VRM data ==
What you've done, like, and want

Done: Transaction history. Your copy of your transaction/interaction record categorized

Like: Preferences. Where do you like to sit on a plane, car, color, and size

Dislike: Preferences, allergies, etc.

Want: Personal RFP. What things do you want to buy and how do you describe your need

Perhaps there is a service to intelligently inform one category from another. For instance, by looking at a transaction history you can deduce preferences and suggest wants. You always want to sit in the aisle seat and buy milk every week.

== VRM meets DRM ==
Perhaps VRM should stand for Vendor Rights Management as well as Vendor Relationship Management.

Perhaps rights management and relationship management should be the same thing.

Perhaps companies doing DRM wouldn't have to bear the full responsibility for managing the rights involved in relationships. Things could be done by mutual agreement by both sides.

We need to make "rights management" something that is mutual in operation, and mutually beneficial. How should we approach that?
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

Personal Data Stores

2009-11-28T11:39:45Z

KruGer:

Drummond Reedâs â Personal Data Store
With Iain Henderson to address as well

On Board:

PDS:

What should be in it? (at a minimum) and (ideally)
Whatâs it for?

What is its essential characteristics/components

Where does it reside?

Where does it fit in the overall OSI Model and the VRM architecture

Why is it important?

When is it deployed?

How is it managed â what policies apply?

Does it have to be standard? Cabn there be many types?

What are the points of failure?

Drummond â the concept of PDS has been central to VRM

This is to talk about why? And to look specifically at the PDS

One starting point is âWhy is it importantâ/

Another is âwhat is essential?â

When we wrap up, we ask â On what points are we not in agreement?

Iain describes myDex though Slide show

Observation â Enterprise CRM architecture have multiple attributes but only store data for a year. If well designed, âimportant dataâ will be stored in Analytical System and data warehouse. Which holds the atomic level of data and stores it for the duration of a decisionmaking cycle.

Analytical systems tracks who bought what, where and why?==> to anticipate what to do next

First order concern is quality â meaning completeness, accuracy and several other attributesâ¦

Evidence is that âCRM Needs to be fixedâ â spending 200 bps is not enough to fulfill requirements. Okay at collecting info on customer. Not so good on tracking customer/product/outlet info in a usable fashion

Definition of âPersonal Data Store â (admittedly not a helpful term) A generic term to âsource, store, enhance and selectively disclose my personal informationâ

Needs to run on the same principles as the CRMâ¦ Systems will do the doingâ¦.

The personal data warehouse is the missing element.

In CRM the identity layer is at the top end
PDS resides on top. With the sources

Sees 3,500 attributes over 70 years (is what each individual has)

''(Thematic) Individuals have less tools, more attributes to control, fewer resources to monitor and track.''

Craig Burton â it is important and extensible as well.
A: So you need to identify the important attributes versos

To determine whatâs important, just identify what info you might need to get your life started again.

Next slide depicts Interactions and transactions with all sorts of businesses and govât entities. With the Identity Layer at the core.

*No CRM database can handle persona so you go about creating multiple ones to transact and interactx in the world.

Important â This is a logical design, not a physical designâ¦

It has been posited that Interactions are whatâs being monitored and that Transactions are a type of interaction.

Joe Andreiu â says we can get to the Model T version that does okay

Next slide â Current state of Who has what dataâ¦

Was My Data, Your data, Everybodyâs Data, âTheir Dataâ

Everybodyâs data = public domain â all sorts of data thatâs avaialbe.
âTheir Data (or parasitic tailings) â what Experian, Acxiom etc, collect about you

Your dat â include a vendors products /services, policies, pricesâ¦
And guesses regarding view of a customers preferences, requirementsâ¦

Our Data â identifiers, clams,/Assertions and transactionsâ¦

MY DATA â is stuff known only to meâ¦ Circumstances, Assets, Liabilities, preferencesâ¦

There are also back channels which are interactions between the parasites, vendors, and the publicly available stores.

At Liberty Alliance they have been discussing âVolunteered Informationâ

Finally, Thereâs the Target State

In 10 years time 80 percent of customer management prcesses will startywith âMYDATAâ (me)

So the customer will be in more control and overt interactions will be between the vendor

Toxic will be bad for both vendors and customers â they destroy trust.

''Drummond â 3 times Iâve heard that âThe customer is the point of integrationâ (which originated from Joe Andrieu)''

âCustomer as Point of Integrationâ

Joe says âAnalysis and Insightâ revolved around the vendor dataâ¦ It is the source of Googleâs competitive advantage â¦

Craig Burton â but Googleâs source of distrust was doing personal data storage for Google to tag and index

PDS has âroots in two placesâ

1) Doc Searls â personal experience with the medical treatment across several care givers and each introduced errors in their systems so that they could not reconcile or synchronizeâ¦ The conclusion is that it would have been more efficient and less dangerous if Doc had been the single repository providing to access to the data on an as needed basis.

2) The other side is âStymergyâ which is the general term for how ants find the shortest path to food. It is also the answer to a distribution problem for multiple trucks between warehouses. They send out ants randomly, the one that comes back first, his trail is doubled.

Balance between exploration and exploitation. They mark their environment. Joe articulates that the data should be stored centrally and when multiple companies or individuals want access, they should not seek out things from one another. They should get it from the individualâs data store

Stuart- Why wouldnât you just ask Amazon.com or Google to do a better job of making your information accessible to other apps. So I can assemble it at my command from the multiple sources.

Joeâs answer â youâre asking about data portability.
Iain says (itâs because youâd be operating under their terms and conditions)

Joe says it is because personal data store is not just âthe dataâ it is about setting up mechanisms for permissioning information in, out based behind your own front end (called identity)

And youâre going to have all sorts of front ends or âService Specificationsâ (Liberty calls them Service Interface Specification)

Status updates
Addresses
Music ratings
Search Activities
Personal RFPs
Personal Healthcare records
SMTP/POP

And itâs all under your control

Sop the question is whether the hub is about authentication (identity layer)
And permissioning

*** so there is a multi-billion battle raging over control of permissioning for status updates.

Iain â youâre still missing the link between doing data and planning data.

Doc sees the user as the point of integration and also origination.

Else â a problem solving thing which gets brought up.

That is the ossified way that existing systems work
In medical system, fârinstanceâ¦ there is a kiretsu of equipment providers, suppliers etc where it is hard to get data from individuals or companies. Incompatibility between media, age of PC, etc.

You are going to have this architecture work better in some cases rather than others.

Iain, where thereâs failure in ERP or CRM itâs because the system is trying to do too much and gets clogged up.

So you need to make the distinction between getting stuff done and when you have to do long-term planning.

Per Drummond â donât you end up answering the question by establishing the framework for these the service interfaces service provier (Facebook, Myspace, Plaxo)â¦. And those service providers would manage one or more of the service specification intervfaces.

Joe is saying that it is easier to solve and optimize the âshortest pathâ solution for specific tasks then to define the personal data store that does it all.

Iain is saying that it will have to do the analytics earlier and constantly.

Architecturally you sidestep it by providing a service thatâs operational and do it in a way that is consistent with doing the analytical and do it in a way thatâs consistent with identity based permissions.

So you donât have to do them all if you can solve one of them seamlessly.

Drummond will explain what XDI is all about as a protocol:

The idea of getting all sorts of schemas to talk to one another is a real probalem. HtML canât. XML cannot.

About trusted Data sharing. And itâs about permission

Craig says that XDI is not a protocol. It is a language structure

He wants to know âwhat does it resolve toâ if I write a command and it gets abstracted to something that then resolves to the data and its location. So if you want to share some of your data that resides elsewhere, like in multiple banksâ¦

''The Data doesnât have to live at the hubâ¦ But control does''

Craig â it resolves around a URL and then I can react to it based on a structured card

Card
Rule Set
Data set

Resolved to a URL and it gives permission to access to where that data can be found. And enable data set mashup.

E.g. iphone with a GPS Google Map moment. âTell me where the lone palms hotel is in relationship to meâ tell me where I am and where I go.

Itâs mashup that needs to include all that data.

CyberCrack!

Ad active rules to operate on your data store, and the mashup of all the services

I just want to get this group to define the architecture to put it into the hands of the developer community./

E.g. Amazon.comâs EC2 setting up all sort of things (like 30 years of census data)

Q: When you say ârule setsâ do you just mean permissions?

A: (using the MyDex example - ) as a proof of concept, no browser is required. Any program and any entity can subscribe to the other info an dlocation and all or part be âin the cloudâ

Switchbook has all the info distilled on the hard drive, there is a copy in the cloud for back up purposes. It doesnât have to be in the cloud. And thereâs code in the client to handle I/O

When you get to rulesâ¦ You put functionality in the cloud that handles services and can find them in the cloud.

Customer write the rules.

Stuartâ¦ Example is embedding a twitpics or a URL in a twitâ¦ Iâm publishing something that can then be seen by anyone or everyone. Or how do I add a âsmart URLâ to a tweet so that I can publish to everyone, but the URL has a set of criteria behind it or around it that is controlled by the higher order infrastructure.

Can use a medium like Twitter to infect the world with XDI and XRI

If all or portions of your data are addressable, it can be made accessible to the rest of the world. If you make it abstract. If itâs inside the âIdentity Layerâ it can be under the control of the user. One of the key purposes of the next step, which is XDIâ¦ The same format says that I can store the âpermissionsâ (sometimes called ârulesâ) so that I can access the Link contract. So that the read/write instructions can attached to another set of rules to do something like letting the gas company

Go To Wiki.kynetics.com (it explains the rules that Phil Wendly has developed)

Joe says that Grease Monkey does it as well. But Craig Burton says that kineticsâ¦ is what we should be interested in.

Joe says HTML 5 is being deployed now in browsers.

Craig: I would strongly recommend that we do this in a way that is somewhere between Wiki-based and Selecter-based that is Strong foundation for VRM.

Joe, part of this is about deploymentâ¦ âI hate JaSon because it is inherently insecureâ but they have ways to do secure parsing of Jasonâ¦ But it was adopted because it provided trivially easy way to do it insecurely and native to JAVAscript.

We want to play friendly with them.

Question, gas company needs employment data about me. 1 to 1 federation on their own terms. VRM way. Passport agency acts as a node and permissions allows Gas company to get info from passport agency.

Data liquidity is what itâs all about.

Read it as âpermissionedâ or âunpermissionedâ and the reason that there is so much unpermissioned is because âthereâs no technology in useâ to support permissioned. Which is an argument for Portable Permissioning.

Joe-looking at Switchbook in this context is that your identity is stringly around what you give permission for.

Switchbook defines you by your âsearch mapâ itâs a file that is orthogonal to all your other identifiers. Itâs Switchbox has a âSearchMapâ document at its core. It is the context where your current browsing shows where youâve been and what youâve done and all that.

Idea is that we shouldnât get hung up on the protocol right now. Just define how entities interact and figure out the mesh points.

In the IDWSF model, how you talk to the gas company is permissions based. They may send you an email or something and you set it up with your IDWSF model.

Drummond: Now we talk about our questions.

1) Why is it important?

Initial â The thing that will put the individual back in control of personal information. Meaning the information that is important to the person.

Itâs the store that you personally have control of, it could be anything.

Will allow us to be more promiscuous with our data because we know it will be stored in a trusted way.

It is a context for control.

Because if you abuse it, I know your pheromone trail?

Benefit is that it will improve my quality life, based on my decisions.

Itâs important because it is valuable? It can be bartered>

It is economically transformational>

Jim â Like credit cards, this lowered the friction and reduces guesswork and waste from the vendor side. Which increases value.

Best case you provide the best possible outcome for both parties.

It is more efficiently economically. (the economy will operate more efficiently)

It enables what weâre calling the fourth party services (what VRM is promising).

Markâs point â Itâs a way to organize VRM.

What weâre talking about as the personal data store is to create a better marketplace by providing the way the individuals are regarded by buyers/sellers/governments.

It helps people organize their lives. It enhances efficiency and productivity.

Framework for new use conventions that we donât foresee right now (think of browsingâ¦ or logging onto the bank)

Itâs implementable

Now letâs look to points of failure:

Adriana would say that there are point-to-point identity free interactions that donât require this.

Aside â Kim Cameron says that âIdentityâ is not an identifier. It is just a set of claims that require context. You can have a claimless set of claims in a container.

It is about 4 different identifiers:

Authentication
Presentation
Reference ID (how to be reached email address)
Internal ID

This is your identity online

Are there VRM-y things that donât have a personal data store as part of itâ¦ The answer is noâ¦

You need a place for your stuffâ¦

Q: Where does it have to resideâ¦ It could be anywhere as long as itâs accessible by the applications

Q: Isnât really a permission and control hub? Answer is ânoâ it is still about the data with rules established as to the permission and conditions under which

Weâve gone in circles around what is a relationship manager as opposed to a relation service.

Iain says, itâs all about how you operate around the dataâ¦ Need to clarify how to source, store, enhance and selectively disclose data.

Drummond â the other place the Identity comes in is that the idea of the role of the user in terms of control is akin to the control they have over their bank account. But the bank has authority.

The relationship someone has with Equifax, for instance, is Massively Passively

Another parallel is like the spam filter, where we have passive benefit but virtually no control.

Jim Morris asked what this would be like if it were Communist China and there was an argument for centralized â¦ Drummond, from the point of view of market (as opposed to moral), this is the mechanism for giving user control.

This is about distributed planning.

Has anyone looked at giving control of the personal ID store to a centralized trusted entityâ¦

Bullets for tomorrow:

Privacy:
*IP addresses are they trackedâ¦
*Iâm worried about Google tracking activity

User Experience
*complex
*could create opportunity for errors
*Mashing on toes

Conformance and compliance
(if I share data, how will I know if people abide)
a
Reputational authority (how do I know you are who you say you are)

Service dependability
Business dependability

Portability?
Inadequate choice of SPs

Data Breach and fear of data breach (Honey Pot)
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

PAM One night Stands

2009-11-28T11:39:05Z

KruGer:

This VRM Workshop session covered the concept of the Personal Address Manager.

The scene setting points covered:

First Assumption - Privacy
Differences from long running relationships
- Mutual policy negotiation - pain-free
- Default policy bucket
- No identifier
Easy to produce end of relationship artifacts
Win-Win for customers and vendors
- Removing barriers to exit is attractive.
A use case was examined: Single Stop Online Shopping

With Address
With Personal Delivery Service (eg. relationship wth UPS, Fedex etc.)
With Vendor Delivery Service (eg. Vendors own delivery service that respects PAM token)
With Address from Personal Address Manager

Is the "With Address" scenario a Personal Address Manager (PAM) case? However the PAM might be the place where user relationship policies are stored. "With Address" was eliminated as a policy statement by vendors.

The "with Delivery Service" was selected to analyze.

'''Roles: '''
Shopper (S:)
Merchant (M:)

'''Assumption:''''''Bold text'''
Policy Assurance and Warranty

'''Scenario:'''
Step 1.

S: Shop at a compliant store

M: Offer VRM ("use VRM" button on the web page)

Step 2.

S: Click "Use VRM"

M: Endpoint Request

Step 3.

S: VRM Discovery End point - ie. PAM Address pointer

M: Push to provision

Step 4.

S: Provision vendor

S: Give Vendor token (with policy)

M: Policy agreement

M: Use token to get address

M: Use Address

M: Delete

M: Confirmation of End of use

Side notes:

Initiatives are underway to build a policy framework. (SAML and WS-Policy?)

This was a complex discussion to develop the scenario. Edits to refine this discussion can be made on the VRM Workshop Wiki in the Personal Address Manager page.

Also posted to [http://ekive.blogspot.com/2008/07/vrm-and-personal-address-manager.html EKIVE Blog]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

User:Khopper

2009-11-28T11:36:09Z

KruGer:

My [http://www.hopperanalytical.com/blog blog].
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

User Driven Services

2009-11-28T11:33:21Z

KruGer:

User Driven Services â Joe Andrieu

Introduced a series of blog posts for user driven services
See blog: [http://blog.joeandrieu.com/]

Issues that arose that led to the idea of user driven services to tackle the general issues of interactions between individuals and a system

See blog for definitions

But in general â a System is something built for a particular goal

User is an individual â not a computer an actual individual

Services is an interaction that creates value

User driven service definition

âServices that maximize value creation by maximizing user control and authority.â

There are a spectrum of possibilities

And there is a continuum of âuser driven servicesâ

You could argue that Google, for instance, is very user drivenâ¦ on a first order level

But they donât conform to many of the characteristics

# impulse form the User
# Control
# Transparcncy
# Data portability
# Service endpoint portability
# Self hosting
# User generativity
# Improvability
# Self-managed identity
# Duty of Care

Question - what do you see as the value of adding all these criteria over the relatively random stuff thatâs going on

Answer from Joe â this is the basis for many conversations. And the conversation regarding VRM was always future. User-driven gives a way to ground it in specific instancesâ¦ like whether a mobile app to tie into a company internet, he wanted to make it more user-driven.

Weâre part of a huge transformation of our society, started with The Enlightenmentâ¦ just figuring out what it means on the internet

Doc: the problem comes up even since Ben Franklinâ¦

Added it includes time travelâ¦ The pace of correspondence is so much faster

Added 4th party discussion makes it more easy to define crisply and clearly

Now we need to define what âfouth party isâ because âvrm is not about user-driven, itâs about how the end-statement changes everything.â Itâs transformational if you can address the end-state

User-driven has instances. Whereas Fourth-party is a category of participant or service provider (not always acting on behalf of the user)

Google figures that they would win in the âopenâ game with their semantic labeling and they expose their APIs to let them

Joe â for Switchbook, we think our algorithms are better.

Issue raised â âUser driven works for some ?? and not othersâ¦

Doc says â the characteristics define a number of bullets that dictate how you let people in without locking them in and locking them down.

Joe â like Umar Haque (phonetic)â¦

He has some this and shares the core tenet that, weâre not doing a moral argument. Weâre coming from the idea that thereâs money left on the table because of faster response time and less waste.

Itâs economically stupid to do it the old way.

Service enpoint portability â you can change service provider without anyting falling apart

Self-hosting = you control the dagt

User-generative = means that the user should be able to add value

Improvability is the âAâ in NEAâ¦

Self managed ID â to be dealt with

Duty of care

Docâs question â who does this apply to? Different users may attach more or less importance to each one

But the service provider has to do them all and be responsive to all requirements and maintain sustainable advantageâ¦ But not locking people in.

1) reprise: Impulse of user - this is not about data miningâ¦ it is about the system responding to a gesture of intent.

The internet is really good at this.

Q: is this really targeting individualsâ¦ The service needs to be at the architectural level and this is about an individual interacting with a service (that could be a 4th party interacting with a 2nd party on behalf of the first party)

E.g. that will come up is a personal RFPâ¦ but it might benefit from group interaction because it could be group buying

e.g. might be eBay because it aggregates a whole lot of sellers.

Alan Mitchell â says that your describing a cell that interacts with a larger organismâ¦

A: This is the pattern of behaviors that make the cell survivable for the organism to live. Itâs that system level that Iâm trying to describe

Doc: a distinction is that we start with the individual (cell) how do we give it the right nutrients to support VRM, not just consumer â like Consumer Reports. Thatâs not are starting point.

Joe: itâs part of our Jui Jitsuâ¦ where we shift the weight.

Don Marti talks about the upside down buyers guide â putting the buyers in control

2) control â Users control the servicesâ¦ E.g. can

Control is not a great word â but the gang put that down. Users should have control

Also comment that service provider should respect the directives of the user.

Issue is whether this expects too much of the user. You could also grant it to tohers.

Doc â we are pouring all sort of responsibility on the usersâ¦ BUT SO ARE VENDORS â with self-service and all. But then again, we can make control as simple as possible.

The issue is whether there is a âstandard default arrangementâ (policies) which is how the things are all the time.

The fact is that if people donât voteâ¦ Theyâre happy.

Itâs something you tackle at the policy levelâ¦ it is distributable, but fluid. Bo said âepisodicâ you care to control what you care about it.

Next up (not discussed ) is âterms of serviceâ that VRM assertsâ¦

â¨Transparency is straightforward â people let you know what they want you to knowâ¦ Alain asked does it apply to all the discounts and incentives etcâ¦

A: this is about increasing value by maximizing control and authority

Q2: this is a principle of design â so it has to do with how the service is designed.

A: well the system does require design..

Q3- therefore the user is not in control and itâs not transparent.

A: the people who design the system define reality. Because weâre using Web technology and thatâs already defvined. But the term âtransparencyâ has a waterâs edge.

But the question is, âWhere do you draw the line?â like motives, margins and incentives are a big part of transparency.

Allainâs answer is that âfor a fourth party serviceâ transpareny has to include motives and incentives.

Is transparency âfull disclosureâ

A: there are five categories of transparencyâ¦

This is a new dimension of the Caveat Emptor akin to the FDA having all the

Transparency is not a âdictateâ it is something that user driven services will need to be survivableâ¦ and it means clear understanding of policy.

Alain â weâre getting to the heart of the organizational world where the vendor needs to assert what it does not intend to be transparent.

Darius â in the real world, the service provider will publish service agreements and people will operate under it and it will either work or it wonât.

It is not the primary place where people make a decision.

Q: is there a registry where people could log on and check

Bill Washburn â there should be a dialogue around a quantitative approach to transparency to a qualitative view regarding âwhat should be the major areas of concern.â

So this will be rescheduled to tomorrow.

Suggestion is to talk about âdefining 4th party services in a way that would have a ârulebookâ with criteria that should be conformed toâ

Joe was wondering whether you could apply these criteria to Web based activityâ¦ like SMTP or Web Hosting.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

VRM Marketing

2009-11-28T11:32:11Z

KruGer:

Scumbag Marketers-

Dean lays down the law :

We need enterprise buy in for this to work. (meaning large companies, brick n mortar and online and have CRM)

Don has brought up there there are a lot of companies that might want to sell what looks like CRM and it might not be with the best intent.

Itâs all about money and they may say âwhatâs in it for me?â

We have a few candidates in mind â¦ we know the right person there. Itâs the highest of C persons because it has to come from the top or else weâre fighting our way through all the little fiefdomsâ¦ Because they have to be told

Pushback â Chris: look at Frank Eliason at ComcastCares who did grassroots, Twitterbased end-run.

Deb-Based on experience with P&G going to the top and pushing down even with smart big companies could be hard. So higher ups and infulentials

* Weâve agreed on Influentials and horizontal

Phil Wolff â another challenge, might be to understand the systems they are using and pull through with an existing vendors.

Sean, VRM isnât going to replace CRMâ¦ Itâs not a replacementâ¦ Think about Oracle/Sun for example, they may be incorporating VRM into part of their solution.

* So we have to take a multi-pronged approach
* We have to target each and speak in their language.

Gam â At sephora, they started at the top and were pushed progressively down to the group that was doing Facebook and they were only interested in their âthe Fan siteâ so then it got totally diffused and sent out.

Sean says weâre tight but we still donât talk in a way that has appeal horizontally among non-geeks

Doc says that there are a few people who get it the first time out. And now we (this group) needs to get out their with a set of stories that highlights the curb appeal

Weâve played down the marketing VRM until some code has been written and there are some examples out there.

Weâve been watching the best people rising and the people who really get it doing some cool stuff.

Now within 6mo to a year. Weâll have PublicRadio. Weâll have Gamâs thing andtcetera. And Debâs gonna have the one pager.

Debâs observation â there are all sorts of consultants saying âyou donât bet itâ and evangelizing around Searchi optimization and blogging.

Deb has community managers at CPG, that means they get that. The future of e-commerce is the next step and âthis is it.â

Dean is channeling Allan â he says that weâre making a statement and getting internal buy in. The mission now should be to get buy in from them and get them to pay something like $10K.

Deb says, they need a real story.

Chris says â We have two products nowâ¦ One was VRMâ¦ The next one is a very distinct product which is âa seat at the table to influence creation of VRMâ

It is Access, privilege and Influence and it should have a price attached to it.

Don â there is definitely value to them. We just have to bring it to their attention.

Chris is saying once again that it has value to them

There will be more of a story when the ClueTrain Manifesto update comes out it will clarify the connection.

Conceptual DNA exists.

Doc says also â by bureaucratizing what we do, some good things happened, but thereâs some organization issues.

* Joyce, Judi, Dean and Renee are going to blend things back together. Renee Lloyd has the best way to articulate this and get the organization.

Dean: Big Company buy in will get companies getting big and small companies interested.

Doc has confidence that the major CRM companies are going to buy into this. Doc is planning to have a combined CRM/VRM session and CRM will sponsor, attend and bring customers.

Q: is there going to be a certification process. And The 4th party concept will be baked in. And certification will protect the concept and clarify. There will be a VRM seal of approval.

Per Dean: VRM as a brand is not sexyâ¦ And itâs not our consumer brand.
Doc says that like the word ATM, people use them but necessarily use the term

Seanâs observation â the name isnât as important as the fact that we have more clay on the piece and, besides, the naming folks at McCann or whatever will âmake a hashâ of any name we might come from

Philâs idea â there are two sides that will make this work. Weâve been focusing on the plumbing sideâ¦ And not the moms and pops or the people that are using it.

Sean is saying that there are stories to be told
Deb says that we need the idiot CNN reporter can say the narrative

Jeff Schwartzâ¦ Agreed that itâs not ready,

Chris Anderson and Tim OâReilley are not sold on it. But some others might be.

Sean: need the manifesto, need the North Star,

Paul: thereâs not one user story, There are many orthogonal ones.

Deb: What we should do is have Sean, Doc or Dean give their elevator pitch.

And Whatâs your story to Mom.

Dean â Big go hears: These days we know that people have more communications platforms where you hear them speak. They are telling you what you had used as predictive, you can now get directly from them.

We enable this data to come in and we make it so you can use info from both sides.

Deb: weâve heard that this is social media stuff is happening. Does it help me sell more stuff.

Paul â said that thereâs a fourth party story for the shopper.

Doc: starts with a question:

Which do you hate more, loyalty cards or bad customer service? And dependeing on which one you go down that path.

Then the story is that the companies are already outsourcing their customer service to you. This is your chance to take better control of that.

Jeff asks: why would a vendor want you to give control to the customers?

Doc: Ask what do you hate most about your business
A: Guessworkâ¦ You can get rid of the waste that occurs because of guess work

* Weâre equipping pull as VRM turns push into pull.

Thereâs so much buzz about listening to your customer and enterprise âgets thatâ but theyâre using market research data, customer research, and market effectiveness studies.

We need to use âthe equippingâ wordâ¦ Ergo not the monitoring stuff

Don â the difference between marketing salesâ¦ Tell the marketing guy that VRM shortens the sales cycles, increases loyalty, costs lessâ¦

Sales guy â¦ you tell them that they gotta have it.

Jeff Schwartz â says the good thing is to say things

Cover Fear of loss and Desire for gain

Sean says â this levels the playing field between big companies and you. You can interact with them eye-to-eye, peer-to-peer. No more loyalty cards. Iâm doing it to GMâ¦

Leveling the playing field is the big deal.

Philâs asking whether we have a shopping list regarding the talent we need

Sean says that we need a grassroots movement sort of structure.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

VRM2008 Phil and Paul get married (BT)

2009-11-28T11:30:47Z

KruGer:

Phil Whitehouse and Paul Downey presented their early thoughts on VRM.

Paul presented a slide deck which can be seen here: http://www.slideshare.net/psd/vrm-wedding/

Phil then presented a TiddlyWiki file showcasing Getting Married as a case study. This file can be seen here: http://www.osmosoft.com/wedding

This led towards a discussion on the potential role of brokers in a VRM engagement. A blog post and video exploring this idea can be seen here: http://philwhitehouse.blogspot.com/2008/04/vrm-tiddlywiki.html
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

VRM2008

2009-11-28T11:29:18Z

KruGer: /* Thanks */

This is the base page for VRM2008 at the European Identity Conference in Munich April 21-22, 2008.

If you are at the unconference, please feel free to contribute here. Just click the edit button. If there is no edit button, first create an account or log in. Once you are logged in, you can also click on the "edit" links for each section.

==Sessions==
This will become a session list. Enclose Session names in double brackets and it will become a link to a separate page for that session. This is the easiest way to create a new wiki page for your session. Even better, if you prepend the session name with VRM2008, we can guarantee it will be unique for the unconference. Then you can use a "pipe" | character to have a more user friendly name. See the Personal Address Manager session for an example:
* [[VRM2008 Personal Address Manager|Personal Address Manager]]
* [[VRM2008 User-centric Search|User-centric Search]]
* [[VRM2008 Higgens/OpenIDSAML InfoCards as VRM enabler]]
* [[VRM2008 VRM and Advertising]]
* [[VRM2008 Phil and Paul get married (BT)]]
* [[VRM2008 Rel Button]]
* [[VRM2008 Business Value/Aspects of VRM]]

==Attendees==
Please feel free to add yourself as an attendee, with any contact information you might want to offer to others interested in VRM.
*Doc Searls
*Joe Andrieu (facilitator) mailto:joe@switchbook.com
*Bart Stevens (facilitator) mailto:bart.stevens@ichoosr.com
*Charles Andres mailto:candres@parityinc.net
*Phil Whitehouse mailto:phil.whitehouse@gmail.com
*Paul Downey

==Thanks==
Joe Andrieu and Bart Stevens would like to extend a special thanks to Kuppinger Cole and Joerg Resch for their gracious support and sponsorship. This meeting wouldn't have been possible without them.

We'd also like to thank all the participants who took the time to join us for the conversation. You are the folks who create the potential for meetings like this to create real value for all of us.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

Services

2009-11-28T11:27:56Z

KruGer: /* Work in Progress */

'''''Working Draft'''''

An introduction to VRM Services and how Use Cases inform our work on VRM. (Formerly called Use Cases.)

==Existing Work==
*Service/[[Use Case Brainstorming]]
*[[Services Under Development]]
**[[:Category:Working Draft|Working Drafts]]
***[[Personal Address Manager Service]]

==Definitions==
First, a Service is a bundle of functionality that provides a complete set of value for users.

Second, A Use Case is a distinct, complete transaction between an actor and the system. A service is a collection of supported Use Cases.

; Transaction: an actor initiated interaction with the system to produce a specific benefit.

; Actor: any entity, human or automated, that initiates and drives a transaction in order to create value for itself or its beneficiary. Users include end-users, administrators, vendors, vendor's CRM systems, and customers. Every VRM Service will be developed with specific focal actors in mind while incorporating the needs of all supported users.

; System: An implemented service that provides a bundled set of functionality for actors. VRM Services implement a few focal use cases and multiple supporting use cases in order to provide value to actors. Think of Services as a convenient way to organize VRM functionality into implementable systems.

==The Requirements Model==
Third, in developing a complete VRM Standard, we will create several documents, which will define exactly what value the system will product for which actors. These documents together comprise the Requirements Model for the Standard.

; Actors: A list of all Actors supported by the system.
; Roles: A list of all Roles support by the system, specifying one or two focal Roles. Roles specify an Actor in terms of their relationship with the system so that we know why they are interacting, what they need to do, and what they expect from the system. More formally, a Role is an abstract collection of needs, interest, expectations, behaviors, and responsibilities characterizing a relationship between a class or kind of actors and a system.
; Role Map: A visual representation of the supported Roles and their relationships to one another.
; Profiles: A detailed description of each Role's expectations, capability, and requirements for the system, forming an operational context for that particular role. Developed to enough detail to distinguish what this particular Actor needs from the system design.
; High Level Use Cases: A list of all supported use cases in the system, identifying all focal and required use cases by title, ordered by priority.
; Scenarios: Prose descriptions of a Role's interaction with the system as one example of the Use Case that explains the context, the interaction, and the benefit. Each Use Case requires at least one Scenario.
; Abstract Use Case Narratives: An implementation and technology-free chronological ordering of Actor intention and System responsibilities for a particular use case. Based on one or more specific Scenarios. The abstract narrative defines the specific, yet technology-free, interactions that are required for the use case. These narratives will be normative, that is, they will ultimately define the requirements of the functioning system.
; Specific Use Case Narratives: Implementation-specific sequences of Actor action and system response for a use case. These narratives will be illustrative, that is, they will show how a particular set of technologies can implement a particular use care--or how a specific set of technologies might require or suggest changes to the use case.
; Use Case Diagrams: Both abstract and specific use cases may be diagramed visually to represent the transaction flow between various system components. For abstract use cases, the diagrams will be normative. For specific use cases, they will be illustrative.
; Use Case Maps: A visual representation of the multiple use cases that comprise a particular service and their relationship to one another.
; Constraints & Requirements: In addition to responding to specific use cases appropriately, every Service shall define its own set of constraints and requirements to complete the specification of the service. Many requirements will be applicable to most, if not all, VRM services, such as those inspired by tenets of data portability and user-centric identity. When mapping out the first use case, it became clear that the core Use Cases were already substantially met by such online services as Plaxo and LinkedIn, raising the question of what would actually make a Change of Address service VRM-compliant. That led directly to a handful of simple requirements that assure the user and vendors have appropriate access and controls.
; Technology Review: A review of existing technologies that can be leveraged to implement a complete service, either directly--by incorporating the technology into a deliverable solution, or indirectly--by learning from the technology to assure a more complete solution.
; Formats & Protocols: The data formats and protocols that are required for implementing the service. This includes interoperable data formats as well as open standard transport protocols for moving data around.

==Standards and Compliance==
Third, we propose that any implementation that fully implements all of the normative requirements of the Requirements Model for a VRM Service, including all constraints and interoperability requirements, meets the VRM Standard for that Service.

Toward that end, the normative documents for the Requirements Model will be drafted, revised, and vetted via an open process, accessible to anyone. Our expectation is that the governing committee of the VRM effort, and the VRM Standards Committee in particular, will oversee the development of new services from brainstorming through to publication. The VRM Standards Committee will Propose complete standards to the governing committee once sufficient development and public review demonstrates to the committee that such a standard is ready for publication. Ultimate authority for publication will remain with the governing committee itself; we anticipate VRM Standards being published as "Recommendations" in similar spirit to long standing Internet Engineering Task Force (IETF) practices.

The VRM [[Compliance Committee]] will oversee compliance to published standards, authenticating vendors right to claim their technology or services are "VRM Compliant."

==Process==
As a Service is defined by its working group, it will proceed through different levels of maturity.

;Working Draft: any work at a stage before the working group considers it to be a complete spec. Straight numeric progression of versions, e.g., WD 1, WD 2, etc.
;Working Specification: approved by the working group as a specification, but not yet at the stage where it has been approved by the VRM powers-that-be. At this stage the key goal is to âproveâ the spec via implementations and interop testing. A Working Specification can go back into more Working Drafts if the Working Group decides further revisions are needed. Another straight numeric progression of versions, i.e., WS 1, WS 2, etc. This level is achieved by a majority vote of the members of the Working Group.
;Recommended Specification: A Working Spec that has been approved by the VRM powers-that-be. A âfinalâ VRM standard, fixed by version # and suitable for widespread adoption. To become a Recommended Specification, a Working Specification must go through a minimum public review period and have some number of interoperable implementations (OASIS is three; donât know about IETF). Also another numeric progression of versions, i.e., RS 1, RS 2, etc. This level is achieved by a majority vote of the VRM Steering Committee.

==Work in Progress==
The VRM initiative is early in its development. The proposed processes are likely to evolve over time. Given the fluid yet inherently dated nature of wikis and web pages, any particular document may or may not reflect the current--or ultimate--disposition of the VRM community. However, we have to start somewhere. We look forward to your input.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

The role of social enterprises in VRM

2009-11-28T11:26:53Z

KruGer:

VRM and social enterprise

Led by William Heath, Mydex.

If we had an institution which got our interest in VRM going what would it look like?

In the UK, we created a Community Interest Company called Mydex. I'll explain what it is in more detail in a minute, but basically it is a new form of legal entity in the UK which allows for the establishment of profit-making companies, whose core purpose is a community benefit, where most of the profits it generates are reinvested into the community 'cause'.

One of our tasks is educating people around the core issues of personal information empowerment. We have to say it over and over again.

Under the current status quo of organisations centralised gathering and management of customer data, they are ending up with bad â inaccurate, partial, out of date data - while losing customer trust.
Customers meanwhile are having to dealing with many different silos, which they find frustrating and difficult.
The VRM Mydex process puts you in control, you can choose who you do business with. It can invoke independent assertions. Work with added value services.
When individuals are empowered to manage their own data in this way, companies benefit too because they are fed with accurate, timely quality data.
So Mydex is creating an interface which individuals feel they can trust and which is under their control.

Mydex's formal statement of social purpose is that it âlets individuals realise the value of their personal dataâ. Key characteristics of a CIC are:
it works in benefit of community
has the advantages of commercial company â it can take risks, make a profiit
but these profits have to reinvested into its purpose
transparency of operation
directors can be reasonably paid
regulated dividend
No tax advantages but relatively light touch regulation-

There are different types e.g. not for profit cooperative, vs limited by shares.

If a dedicated institution -
what is its scope: what's in it and what's not?
what characteristics âwhat does it need to do to earn its users' trust and love?
global v local; what is its global dimension, what is its local dimension. If it is global, what organisational structure should it adopt. Amex or Visa?

Points from ensuing discussion

It needs to be sustainable.

Reliable

What Governance would people actually trust? It needs to be open.

Immutability so that it can't metamorphose in front of your eyes, to become something other. By regulation; charter.

Alignment to purpose

Leavability â right to delete me. Exit.

Transparency of governance, process, finance.

No cabals (or do cabals sometimes exist only in the mind of the critic?).

Community should be able to kick out directors/accountability.

Open standards.- in a 'global' or local context?
.
All contracts should be public; all specifications for data etc should be public

Portable data.

More on Global vs local:
is it one single corporation; federated â a group of the willing. A coalition.
Clearly some aspects have to be local. Probably some aspects that have to be global.
e.g. language, local law.
Use global to avoid reinventing the wheel â good ideas can be globally accessed. Use the crowd sourcing to your advantage.

It should be the people's Google, (whatever that means

instead of creating global entity, create an entity that defines the community, and let them define their own extensions, and define their own versions.
That model should be chaoridc.

If global, what is our 'community'? Idea of a global definition/guidelines to make this work, is interesting. Technologies, resources, knowledge, influence, relationships.

Degree of proactivity. e.g can raise a war chest to tackle issues the community don't like. e.g to sue evil doers. Talking about compliance â need to protect interests.
Different means of of proactivity â campaigning, dealing with issues once, for all.

Want to be able to innovate â leadership, structure, incentives, On the other hand, don't want politbureau style.

Design things so that everybody can do it: a mental model

scalable, extensible, interoperable;

agnostic about technology

What are the metrics for Mydex to measure its service to the community?.

Money flows:
corporate fees
value added services
VPI fees
member/supporter contributions
membership subscription

The money flows must be aligned to the community interest.
Is Mydex sharing its revenues with me, or is the individual sharing some of its revenues with Mydex.?

Auditability/track how my data is being used. Very like banking: storing personal information so that it earns interest, being loaned to vendors.

Non-discriminatory pricing and access models.

A personal data union.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

Taxonomy issues

2009-11-28T11:25:59Z

KruGer:

Very much a stub...sorry for the current "stream of consciousness" character of this -- will be cleaning it all up as soon as possible.

There's <strong>a lot</strong> of work here. RFPs should allow for widely varying degrees of specificity. Ideally, a seeker should be able to create an RFP for:
<ul><li>a blackberry 7130c</li>
<li>a cell phone with bluetooth and EDGE support</li>
<li>a cell phone costing less than $250</li>
<li>a cell phone</li></ul>
Even before considering the different attributes required by different types of requests (travel planning vs. product purchase, for example) it's clear that creating a workable microformat for RFPs will be a fascinating (and frustrating) process. It's worth noting, though, that work in this area pays off in many ways.

Desirable: RFP attribute "package," optional, linking multiple RFPs. Indicator to vendors that the seeker is interested in the entire package (implicitly asserting that offers that cover the entire package are preferable/required? Or explicit flag?) -- plane ticket RFP, car rental RFP, hotel RFP, linked by package ID. Five different books, linked by package ID. Possibly worthwhile on both ends: seeker only wants A if they can also get B, vendor can tailor offer/discounts based on total package.

Note to self: Marti's "fulfillment" RFP attribute is an elegant addition. Does seem to suggest that authoritative, verifiable identity for vendors goes from "extremely useful" to "non-negotiable," though. Note also that it makes authoritative seeker identity even more significant: if seekers provide feedback that (is | may be) used to establish vendor reputation as an evaluation factor, there's significant incentive to astroturf.

Suggests the desirability of a parallel reputation system that covers both vendors and seekers. Consider how long an entity has had a public presence, RFP/feedback patterns. Unfortunately seems to also suggest that there could be an actual need for some third-part(y|ies), handling the seeker/vendor DB stuff outlined in the VRM diagram: in addition to pointers to requests/offers, the archive retains history. In this case I guess one would want as many competing versions as possible, so that clients can poll multiple and use their own systems to resolve differing data.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]
[http://www.cinsel-sohbet.com cinsel sohbet]

September 09 2008 Conference Call

2009-11-28T11:25:02Z

KruGer:

Topic: Relbutton working meeting

== Attendees ==

* Keith Hopper
* Dean Landsman
* Iain Henderson
* Britt Blaser
* Matt Cooperider
* Joe Andrieu
* Drummond Reed
* Chris Carfi
* Doc Searls

== Action Items ==
* Drummond send out link to IDTBD google doc notes
* Use [http://cyber.law.harvard.edu/projectvrm/edit/Talk:R-button discussion page] on r-button for discussion, thoughts, ideas, questions
* Update format and content for [[R-button Functional Specification]] page
* Dean to ask Sean and crew about "r-button"
* Pick date for convening at Berkman re: VRM + Public Media
** Keith check with Barbara Applebee
** Who could do prototyping? Asa? Leonard Lynn? Phil Jacob? Britt Blaser? Should all coalesce in a single meeting?
* Update r-button image (ccarfi)
* What are those toolbar icons called in firefox?? (dsearls)

== Agenda notes, questions, comments ==
* Functional spec & Digital ID world
** Meeting held on 9/9 on volunteered personal information button. Agreed that it should it be the same as the r-button - to be deployed by pariity
* [[R-button]] page and requirements that Doc has created
** Idea from Andre - browser plug-in icon (toolbar / add-on items) that represents r-button functionality
* [http://barcamp.org/PublicMediaCamp Public Media Barcamp]
* Use convening power of Berkman to bring together VRM incorporating a Public Media audience: show off and follow-up
* Sean / marketing update
** Trying to schedule a call for this week
* iPhone update - budgets submitted, waiting for CPB confirmation, 'direct giving' scheduled for
* Update from Digital ID World - check google doc notes on IDTBD google groups
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

R-button Functional Specification

2009-11-28T11:24:04Z

KruGer:

(Some suggested spec categories if you're looking for a place to get started [[User:Khopper|Khopper]] 17:45, 2 September 2008 (EDT))

== Universal Characteristics / Attributes ==

== Core Capabilities ==

== R-button States ==

[[Image:pic1.jpg]]

[[Link to Drummond Reed explanation of each R-button state]]

== Expected Behavior ==

== Design Affordances ==

== Use Cases ==
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Project ideas

2009-11-28T11:20:25Z

KruGer:

== Upside-down buyer's guide ==

[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Don Marti writes],

''Doc has been contemplating business, identity and vendor lock-in, and makes me think about an interesting experiment -- use links, tags, and a microformat to help people buy a "commodity" IT product, the 1U or 2U rack-mount Linux server.''

''First step would be to come up with a microformat for a "server RFQ". At the beginning of the experiment, these could be relatively loose -- just a bunch of "ol"s with "id"s such as "required-parts" "preferred-parts", "disliked-parts", "forbidden-parts", "required-features" and so on.''

''There would also be a section for "status", which would be time until buying decision, "deferred" "cancelled" or "ordered". If and when the idea got more popular, the RFQ could be more detailed, and sites and apps could offer server RFQ construction wizards. The nice thing about using a microformat is that (1) it's human-readable in a browser and (2) you can add free-form commentary on what you like or don't like in a server.''

''So you want to buy a server? Write your server RFQ, put it up with a rel="tag" link to a Technorati tags page for "server RFQs". and another tag link to a new, unique tags page just for that one, such as "joe@example.com-2005-07-09".''

''Along come the vendors who want to sell you a box, and are naturally watching the "server RFQs" tag like hawks, I mean like some animal that doesn't want to eat you. Like Easter Bunnies? Vendor sales person checks your RFQ, makes a page for you with links to matching products and a rel=tag link to "joe@example.com-2005-07-09". This is highly automatable, but careful, vendors -- don't spam. A future web-based product configurator should be able to crawl a server RFQ page and come up with a good quotation in response.''

''Now, you, the buyer, just watch the RSS feed for joe@example.com-2005-07-09 -- hey presto, it turns into your own personalized Server Buyers' Guide! When you buy the server, you change the "status" field on the RFP to "ordered", and add a link to the vendor you bought from. This is to (1) give the good vendors Google Juice and (2) let vendors know you're serious in the future so they'll pay attention to your RFQs. ''

Read the whole thing.

== Categories of VRM data ==
What you've done, like, and want

Done: Transaction history. Your copy of your transaction/interaction record categorized

Like: Preferences. Where do you like to sit on a plane, car, color, and size

Want: Personal RFP. What things do you want to buy and how do you describe your need

Perhaps there is a service to intelligently inform one category from another. For instance, by looking at a transaction history you can deduce preferences and suggest wants. You always want to sit in the aisle seat and buy milk every week.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Privacy issues

2009-11-28T11:18:56Z

KruGer:

Burada tartÄ±Åma iÃ§in olasÄ± bir VRM gizlilik modeli, [dayalÄ± http://www-306.ibm.com/software/data/db2/eas/anonymous/ Beraber IBM'de Ã§alÄ±Åan mevcut araÃ§larÄ±'s]
Â Â
GerÃ§ek dÃ¼nyadan bir Ã¶rnek olarak, hÃ¼cre geÃ§iÅ planlÄ±yorum-telefon taÅÄ±yÄ±cÄ±larÄ± Åubat ayÄ±nda bu yÄ±l, ve ben de yeni bir cep telefonu gerekir. Bu durumda, hangi anonim merkezi bir veritabanÄ± (bir Web sitesi Ã¼zerinden saklayabilir verecek bir VRM sistemi / Web servisi veya yerel P2P istemci bir tÃ¼r iÃ§ine benim lÃ¼zum girebilirsiniz.).

Gelince nasÄ±l bilgi depolamak ve ihtiyaÃ§larÄ±nÄ± belirlemek .... Cep telefonu tespit edebilmek iÃ§in nasÄ±lsa biz var tabi. Ben UPC kodlarÄ± veya baÅka bir kimlik, Ã¼rÃ¼n sunulan ana listeden tercÃ¼me kullanÄ±labilir varsayalÄ±m. Cep telefonu planÄ± giriÅi biraz daha belirsiz olduÄunu. DeÄil nasÄ±l bir tespit olacaktÄ±r, ihtiyacÄ± olan bir mÃ¼Återi formu dayalÄ± baÅka emin .... Dakikada, aile planÄ±, kapsamÄ±, vb gerekli .... (Ben artÄ±k bu kÃ¼Ã§Ã¼k parÃ§asÄ± ... ..:) atlayacaklarÄ±

Sonra ihtiyaÃ§larÄ± kaydedilir, bunlar tek yÃ¶nlÃ¼ karma ile (Åu anda) [http://en.wikipedia.org/wiki/SHA-1 SHA-1] algoritma kullanarak anonim olacaktÄ±r. ÃzgÃ¼n durumuna hala iÃ§inde Ã¶zgÃ¼n veriler, ama sadece onu oluÅturan kiÅiye ulaÅÄ±labilir. DiÄer mÃ¼Återilerin herhangi bir veri ama kendi gÃ¶remiyorum.

Karma giriÅleri ayrÄ± ayrÄ± ve Bayiler tarafÄ±ndan sorgulamak iÃ§in saklanÄ±r. Bayiler paylaÅÄ±lan bir karma anahtarÄ± almak iÃ§in kayÄ±t gerekir. Bu anahtar saÄlayacak eÅsiz, paylaÅÄ±lan kodlarÄ± Ã¼zerinden sorgu mÃ¼Återi ihtiyaÃ§larÄ±na satÄ±cÄ±lar, ancak saÄladÄ±ÄÄ± Ã¼rÃ¼nler sadece.

SatÄ±cÄ±larÄ±nÄ±n mÃ¼Återi veri gÃ¶remiyorum. Benzersiz bir ortak kimliÄi ile sunduklarÄ± Ã¼zerinde sahip Ã¼rÃ¼nleri ile Onlar sadece sorgu verileri. VRM sistemi bir eÅleÅme bulunursa mÃ¼Återi deÄil, SatÄ±cÄ± bildirir.

VRM sistemi isteÄe baÄlÄ± olarak, istatistiksel amaÃ§lar iÃ§in (Ã¼rÃ¼nler satÄ±lan hits karÅÄ±laÅtÄ±rarak, Ã¶rneÄin), fakat bu ikili hit / hayÄ±r isabet deÄeri olurdu tÃ¼m satÄ±cÄ± olduÄu bir eÅleÅme bulunursa satÄ±cÄ± uyarabilir. Kadar bir Ã¼rÃ¼n veya hizmeti satÄ±n almayÄ± mÃ¼Återi anonim kalÄ±r.

MÃ¼Återilerin bir maÃ§ anonim bir Web sayfasÄ± veya Web Hizmeti iÃ§in belirli bir Ã¼rÃ¼n iÃ§in bir teklif ile bunlarÄ±n AradÄ±ÄÄ±nÄ±z yÃ¶nlendirilmiÅ olacaÄÄ±nÄ± bulunursa bildirilir. EÄer bu satÄ±cÄ± ile Ã¼rÃ¼n takip etmek istiyorsanÄ±z daha sonra o kadar mÃ¼Återiye (sonraki seviyeye) iliÅki almak karar.

EÄer size, tÃ¼m Web Servis tabanlÄ±, araÃ§ toplam inÅa edilebilir ve o zaman ihtiyacÄ± kaydedilen iade edilir sunar karÅÄ±laÅtÄ±rÄ±n. Daha da ileri giderek araÃ§larÄ± Ã¼rÃ¼n ve hizmet deÄerlendirmeleri baÄlamak iÃ§in, inÅa edilebileceÄini ve iÅlemi tamamlamak kez bir karar yapÄ±lÄ±r.

Benim gerÃ§ek dÃ¼nyadan bir Ã¶rnek olarak, bir cep telefonu ve hizmet seÃ§enekleri online anonim iÃ§in, alÄ±ÅveriÅ olur ve bir veya daha fazla Ã¼rÃ¼nleri I, hoÅ Ã§ok Åimdi ne aynÄ± Åekilde ilgileniyorum karar. Daha sonra VRM sistemde cep telefonu tercihleri ve hizmet ihtiyaÃ§larÄ±nÄ± kayÄ±t olur. Benim lÃ¼zum karma olacak ve Bayiler iÃ§in eriÅilebilir karma deÄerlere ekledi merkezi ya da P2P tarzÄ± merkeziyetÃ§i sistemi (yoluyla). KayÄ±tlÄ± cep telefonu satÄ±cÄ±larÄ± bir ben ne zaman ihtiyaÃ§ kaydedilen girilen karma veri (UPCs veya diÄer deÄer) aynÄ± benzersiz kimliklerini kullanarak sorgulayabilir. EÄer bir eÅleÅme's, ben bir teklif haberdar olacaÄÄ±nÄ± SatÄ±cÄ± VRM sistemi. AynÄ± zamanda, cep telefonu servis saÄlayÄ±cÄ± B planÄ± paylaÅÄ±lan kimlikleri ile veya planÄ±n parametreleri ile ihtiyaÃ§larÄ±, planÄ±m sorgu ve beni bir cep telefonu saÄlayÄ±cÄ± ile birlikte bir cep telefonu ve cep telefonu servis listesi sunuyoruz.

Ben anonim Bu teklifleri gÃ¶zden geÃ§ireceÄini ve benim iÃ§in en iyi karar. Bir kez bir kararÄ± var, VRM sistemi veya doÄrudan () Ã¼zerinden satÄ±n devam satÄ±cÄ±sÄ±na baÅvurun olur. SatÄ±n satÄ±cÄ± ile ilk doÄrudan olmayan anonim temas olacaktÄ±.

Bir kez karar ve ulaÅÄ±lÄ±r bir satÄ±n alma yapÄ±lmÄ±Å, ben VRM sisteminden ve artÄ±k benim ihtiyaÃ§larÄ±n kaydÄ±nÄ± kaldÄ±rmak istiyorsunuz belirli Ã¼rÃ¼n veya hizmet iÃ§in teklif alÄ±rsÄ±nÄ±z.

Daha fazla dÃ¼ÅÃ¼nce gerekenler, daha fazla tartÄ±Åma:
Bu model sadece birden Ã§ok satÄ±cÄ± varsayarak Ã§alÄ±ÅtÄ±ÄÄ±nÄ± aynÄ± satmak iÃ§in, biraz kolayca Ã¼rÃ¼n veya hizmet tespit Ã§alÄ±ÅÄ±yoruz. Belirsiz Ã¶Äeler iÃ§in kolayca bu model iÃ§ine (video servis saÄlayÄ±cÄ±larÄ±, tatil seyahat, yemek, diÄer hizmetler), daha fazla dÃ¼ÅÃ¼nce tabi ... uymaz
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikisi]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikisi]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek sohbet]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org sohbet sohbet]
[http://www.siberchat.net sohbet]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net sohbet]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr sohbet gay]
[http://www.sempatim.net seviÅme]

Notes from VRM

2009-11-28T11:12:11Z

KruGer:

''Notes from the notetaker: There was so much covered and so much discussed on this day - I did not attempt to scribe the event. Alas, below are merely my own self-directed thoughts that emerged. Please add your own if you were present.'' -[http://cyber.law.harvard.edu/projectvrm/?title=User:Khopper Keith Hopper]

'''Objective:'''

How can the public broadcasting audience member take greater control of their relationship with public media? (â¦and as the audience becomes the former audience, how does this relationship change?)

'''Background Thoughts:'''

* Relationship does not equal transaction â in envisioning a vendor relationship tool, we need to think beyond just financial transactions (e.g. donation software)
* Incremental, internal change is not what weâre looking for here. Instead, letâs identify new ideas for experimentation on the fringes of the industry. These ideas should allow individuals to flex their creative consumer muscles in this new participatory landscape. Existing public media, broadcasters, shows, and distributors will serve as the relationships, platform, and ethos to leverage
* Letâs not attempt to address or work inside the existing public broadcasting infrastructure â a better strategy might be to 'end-run' a solution that imagines new ideas from a variety of committed individuals and asks for permission from the stations, shows, and distributors to explore these ideas. If the ideas get traction, the existing players can get involved to their level of comfort and in the ways they see valuable
* There seems to be an overlap between what's going on in participatory culture and what exists in public broadcasting. The potential exists to tap a whole new generation of creative consumers who will 'discover' public broadcasting and want to adopt it for its potential as a non-commercial, open network designed explicitly to serve the public. Can we stimulate this adoption?
[[Image:public-radio-participation.jpg]]

* Can we reduce the friction of listener giving? Perhaps provide a capacity to donate directly to shows/programs?
* Project VRM shouldnât code software, but rather lay out ideas, standards, and support for others who can
* What's the device that will eventually replace the radio? How will this impact public radio and the relationship with the (former) listeners?
* What does the long tail of public media look like?
** Leverages democratized tools of production and redistributable media
** Leverages the cheap, fast, and widespread distribution of end-to-end environments and the benefits of aggregation
** Uses filter technology to drive demand down the tail
* If we were to reinvent public radio in an end-to-end environment like the internet, what would it look like? How would it compare to what exists, and what important differences might emerge? Can we fill those gaps?

'''Ideas for action:'''

* Make public radio the 'test project' for a vendor relationship management tool
* Provide a capacity for end-users to publish their iTunes playlists of public radio podcasts â provide a tool or environment that aggregates and features listener playlists
* Is there stuff we can do with RDS (or HD, PAD, etc.), such as publish texting codes for listeners to use in providing feedback or funding linked to specific stations, programs, and times?
* Use the existing NPR podcast directory as a platform for additional capability â specifically, experimentation with an online donation linked to podcasts
* Get a conversation or survey going with the end-users, mashup folks, or those formally known as the audience to get a better idea of needs/desires and to brainstorm ideas for creative production/control over public media
** As a creative consumer, what is it that I want to do with public media? What are my 'lego blocks'?
* Investigate a new model for a public radio station ''not'' centered on broadcast
** Embrace end-user control over programming, funding, content creation, and overall relationship
** Incorporate participatory programming direction (e.g. guest programmers, vote programs into timeslots, etc.)
** Incorporate online-only shows; act as test market for new shows
** Re-invent the traditional show model (ala Radio Open Source) to be truly conversational and participatory (What might this look like?)
** Use financial models like fundable.org to collect threshold capital to fund desired programming
** Use a small terrestrial station to carry stream and get CPB certification and permit audio use in podcasts (whatâs the secret, here?)
* Build a configurable and redistributable âuser-as-public-radio-stationâ model, integrating various streams and podcasts from around the web into a cohesive and personalized internet public radio station (e.g. KPR = Keith Public Radio)
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Interesting Links

2009-11-28T11:10:27Z

KruGer:

[http://cyber.law.harvard.edu/ The Berkman Center for Internet

Stephen Downes - Distributed Digital Rights Management
-- (The 'VRM' of this website is the 'Customer Broker' of the Downes presentations)
-- [http://www.slideshare.net/tag/ddrm Slide shows on DDRM]
-- [http://odrl.net/workshop2004/paper/odrl-downes-paper.pdf Distributed Digital Rights Management: The EduSource Approach to DRM] - presented at ODRL 1.0
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

VRM Hacker Session

2009-11-28T11:08:31Z

KruGer:

'''VRM Hacker Session in London, November 9th'''
Attendees: ''Doc Searls, Ben Laurie, Duncan Cragg, Alec Muffett, Alan Patrick, Alan Mitchell, Iain Henderson, Dave Shaw, Adriana Lukas''

the minimum requirement - flexible enough to built on top of it

* structured goop,
* two way links, and
* access control

-> that's the infrastructure level

access management

underpinning of vrm is structured goop, two way links, access control

Alec's comments in italics throughout the document:

what is the minimum technical requirement that we can specify to create one or many different VRM tools?

we suspect that we will need:

an ontology to describe purchases, objects, anything ... (slang: "structured goop", existing in "blobs" - probably XML)

a syntax and means to describe bidirectional links between objects (so that B knows it is a child of A, and A knows it is a parent of B)
access control of some sort

where do you draw line, single ownership objects and then what we will see is a construct made of lots of single ownership objects

there is an open issue of object ownership; whether a data object ("blob of goop") can/should have multiple owners at a given time

what you do â make any progress- ontology

I want wifi on the plane, how do say that â has to be machine readable

does it have to be machine readable from the start?

the ontology challenge could be huge; for instance if you want to describe that a particular airplane journey provided wifi, how are you going to define that in a machine-readable manner? it would seem impractical to expect some committee to create a series of pre-ordained flags to be create which can describe everything the user wishes to describe. can we / should we ignore the issue of machine-readability at the outset, or might it be better to leave the matter of description open, eg: by designing space for a folksonomy of tags, or some other open-ended means of description?

Next question â how do you express what you want? Objects, data

smaller subdivisions â what's in it

structure â tools UI stuff, it has to produce something

make the UI unstructured but the underlying data structured

some data should have meta data â book has ISBN

QR codes â idea

agree piece of structure,

suck this info into my database

support rich data structures â will arrive by consensus, book author, date of publication, ISBN

when it comes to absolute description of objects, or (more concisely) "binding" a blob of goop to a specific object, then the obvious thing to do is leverage ISBN codes, UPC/Barcodes, and other unique identifiers like those which exist in the real world; referencing them either directly, or in some coded format (XRI?) in the blobs of goop.

click on a page of restaurant and see who from my network commented on it â I want a handle on what they are saying, filter - meta data that says stuff about the data, so I can look at it and context

we imagine that VRM tools will be able to draw together the many blobs of goop which reference the same objects, eg: the many reviews (each, a blob) which refer to a specific restaurant; the tools will provide the ability to search and collate, aggregate and present these blobs in an accessible manner.

* two-way links: protocol for referencing data â http or something â micro web

highly rigid two ways links to stick, URI vs URL

freenet, mutual pointers between pieces data, common information about things, Doc's fave example travel, hotel - my representation of the hotel links to Adriana's representation of the hotel.

The price we pay for distributed information/data not platforms?

the "blobs of goop" are an atomic data format, they should be able to be exchanged and manipulated without dependency upon other larger data structures; however there will likely still be a need to represent hierarchical relatiopnships between blobs; since the objects are atomic, their parent/child hierarchical relations need to be cited in both objects, ie: bidirecionally; a parent cites its children, and a child knows its parent.

Open APIs don't solve the cross-system links? Duncan's point about presentation at google on 8th November

We are taking data away from the silos but the same issues will be there â distributed access

OpenID â works on multiple sites, profile level,

selective disclosure â trusted entities, two proofs are linked together

* structured goop: ontology (Dewey decimal system) [is an example of] how we talk about any subject (eg: wine), assuming creation of an agreement, common understanding or framework for the data, less than language, way of dividing and classifying data, so we can communicate â machine readable => we have to agree that how to express data/facts about a thing

cloud of all variables generated by centralised system but by users

in other words there is an easy way to create a "blob of goop" without requiring some committee to create a DTD which describes the comfort of an airline flight; instead the "blob of goop" is just a container that is described by a bunch of tags which evolve under a folksonomy, ie: are neither pre-defined nor bounded. An interesting concept which arose during the meeting was that a blob could - in addition to the tags which describe it - could contain a "payload" of data held in whatever microformat is most convenient and popular to contain the pertinent, object-specific data. "Blobs" would thus become ubiquitous wrappers for exchange of data payloads (in arbitrary formats) whilst tagging them for indexing, retrieval and to cite authorship, etc.

XRI guys will be at the event in california

extra layer of problem, we are going to define this system of categories, we'll do is pass around tokens and someone else will define it for you â meta data

categories for various objects/data

humans can deal with multiple frames of reference â but computers need a more unified frame of reference

too many things to describe

ontology will emerge? [ie: folksonomy]

Personal RFP? Number â looking it up on the website, I want that

here's a verbal description, clunky

looking for video camera on ebay â different spellings, hyphen

As ever, the challenge to finding what you want on google, ebay, etc, is to work out how someone else will have typed the name of the thing you want - TRV900, TRV/900, TRV-900, TRV900E, ... are all the same video camera, but only if you are a human being who can weave your way through the ambiguity of different naming; some means of disambiguating product lookup would be really beneficial to online purchasers...

something very discrete â looking for something specific, not search query

if a vague search query marketers will crowd in and promise to find you something like this and all your friends will recommend!

Start with specifics â car parts that deal with it, centralise info and email you back

[ie: the story about companies which exist and add value by presenting a single point of contact to a bunch of junkyards; the company will forward your request for (some specific auto-part) to a bunch of junkyards, and let you know who can supply it for you; the junkyards benefit because they get specific queries phrased in terms they can understand, the buyers benefit from saving time; this also happens in the secondhand book market ]

Harvard business schools â MBA students who came back to school â remake the car industry from customers side

social web thing â I don't want to enter what I know about hotels, cross-silo standardisation

no federation across silos

point of integration, the patient is the best side

at the dispersal side â multiple providers, any personal information, that needs to be formalised

is it pull or push?

Define VRM as a social network?

Creator of Jabber â Jeremy, approach to search â distributed way

DTD â template, name, location, price, tagged

CRM it's minimisation of information

high speed internet or not in hotels â tags that orbitz can pick up

four airlines got together â competed with travelocity and expedia

every hotel has its own CRM system â communications are very screwy

different things about connectivity

turn obsessives into search â architect a data system

in long run we need is a common practice, community of practice â mini-communities

how we do routinise, the activities of individuals coalescing about specific activities

first order is you contributing to order and find the hotel I want, how that finds its way into a formal system, that's big enough to call market place and how to change CRM systems to give you more granular information

Open social â trying to do the same thing, sneak that stuff into VRM

the architecture â I belong to many things or want to relate, doesn't have to be linkedIn, Facebook or MySpace but it can be Doc's space or Adriana space

Facebook is evil, facebook mark up language â the old silo, lock-in trick

Proof-Of-Concept Thought-Experiment: create a human-readable microformat to describe a (for instance) hotel stay; get lots of people to post their review (using this microformat) to their existing blogs as standalone articles (blobs of goop) ensuring they tag the postings appropriately, including the tag HOTELVRM. Use Technorati/Google to access, aggregate and search all HOTELVRM postings in the entire world, and a custom AJAX application to present the microformat data in a more attractive manner. Object interrelationships would be implemented via "trackbacks" and comments could be added to the original posting. You would never want to /do/ it like this, of course, but the above gedanken demonstrates the some of the desirable traits - sharing, syndication, aggregation, search, tagging folksonomy (SHERATON, HILTON, SMELLYROOM, BADFOOD, GOODSERVICE) etc... You are mostly missing access control.

the moment you control your personal data â how you get the data shared, how to get ben and alec excited, we have to talk about how to stop it from being shared

the best way to predict the future is to prevent it [Doc quoting someone else]

we are not codifying beer or wine or car part, we won't see wars like around RSS

what are we going to talk about â if the market is going to do that, what's the easier way to do that

answer â reuse shit

Micro Web

P2P, microformats, people, reviews, calendars

user at the centre of the whole thing

if you want to leave it to the market?

Bottom up, people know stuff already you are getting them try to describe it

how about using micro-format for a car part website

nuggets of informations, micro-formats?

Don't sit down with OASIS

viable conversation between Alec, Alan P and Duncan â ask about later!!!

encoded blobs â can you stop that working?

blobelicious

Alec: I think there are three major ways to address the matter of "blobs" ontology - what they should look like, and what they contain:
1) throw the whole thing over to committee, to come up with new DTDs to describe each and every thing VRM might ever want to describe. <object class=teaspoon metal=silver style=baroque,ornate />
2) create a "container" format which exists mostly to provide structure to tags which are created by the users, pure folksonomy (<tag>spoon teaspoon silver pretty spooooon baroquespoon</tag>)

3) as for 2) but make space to employ pertinent microformats.

<blob>

<email>adriana@bigblog.net</email>

<comment>i really like this spoon, i am heartbroken to sell it</comment>

<payload format="uSpoon(Antique)1.0" encoding=raw>

=spoon,value/1000,baroque/47,metal/silver,tarnish+coefficent=42,TZ/UTC+1=

</payload>

</blob>

...my personal bet is that the answer lies between numbers 2 and 3, and that number 1 is impractical. If microformats exist, then reusing them makes sense as the communities of interest will see VRM as a way of querying, swapping and discussing their favourite things.

Doc likes the fact that "long get" is involved in Micro Web â two stage transaction

medical records â form I get as a copy, scan it, card that points to a database

trusted places, surgery, hospital â health authority â custody

disclosure â allow not for profit social enterprises

nobody will trust a profit company

standardised or common way of gather data â this is what you bring to the hospital

product IB â patient needs to be the point of integration for multiple treatments, devices and product

they are siloed in diabetes â take a disease

create the receiving end of VRM organisation â couple of employees tasked with creating with interface

integration â reasonable set of variables facing a patients, list of all things that are JNJ and that are not JNJ

helping the patient formalise to be at the centre

inclusive of doctor-patient relationship

geriatric medicine some VRM mechanism that makes it easier for patient and his doctors to integrate all that records and data

having the patient at the point of integration â from one department to another without any communication â that's happens all the time

triangulation of multiple specialities

they clicked and somebody said, that might be something or other

patients cross fertilise different communities of practice

House series â interesting show because you have doctor who can puzzle things because he is a cross-specialist

can turn every doctor into a House guy

from J&J perspective:
1. look for areas of business where customer data and shared access to it would make a difference to the business itself and its operations, product development, distribution etc
2. look for areas of business where there already is access to data and how it can be enhanced by VRM, what business benefits that would have
3. look for communities related to 1. & 2.
4. familiarise yourself with new approaches and the net dynamics - open source, long tail, attention economy, identity, VRM etc
5.

Doctors might hate the idea â response might be there is too much info to patients, self-diagnoses

you can only help by informing them

Security requirements for VRM include the standard model

1) authentication: the ability to establish an 'identity' for each user of the system
2) authoristion: the ability to establish capabilities/privileges which are strongly bound to an each identity, eg: ability to read, write, or delete blobs...
3) integrity: the ability to protect blobs against modification/forgery/amendments, eg: by use of digital signatures bound to identities
4) secrecy/privacy: the implementation of access controls of data at rest or in motion, so that blobs cannot be read by those without authorisation

Two architectures for implementation of the security model were suggested:
a 'fortress' model, where those who desire access to data must successfully authenticate themselves to the data repository before retrieval.
a 'broadcast' model, where data is broadcast, unicast or published but under encryption, where only those with authorisation possess keys for access

distributed just coz it's sexy? It's a necessary because it's more resilient

Alec: basically the discussion was about: should we consider making a VRM pilot and simplify our lives by making the assumption that the database would be wholly centralised; the answer to that was an emphatic NO; the reason being that working from a perspective of "the data is centralised in a fortress" will lead to thinking that will never be able to accommodate a distributed architecture; whereas there is nothing to prevent an architecture which is capable of distribution in a wholly or partly centralised matter, as a convenience. In short: the web-browser would never have been invented had someone elected to ignore the distributed nature of the Web; instead, they would have merely yet again reinvented the file-browser. So: DESIGN IT DISTRIBUTED, TEST IT DISTRIBUTED, BUT IMPLEMENT IT HOWEVER YOU CHOOSE.

personal data stores â data objects

design it around one big machine everyone will talk to â you are predetermining design

if you design breakable because then it doesn't matter because there are enough distributed machines, VRM lifestyle â approach â embracing distributed model will save a lot of pain in the long run

client- server? Duncan's reminder

P2P solution?

Virgin not trusted because private company, social enterprises trusted more

regulated

trusted storage â telcos, banks, private, public?

QUANGO

where do you stick the data?

credit boom started â CRM was started by financial industry handling a number of customers due to increased demand

flacking â helping to sell something via third party â use and abuse of trust

who would you trust as a company to held your keys?

the whole trusted third party debate â clipper 1994 or 1996?
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Events

2009-11-28T11:06:39Z

KruGer:

== Gelecek Aktiviteler ==

* [Http: / / cyber.law.harvard.edu/projectvrm/VRM_East_Coast_Workshop_2009 VRM East Coast AtÃ¶lyesi 2009], 12-13 Ekim 2009, Harvard Hukuk Okulu, Cambridge, MA gÃ¼ncellenmiÅtir.
* [Http: / / cyber.law.harvard.edu / projectvrm / VRooM_Leadership_Workshop KasÄ±m 2009 Liderlik AtÃ¶lyesi], yeri TBA
* [Http: / / www.internetidentityworkshop.com/ Ä°nternet Kimlik AtÃ¶lyesi 2009 (IIWIX, IIW)], 3-5 KasÄ±m 2009 Bilgisayar Tarihi MÃ¼zesi Mountain View, CA gÃ¼ncellenmiÅtir.

== GeÃ§miÅ Etkinlikler ==

[[VRM West Coast ÃalÄ±Åtay 2009]]

[[VRMworkshop Harvard Hukuk FakÃ¼ltesi, Temmuz 2008]] de

[[VRM Hacker Session]] 9 KasÄ±m 2007 Londra

[http://www.supernova2006.com/ Supernova] 20-22 Haziran 2007 San Francisco

[http://conferences.oreillynet.com/os2007/ OSCon] 23-27 Temmuz, Portland

[http://conference.digitalidworld.com/2007/ Dijital Kimlik DÃ¼nya (DIDW)] 24-26 AÄustos 2007, San Francisco

[http://www.windley.com/events/iiw2007a/announcement Ä°nternet Kimlik AtÃ¶lyesi (IIW)] 14-15 MayÄ±s, 2007, Mountain View, CA

[https: / / events.projectliberty.org / details.php? id = 11 Kimlik Open Space (IOS)], 26-27 Nisan, 2007 BrÃ¼ksel

[[VRM & Genel Notlar Media Workshop]] Berkman Merkezi, 4 Nisan 2007 de
* Takip-6 Nisan 2007 fikir beyin fÄ±rtÄ±nasÄ± kadar kapsar

[http://cyber.law.harvard.edu/identity/Mobile_Identity_Workshop Mobil Kimlik AtÃ¶lyesi], 26 Ocak 2007

[[VRM Notlar] ToplantÄ±], 25 Ocak 2007

[[Ä°nternet Kimlik AtÃ¶lyesi 2006b Notlar]], 4-6 AralÄ±k, 2006
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikisi]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikisi]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek sohbet]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org sohbet sohbet]
[http://www.siberchat.net sohbet]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net sohbet]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr sohbet gay]
[http://www.sempatim.net seviÅme]