<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Introspection &#187; MRCP</title>
	<atom:link href="http://blog.jeffhaynie.us/category/mrcp/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.jeffhaynie.us</link>
	<description>Jeff Haynie on business and technology in Silicon Valley</description>
	<lastBuildDate>Mon, 01 Feb 2010 18:32:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>ZiVva to acquire Vocalocity</title>
		<link>http://blog.jeffhaynie.us/zivva-to-acquire-vocalocity.html</link>
		<comments>http://blog.jeffhaynie.us/zivva-to-acquire-vocalocity.html#comments</comments>
		<pubDate>Wed, 28 Jun 2006 15:41:06 +0000</pubDate>
		<dc:creator>Jeff Haynie</dc:creator>
				<category><![CDATA[CCXML]]></category>
		<category><![CDATA[MRCP]]></category>
		<category><![CDATA[SIP]]></category>
		<category><![CDATA[Speech]]></category>
		<category><![CDATA[VoIP]]></category>
		<category><![CDATA[VoiceXML]]></category>

		<guid isPermaLink="false">http://blog.jeffhaynie.us/?p=27</guid>
		<description><![CDATA[If you have not already heard, today ZiVva annouced the acquisition of Vocalocity.  You can read the press release to get a little more information.
This does mark the end to my involvement with Vocalocity.  It is a very bitter sweet ending.  I would like to thank Jim White of Sutter Hill Ventures, [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>If you have not already heard, today <a href="http://www.zivva.com">ZiVva</a> annouced the acquisition of Vocalocity.  You can read the <a href="http://biz.yahoo.com/prnews/060628/clw037.html?.v=57">press release</a> to get a little more information.</p>
<p>This does mark the end to my involvement with Vocalocity.  It is a very bitter sweet ending.  I would like to thank Jim White of <a href="http://www.shv.com">Sutter Hill Ventures</a>, Mike von Grey of Revenue Med, Kelly Conway of <a href="http://www.eloyalty.com">eLoyalty</a>, Sig Mosely of Imlay Investments, Said Mohammadioun, Lou Santora and all the other close advisors of the company, employees and investors &#8211; and most of all, I would like to thank Mike Dickerson, my partner and loyal friend for 5 tough and rewarding years at Vocalocity.  I will forever be indebted to you and all the people that made Vocalocity a success.</p>
<p>At Vocalocity, we had the concept of taking complex and ever changing communications standards such as VoiceXML, CCXML and SIP, to name a few, and making software that completely followed the standard and that was available on an OEM basis to larger customers.  To name a few: Microsoft, IBM, Aspect and Siemens.  We also strongly believed that standards in the communications world would completely disrupt their proprietary cousins, over time.   Time being the operative word.  Standards have taken over, but at at rate that is hard to track.   SIP has become so mainstream that some of the largest carriers in the world are using it natively.  <a href="http://www.w3.org/Voice">VoiceXML</a> has completely taken over the IVR and next generation interactive voice application space.  MRCP is now the de-facto specification for interfacing with a speech server.</p>
<p>However, standards also have competition &#8211; not just from big companies like Microsoft who sometimes choose not to follow them (or better, extend and embrace them).  For example, <a href="http://www.skype.com">Skype</a> is the world&#8217;s largest VoIP network &#8211; and they don&#8217;t use SIP &#8211; at least not natively.  And you can&#8217;t say that&#8217;s because they have a legacy application problem &#8211; they&#8217;re somewhat a new company dispite their size.</p>
<p>Some of the frustration that I always felt as part of my involvement in the standards process is that they move too slow.  Slow on purpose, I understand. But sometimes, too slow for any good.  Technology is evolving at a breakneck pace &#8211; and standards need to evolve on a more practical timeframe, not a timeframe that is suitable for a large research organization.  The <a href="http://www.ietf.org">IETF</a> is quite dramatically different than the <a href="http://www.w3.org">W3C</a> in this regard.  While the W3C moves like a glacier, the IETF moves like a startup.  IETF drafts expire every 6 months, forcing momentum.  But causing lots of drafts that sometimes have not much change.  On the other hand, how many different SIP extension drafts exist?  A lot and that causes some fragmentation.</p>
<p>I don&#8217;t claim to have any answers or even plausible suggestions &#8211; even after 4 years of standards work.  But, it needs to be examined.</p>
<p>To all the former employees of Vocalocity, you&#8217;ll always be near and dear to my heart for your hard work, dedication and friendship.  I wish everyone the best of luck in the future and hope we can work together again.  Please keep in touch.</p>
<hr />
<p><b>Technorati Tags:</b> <a href="http://www.technorati.com/tags/vocalocity" rel="tag">vocalocity</a>, <a href="http://www.technorati.com/tags/zivva" rel="tag">zivva</a>, <a href="http://www.technorati.com/tags/voicexml" rel="tag">voicexml</a>, <a href="http://www.technorati.com/tags/ccxml" rel="tag">ccxml</a>, <a href="http://www.technorati.com/tags/sip" rel="tag">sip</a>, <a href="http://www.technorati.com/tags/ietf" rel="tag">ietf</a>, <a href="http://www.technorati.com/tags/w3c" rel="tag">w3c</a>, <a href="http://www.technorati.com/tags/mrcp" rel="tag">mrcp</a></p>
<img src="http://blog.jeffhaynie.us/?ak_action=api_record_view&id=27&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blog.jeffhaynie.us/zivva-to-acquire-vocalocity.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
