https://cyber.harvard.edu/projectvrm/api.php?action=feedcontributions&user=Avery&feedformat=atomProject VRM - User contributions [en]2024-03-29T08:56:09ZUser contributionsMediaWiki 1.39.5https://cyber.harvard.edu/projectvrm/?title=Project_ideas&diff=1618Project ideas2007-01-26T00:20:14Z<p>Avery: /* Categories of VRM data */</p>
<hr />
<div>== Upside-down buyer's guide ==<br />
<br />
[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Don Marti writes],<br />
<br />
''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.''<br />
<br />
''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.''<br />
<br />
''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.''<br />
<br />
''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".''<br />
<br />
''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.''<br />
<br />
''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. ''<br />
<br />
Read the whole thing.<br />
<br />
== Categories of VRM data ==<br />
What you've done, like, and want<br />
<br />
Done: Transaction history. Your copy of your transaction/interaction record categorized <br />
<br />
Like: Preferences. Where do you like to sit on a plane, car, color, and size<br />
<br />
Want: Personal RFP. What things do you want to buy and how do you describe your need<br />
<br />
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.</div>Averyhttps://cyber.harvard.edu/projectvrm/?title=Project_ideas&diff=1617Project ideas2007-01-26T00:19:51Z<p>Avery: /* Upside-down buyer's guide */</p>
<hr />
<div>== Upside-down buyer's guide ==<br />
<br />
[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Don Marti writes],<br />
<br />
''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.''<br />
<br />
''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.''<br />
<br />
''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.''<br />
<br />
''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".''<br />
<br />
''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.''<br />
<br />
''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. ''<br />
<br />
Read the whole thing.<br />
<br />
== Categories of VRM data ==<br />
What you've done, like, and want<br />
Done: Transaction history. Your copy of your transaction/interaction record categorized <br />
Like: Preferences. Where do you like to sit on a plane, car, color, and size<br />
Want: Personal RFP. What things do you want to buy and how do you describe your need<br />
<br />
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.</div>Averyhttps://cyber.harvard.edu/projectvrm/?title=Expressions_of_Relationships&diff=1616Expressions of Relationships2007-01-25T23:56:47Z<p>Avery: /* Some interesting questions / thoughts */</p>
<hr />
<div>These are my rough notes of what is being written on the flip chart during the VRM meeting breakout on 2006-01-25.<br />
<br />
==Types of Relationships==<br />
* marriage<br />
* business partnership<br />
* counselor<br />
* subscription<br />
* friendship<br />
* family<br />
* membership<br />
* fanboy<br />
* contract<br />
* employment<br />
* confucian<br />
* mentor / advisor<br />
* citizenship<br />
* blacklist<br />
* champion<br />
* familiar stranger<br />
* colleague<br />
* teacher<br />
* stalker<br />
* neighbor<br />
* patron<br />
* customer<br />
* vendor<br />
* circle of trust<br />
* sponsor<br />
* priest / shaman / rabbi / ...<br />
* advocate<br />
* alumni<br />
* nemesis<br />
* cohorts<br />
* shared experience<br />
<br />
==Expressions of Relationships==<br />
You know it is a relationship when ...<br />
* there are implications for the future<br />
* expectations<br />
* recognition<br />
* subscription<br />
* payment<br />
* tipping<br />
* genealogy<br />
* hate sites<br />
* strong feelings<br />
* recommend<br />
* contract<br />
* employment<br />
* ask advice<br />
* expose yourself to vulnerability ("trust")<br />
* blacklist<br />
* conversation<br />
* stalking<br />
* repeat patronage<br />
* badmouth<br />
* reliance<br />
* federation<br />
* referral/introduction<br />
* sponsor<br />
* invite<br />
* rebuff<br />
* evaluate<br />
* hug / PDA<br />
* advocate<br />
* commenting (e.g. blogs)<br />
* give gifts<br />
* find<br />
* respond<br />
* keep apprised<br />
* request<br />
* extend credit<br />
* support<br />
* vouch<br />
* shared experience<br />
* having coffee<br />
* conferences<br />
<br />
==Dimensions==<br />
* Time<br />
* Transparency<br />
* Intensity<br />
* Frequency<br />
* Commitment<br />
* Control<br />
* Potential to real<br />
* Latent to explicit<br />
* Reciprocity<br />
* Symmetry<br />
* Frequency of interaction<br />
* Cardinality<br />
<br />
== Some interesting questions / thoughts ==<br />
* Are we presuming that relationships are bidirectional? (e.g. crush) No ...<br />
* Relationships are not boolean -- there is a degree, e.g. very close vs. "have heard of some guy.."<br />
* Law/lawyers as a source of a relationship taxonomy<br />
* Confucianism as a source of relationship taxonomy</div>Averyhttps://cyber.harvard.edu/projectvrm/?title=VRM_Meeting&diff=1525VRM Meeting2007-01-03T16:46:34Z<p>Avery: </p>
<hr />
<div>This is a VRM Developers Meeting. Not a conference. <br />
<br />
We want to make this small and focused on development work: who's doing what, who's planning what, and how we can help each other do whatever we're doing.<br />
<br />
The date is January 25 in Redwood City. Details will be up here shortly.<br />
<br />
<br />
Meanwhile this page is also where we sign up. Add your name and relevant links to the list.<br />
<br />
List of attendees:<br />
<br />
* [http://cyber.law.harvard.edu/home/doc_searls Doc Searls]<br />
* http://lid.netmesh.org/images/openid-relying-party-authenticated.gif [http://netmesh.info/jernst Johannes Ernst]<br />
* [http://blog.joeandrieu.com Joe Andrieu]<br />
* [http://www.deborahschultz.com Deborah Schultz]<br />
* [http://xri.net/=drummond.reed Drummond Reed]<br />
* [http://epeus.blogspot.com Kevin Marks]<br />
* [http://haystack.cerado.com/profile/2 Christopher Carfi]<br />
* [http://blog.wachob.com Gabe Wachob] (Its in my home town - can't miss it!)<br />
* [http://www.confusedofcalcutta.com JP Rangaswami]<br />
* [http://www.digisenseinc.com Avery Lyford]</div>Avery