<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Dealing with it</title>
	<atom:link href="http://blogs.law.harvard.edu/vrm/2007/08/31/dealing-with-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/vrm/2007/08/31/dealing-with-it/</link>
	<description>Developing tools for customer independence and engagement with vendors</description>
	<lastBuildDate>Sat, 05 Dec 2009 00:22:38 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Russell Nelson</title>
		<link>http://blogs.law.harvard.edu/vrm/2007/08/31/dealing-with-it/comment-page-1/#comment-503</link>
		<dc:creator>Russell Nelson</dc:creator>
		<pubDate>Mon, 03 Sep 2007 19:34:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/vrm/2007/08/31/dealing-with-it/#comment-503</guid>
		<description>VRM works for anything whose discovery can be automated, even extremely inexpensive things.  Let&#039;s say that I want twenty 10K 5% 1/4watt resistors.  I post that fact in the appropriate format.  I&#039;ve already told various electronics vendors that I want to buy stuff, so they know to watch my RSS feed.  They fetch my RFP, get my identity for my shipping address, compute the shipping cost, and return a fixed-price bid.  My software looks at the bids, and picks the one I think is most appropriate, or alerts me if something interesting looks like it&#039;s happening.</description>
		<content:encoded><![CDATA[<p>VRM works for anything whose discovery can be automated, even extremely inexpensive things.  Let&#8217;s say that I want twenty 10K 5% 1/4watt resistors.  I post that fact in the appropriate format.  I&#8217;ve already told various electronics vendors that I want to buy stuff, so they know to watch my RSS feed.  They fetch my RFP, get my identity for my shipping address, compute the shipping cost, and return a fixed-price bid.  My software looks at the bids, and picks the one I think is most appropriate, or alerts me if something interesting looks like it&#8217;s happening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Warot</title>
		<link>http://blogs.law.harvard.edu/vrm/2007/08/31/dealing-with-it/comment-page-1/#comment-466</link>
		<dc:creator>Mike Warot</dc:creator>
		<pubDate>Sun, 02 Sep 2007 02:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/vrm/2007/08/31/dealing-with-it/#comment-466</guid>
		<description>Well. thanks to blogs and cheap web hosting we can all put out a press release and get ignored like all of the other advertising we all hate. The power isn&#039;t in the ability to publish, it&#039;s in the relationships that tie us together, earning and sharing respect with each other, until some of us become know as the &quot;authority&quot; on a subject.

The ability to send out an RFP (request for proposal) seems to be the guts of VRM. This works well for high ticket items requiring contracts, lawyers, etc.. but it isn&#039;t likely to work for retail items. The key here is once again to build relationships between ourselves, and get some connectivity going, and build up a way for very small companies to essentially do an RFP in terms of a microformat.

You have to specify what you want, URLs work great for that... then you have to be able to publish the RFP... which a retail vendor won&#039;t let you do... you have to provide your own host to publish the RFP on... then hope people will read it.

The provisioning of the connectivity to complete the loop is the tricky bit. Blogs got better once the scale went up because of Google and other search engines. We need the equivalent structure to be able to complete the loop of discovery for VRM.

I&#039;m typing fast, and it makes sense to me now... but I hope it does for someone else as well.


Virginia&#039;s having fun playing with the CD player, so I have a brief moment of grace while she&#039;s distracted. 8)

  --Mike--</description>
		<content:encoded><![CDATA[<p>Well. thanks to blogs and cheap web hosting we can all put out a press release and get ignored like all of the other advertising we all hate. The power isn&#8217;t in the ability to publish, it&#8217;s in the relationships that tie us together, earning and sharing respect with each other, until some of us become know as the &#8220;authority&#8221; on a subject.</p>
<p>The ability to send out an RFP (request for proposal) seems to be the guts of VRM. This works well for high ticket items requiring contracts, lawyers, etc.. but it isn&#8217;t likely to work for retail items. The key here is once again to build relationships between ourselves, and get some connectivity going, and build up a way for very small companies to essentially do an RFP in terms of a microformat.</p>
<p>You have to specify what you want, URLs work great for that&#8230; then you have to be able to publish the RFP&#8230; which a retail vendor won&#8217;t let you do&#8230; you have to provide your own host to publish the RFP on&#8230; then hope people will read it.</p>
<p>The provisioning of the connectivity to complete the loop is the tricky bit. Blogs got better once the scale went up because of Google and other search engines. We need the equivalent structure to be able to complete the loop of discovery for VRM.</p>
<p>I&#8217;m typing fast, and it makes sense to me now&#8230; but I hope it does for someone else as well.</p>
<p>Virginia&#8217;s having fun playing with the CD player, so I have a brief moment of grace while she&#8217;s distracted. <img src='http://blogs.law.harvard.edu/vrm/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /> </p>
<p>  &#8211;Mike&#8211;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
