<?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/"
		>
<channel>
	<title>Comments on: Voice APIs a Part, Not The Solution</title>
	<atom:link href="http://phoneboy.com/2347/voice-apis-a-part-not-the-solution/feed" rel="self" type="application/rss+xml" />
	<link>http://phoneboy.com/2347/voice-apis-a-part-not-the-solution</link>
	<description>Simplifying Network Security, Telecom, Gadgets, and More!</description>
	<lastBuildDate>Fri, 19 Mar 2010 15:26:22 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Discover From Your Favorite Topic or Web Page: www.programmableweb.com/apitag/telephony</title>
		<link>http://phoneboy.com/2347/voice-apis-a-part-not-the-solution/comment-page-1#comment-26636</link>
		<dc:creator>Discover From Your Favorite Topic or Web Page: www.programmableweb.com/apitag/telephony</dc:creator>
		<pubDate>Wed, 20 Aug 2008 16:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/?p=2347#comment-26636</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] http://mashable.com/2008/05/19/letsprov/ (friendfeed apis socialmedia mashable)  &#160;[Discover] Voice APIs a Part, Not The Solution http://www.phoneboy.com/2347/voice-apis-a-part-not-the-solution#comment-26502 (telephony apis voip [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="http://phoneboy.com/wp-content/plugins/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[...] <a href="http://mashable.com/2008/05/19/letsprov/" rel="nofollow">http://mashable.com/2008/05/19/letsprov/</a> (friendfeed apis socialmedia mashable)  &nbsp;[Discover] Voice APIs a Part, Not The Solution <a href="http://www.phoneboy.com/2347/voice-apis-a-part-not-the-solution#comment-26502" rel="nofollow">http://www.phoneboy.com/2347/voice-apis-a-part-not-the-solution#comment-26502</a> (telephony apis voip [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PhoneBoy</title>
		<link>http://phoneboy.com/2347/voice-apis-a-part-not-the-solution/comment-page-1#comment-26505</link>
		<dc:creator>PhoneBoy</dc:creator>
		<pubDate>Fri, 18 Jul 2008 08:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/?p=2347#comment-26505</guid>
		<description>Ok, I forgot about open APIs, you&#039;re right, Dan.

@Jack what&#039;s the saying, the great thing about standards is that there are so many to choose from? :)</description>
		<content:encoded><![CDATA[<p>Ok, I forgot about open APIs, you&#8217;re right, Dan.</p>
<p>@Jack what&#8217;s the saying, the great thing about standards is that there are so many to choose from? <img src='http://phoneboy.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Rynes</title>
		<link>http://phoneboy.com/2347/voice-apis-a-part-not-the-solution/comment-page-1#comment-26503</link>
		<dc:creator>Jack Rynes</dc:creator>
		<pubDate>Thu, 17 Jul 2008 13:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/?p=2347#comment-26503</guid>
		<description>Dameon,

Nice follow-up to yesterdays conversation. Pulling together all of pieces (API, reliable scalable network and the consulting) is the path to true value and revenue.

@DAN - You have a good point about API&#039;s based on industry standards. Web Services simply points to a &quot;standard&quot; used through out the internet. My only concern with &quot;standards&quot;, being an old telecom guy, is that there always seems to be some nuance to each (SS7, ISDN, etc) making it difficult for interoperability. That said, SIP, VoiceXML and CCXML seem to moving in the right direction.</description>
		<content:encoded><![CDATA[<p>Dameon,</p>
<p>Nice follow-up to yesterdays conversation. Pulling together all of pieces (API, reliable scalable network and the consulting) is the path to true value and revenue.</p>
<p>@DAN &#8211; You have a good point about API&#8217;s based on industry standards. Web Services simply points to a &#8220;standard&#8221; used through out the internet. My only concern with &#8220;standards&#8221;, being an old telecom guy, is that there always seems to be some nuance to each (SS7, ISDN, etc) making it difficult for interoperability. That said, SIP, VoiceXML and CCXML seem to moving in the right direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan York</title>
		<link>http://phoneboy.com/2347/voice-apis-a-part-not-the-solution/comment-page-1#comment-26502</link>
		<dc:creator>Dan York</dc:creator>
		<pubDate>Thu, 17 Jul 2008 13:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/?p=2347#comment-26502</guid>
		<description>Dameon,  Good summary... but I still keep beating the drum: APIs need to be based, as much as possible, on *open standards*.  Otherwise:  1) an API becomes just yet-another-way for a vendor to lock you in to their specific platform; and 2) developers can&#039;t use their existing knowledge and have to learn how to use *your* new API.  We as an industry need to use open standards-based APIs as much as possible so that we can build a larger pool of people who can build voice applications... the more developers there are who can do it, the more voice apps... 

So in my opinion we need to be promoting the use of protocols like SIP, VoiceXML, CCXML and other similar technologies and protocols.

Thanks for raising all these points about APIs,
Dan  (who, yes, does work for Voxeo, but would be making these points about open standards regardless of who my employer was)</description>
		<content:encoded><![CDATA[<p>Dameon,  Good summary&#8230; but I still keep beating the drum: APIs need to be based, as much as possible, on *open standards*.  Otherwise:  1) an API becomes just yet-another-way for a vendor to lock you in to their specific platform; and 2) developers can&#8217;t use their existing knowledge and have to learn how to use *your* new API.  We as an industry need to use open standards-based APIs as much as possible so that we can build a larger pool of people who can build voice applications&#8230; the more developers there are who can do it, the more voice apps&#8230; </p>
<p>So in my opinion we need to be promoting the use of protocols like SIP, VoiceXML, CCXML and other similar technologies and protocols.</p>
<p>Thanks for raising all these points about APIs,<br />
Dan  (who, yes, does work for Voxeo, but would be making these points about open standards regardless of who my employer was)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
