<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://cyber.harvard.edu/projectvrm/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Avery</id>
	<title>Project VRM - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://cyber.harvard.edu/projectvrm/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Avery"/>
	<link rel="alternate" type="text/html" href="https://cyber.harvard.edu/projectvrm/Special:Contributions/Avery"/>
	<updated>2026-10-02T09:53:06Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.6</generator>
	<entry>
		<id>https://cyber.harvard.edu/projectvrm/?title=Project_ideas&amp;diff=1618</id>
		<title>Project ideas</title>
		<link rel="alternate" type="text/html" href="https://cyber.harvard.edu/projectvrm/?title=Project_ideas&amp;diff=1618"/>
		<updated>2007-01-26T00:20:14Z</updated>

		<summary type="html">&lt;p&gt;Avery: /* Categories of VRM data */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Upside-down buyer&#039;s guide ==&lt;br /&gt;
&lt;br /&gt;
[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Don Marti writes],&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;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 &amp;quot;commodity&amp;quot; IT product, the 1U or 2U rack-mount Linux server.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;First step would be to come up with a microformat for a &amp;quot;server RFQ&amp;quot;. At the beginning of the experiment, these could be relatively loose -- just a bunch of &amp;quot;ol&amp;quot;s with &amp;quot;id&amp;quot;s such as &amp;quot;required-parts&amp;quot; &amp;quot;preferred-parts&amp;quot;, &amp;quot;disliked-parts&amp;quot;, &amp;quot;forbidden-parts&amp;quot;, &amp;quot;required-features&amp;quot; and so on.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There would also be a section for &amp;quot;status&amp;quot;, which would be time until buying decision, &amp;quot;deferred&amp;quot; &amp;quot;cancelled&amp;quot; or &amp;quot;ordered&amp;quot;. 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&#039;s human-readable in a browser and (2) you can add free-form commentary on what you like or don&#039;t like in a server.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;So you want to buy a server? Write your server RFQ, put it up with a rel=&amp;quot;tag&amp;quot; link to a Technorati tags page for &amp;quot;server RFQs&amp;quot;. and another tag link to a new, unique tags page just for that one, such as &amp;quot;joe@example.com-2005-07-09&amp;quot;.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Along come the vendors who want to sell you a box, and are naturally watching the &amp;quot;server RFQs&amp;quot; tag like hawks, I mean like some animal that doesn&#039;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 &amp;quot;joe@example.com-2005-07-09&amp;quot;. This is highly automatable, but careful, vendors -- don&#039;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.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;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&#039; Guide! When you buy the server, you change the &amp;quot;status&amp;quot; field on the RFP to &amp;quot;ordered&amp;quot;, 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&#039;re serious in the future so they&#039;ll pay attention to your RFQs. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Read the whole thing.&lt;br /&gt;
&lt;br /&gt;
== Categories of VRM data ==&lt;br /&gt;
What you&#039;ve done, like, and want&lt;br /&gt;
&lt;br /&gt;
Done: Transaction history.  Your copy of your transaction/interaction record categorized &lt;br /&gt;
&lt;br /&gt;
Like: Preferences. Where do you like to sit on a plane, car, color, and size&lt;br /&gt;
&lt;br /&gt;
Want: Personal RFP. What things do you want to buy and how do you describe your need&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Avery</name></author>
	</entry>
	<entry>
		<id>https://cyber.harvard.edu/projectvrm/?title=Project_ideas&amp;diff=1617</id>
		<title>Project ideas</title>
		<link rel="alternate" type="text/html" href="https://cyber.harvard.edu/projectvrm/?title=Project_ideas&amp;diff=1617"/>
		<updated>2007-01-26T00:19:51Z</updated>

		<summary type="html">&lt;p&gt;Avery: /* Upside-down buyer&amp;#039;s guide */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Upside-down buyer&#039;s guide ==&lt;br /&gt;
&lt;br /&gt;
[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Don Marti writes],&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;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 &amp;quot;commodity&amp;quot; IT product, the 1U or 2U rack-mount Linux server.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;First step would be to come up with a microformat for a &amp;quot;server RFQ&amp;quot;. At the beginning of the experiment, these could be relatively loose -- just a bunch of &amp;quot;ol&amp;quot;s with &amp;quot;id&amp;quot;s such as &amp;quot;required-parts&amp;quot; &amp;quot;preferred-parts&amp;quot;, &amp;quot;disliked-parts&amp;quot;, &amp;quot;forbidden-parts&amp;quot;, &amp;quot;required-features&amp;quot; and so on.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;There would also be a section for &amp;quot;status&amp;quot;, which would be time until buying decision, &amp;quot;deferred&amp;quot; &amp;quot;cancelled&amp;quot; or &amp;quot;ordered&amp;quot;. 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&#039;s human-readable in a browser and (2) you can add free-form commentary on what you like or don&#039;t like in a server.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;So you want to buy a server? Write your server RFQ, put it up with a rel=&amp;quot;tag&amp;quot; link to a Technorati tags page for &amp;quot;server RFQs&amp;quot;. and another tag link to a new, unique tags page just for that one, such as &amp;quot;joe@example.com-2005-07-09&amp;quot;.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Along come the vendors who want to sell you a box, and are naturally watching the &amp;quot;server RFQs&amp;quot; tag like hawks, I mean like some animal that doesn&#039;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 &amp;quot;joe@example.com-2005-07-09&amp;quot;. This is highly automatable, but careful, vendors -- don&#039;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.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;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&#039; Guide! When you buy the server, you change the &amp;quot;status&amp;quot; field on the RFP to &amp;quot;ordered&amp;quot;, 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&#039;re serious in the future so they&#039;ll pay attention to your RFQs. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Read the whole thing.&lt;br /&gt;
&lt;br /&gt;
== Categories of VRM data ==&lt;br /&gt;
What you&#039;ve done, like, and want&lt;br /&gt;
Done: Transaction history.  Your copy of your transaction/interaction record categorized &lt;br /&gt;
Like: Preferences. Where do you like to sit on a plane, car, color, and size&lt;br /&gt;
Want: Personal RFP. What things do you want to buy and how do you describe your need&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Avery</name></author>
	</entry>
	<entry>
		<id>https://cyber.harvard.edu/projectvrm/?title=Expressions_of_Relationships&amp;diff=1616</id>
		<title>Expressions of Relationships</title>
		<link rel="alternate" type="text/html" href="https://cyber.harvard.edu/projectvrm/?title=Expressions_of_Relationships&amp;diff=1616"/>
		<updated>2007-01-25T23:56:47Z</updated>

		<summary type="html">&lt;p&gt;Avery: /* Some interesting questions / thoughts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are my rough notes of what is being written on the flip chart during the VRM meeting breakout on 2006-01-25.&lt;br /&gt;
&lt;br /&gt;
==Types of Relationships==&lt;br /&gt;
* marriage&lt;br /&gt;
* business partnership&lt;br /&gt;
* counselor&lt;br /&gt;
* subscription&lt;br /&gt;
* friendship&lt;br /&gt;
* family&lt;br /&gt;
* membership&lt;br /&gt;
* fanboy&lt;br /&gt;
* contract&lt;br /&gt;
* employment&lt;br /&gt;
* confucian&lt;br /&gt;
* mentor / advisor&lt;br /&gt;
* citizenship&lt;br /&gt;
* blacklist&lt;br /&gt;
* champion&lt;br /&gt;
* familiar stranger&lt;br /&gt;
* colleague&lt;br /&gt;
* teacher&lt;br /&gt;
* stalker&lt;br /&gt;
* neighbor&lt;br /&gt;
* patron&lt;br /&gt;
* customer&lt;br /&gt;
* vendor&lt;br /&gt;
* circle of trust&lt;br /&gt;
* sponsor&lt;br /&gt;
* priest / shaman / rabbi / ...&lt;br /&gt;
* advocate&lt;br /&gt;
* alumni&lt;br /&gt;
* nemesis&lt;br /&gt;
* cohorts&lt;br /&gt;
* shared experience&lt;br /&gt;
&lt;br /&gt;
==Expressions of Relationships==&lt;br /&gt;
You know it is a relationship when ...&lt;br /&gt;
* there are implications for the future&lt;br /&gt;
* expectations&lt;br /&gt;
* recognition&lt;br /&gt;
* subscription&lt;br /&gt;
* payment&lt;br /&gt;
* tipping&lt;br /&gt;
* genealogy&lt;br /&gt;
* hate sites&lt;br /&gt;
* strong feelings&lt;br /&gt;
* recommend&lt;br /&gt;
* contract&lt;br /&gt;
* employment&lt;br /&gt;
* ask advice&lt;br /&gt;
* expose yourself to vulnerability (&amp;quot;trust&amp;quot;)&lt;br /&gt;
* blacklist&lt;br /&gt;
* conversation&lt;br /&gt;
* stalking&lt;br /&gt;
* repeat patronage&lt;br /&gt;
* badmouth&lt;br /&gt;
* reliance&lt;br /&gt;
* federation&lt;br /&gt;
* referral/introduction&lt;br /&gt;
* sponsor&lt;br /&gt;
* invite&lt;br /&gt;
* rebuff&lt;br /&gt;
* evaluate&lt;br /&gt;
* hug / PDA&lt;br /&gt;
* advocate&lt;br /&gt;
* commenting (e.g. blogs)&lt;br /&gt;
* give gifts&lt;br /&gt;
* find&lt;br /&gt;
* respond&lt;br /&gt;
* keep apprised&lt;br /&gt;
* request&lt;br /&gt;
* extend credit&lt;br /&gt;
* support&lt;br /&gt;
* vouch&lt;br /&gt;
* shared experience&lt;br /&gt;
* having coffee&lt;br /&gt;
* conferences&lt;br /&gt;
&lt;br /&gt;
==Dimensions==&lt;br /&gt;
* Time&lt;br /&gt;
* Transparency&lt;br /&gt;
* Intensity&lt;br /&gt;
* Frequency&lt;br /&gt;
* Commitment&lt;br /&gt;
* Control&lt;br /&gt;
* Potential to real&lt;br /&gt;
* Latent to explicit&lt;br /&gt;
* Reciprocity&lt;br /&gt;
* Symmetry&lt;br /&gt;
* Frequency of interaction&lt;br /&gt;
* Cardinality&lt;br /&gt;
&lt;br /&gt;
== Some interesting questions / thoughts ==&lt;br /&gt;
* Are we presuming that relationships are bidirectional? (e.g. crush) No ...&lt;br /&gt;
* Relationships are not boolean -- there is a degree, e.g. very close vs. &amp;quot;have heard of some guy..&amp;quot;&lt;br /&gt;
* Law/lawyers as a source of a relationship taxonomy&lt;br /&gt;
* Confucianism as a source of relationship taxonomy&lt;/div&gt;</summary>
		<author><name>Avery</name></author>
	</entry>
	<entry>
		<id>https://cyber.harvard.edu/projectvrm/?title=VRM_Meeting&amp;diff=1525</id>
		<title>VRM Meeting</title>
		<link rel="alternate" type="text/html" href="https://cyber.harvard.edu/projectvrm/?title=VRM_Meeting&amp;diff=1525"/>
		<updated>2007-01-03T16:46:34Z</updated>

		<summary type="html">&lt;p&gt;Avery: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a VRM Developers Meeting. Not a conference. &lt;br /&gt;
&lt;br /&gt;
We want to make this small and focused on development work: who&#039;s doing what, who&#039;s planning what, and how we can help each other do whatever we&#039;re doing.&lt;br /&gt;
&lt;br /&gt;
The date is January 25 in Redwood City. Details will be up here shortly.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Meanwhile this page is also where we sign up. Add your name and relevant links to the list.&lt;br /&gt;
&lt;br /&gt;
List of attendees:&lt;br /&gt;
&lt;br /&gt;
* [http://cyber.law.harvard.edu/home/doc_searls Doc Searls]&lt;br /&gt;
* http://lid.netmesh.org/images/openid-relying-party-authenticated.gif [http://netmesh.info/jernst Johannes Ernst]&lt;br /&gt;
* [http://blog.joeandrieu.com Joe Andrieu]&lt;br /&gt;
* [http://www.deborahschultz.com Deborah Schultz]&lt;br /&gt;
* [http://xri.net/=drummond.reed Drummond Reed]&lt;br /&gt;
* [http://epeus.blogspot.com Kevin Marks]&lt;br /&gt;
* [http://haystack.cerado.com/profile/2 Christopher Carfi]&lt;br /&gt;
* [http://blog.wachob.com Gabe Wachob] (Its in my home town - can&#039;t miss it!)&lt;br /&gt;
* [http://www.confusedofcalcutta.com JP Rangaswami]&lt;br /&gt;
* [http://www.digisenseinc.com Avery Lyford]&lt;/div&gt;</summary>
		<author><name>Avery</name></author>
	</entry>
</feed>