<?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: More &#8220;Windows Phone 7&#8243; Confirmation</title>
	<atom:link href="http://msftkitchen.com/2010/02/more-windows-phone-7-confirmation.html/feed" rel="self" type="application/rss+xml" />
	<link>http://msftkitchen.com/2010/02/more-windows-phone-7-confirmation.html</link>
	<description>Heard of Windows 8? Learn about Windows 8, Office 15, Windows Mobile 8 and more. The future of Microsoft, here @ MSFTKitchen: The #1 Windows 8 resource!</description>
	<lastBuildDate>Sat, 12 May 2012 12:21:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rey Hounshell</title>
		<link>http://msftkitchen.com/2010/02/more-windows-phone-7-confirmation.html/comment-page-1#comment-130763</link>
		<dc:creator>Rey Hounshell</dc:creator>
		<pubDate>Thu, 21 Jul 2011 15:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://msftkitchen.com/?p=1748#comment-130763</guid>
		<description>I鈥檓 pleased, I must say. Really not usually can i go through a blog that鈥檚 both educative and amusing, and let me tell you, you might have hit the nail on the head. Your idea is outstanding; the problem is whatever inadequate people are talking smartly about. Now i&#039;m very happy which I found it in my search for something relating to this.</description>
		<content:encoded><![CDATA[<p>I鈥檓 pleased, I must say. Really not usually can i go through a blog that鈥檚 both educative and amusing, and let me tell you, you might have hit the nail on the head. Your idea is outstanding; the problem is whatever inadequate people are talking smartly about. Now i&#8217;m very happy which I found it in my search for something relating to this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Wark</title>
		<link>http://msftkitchen.com/2010/02/more-windows-phone-7-confirmation.html/comment-page-1#comment-40459</link>
		<dc:creator>Karl Wark</dc:creator>
		<pubDate>Thu, 09 Dec 2010 20:49:08 +0000</pubDate>
		<guid isPermaLink="false">http://msftkitchen.com/?p=1748#comment-40459</guid>
		<description>Strong Points: -The people who wrote it are absolutely knowledgeable: They&#039;ve loads of information about nearly every single subject they talk about -Chapter organization: the chapters are well organized as far as the order in which to expose a reader to the topics, creating as much as the subsequent. Weak Points: -In just about just about every chapter, the author(s) regularly mention or compare the subject being discussed with an actual Cisco item. Although lots of individuals agree they make very good merchandise, which includes myself, this book needs to be about the VoIP as a standard (as the title implies), not Cisco’s products. -The author(s) clarify most topics by throwing tons of (or an excessive amount of) information and facts at the reader, such as exceptions to the rule - all within the exact same sentence. A number of the key points are not even mentioned or elaborated on, whilst the author goes to point out small or insignificant particulars. -While discussing the history of Telephony and VoIP technology, using acronyms is unavoidable, but the author(s) overuses them to the extreme. At occasions, you can find synonym acronyms that the author(s) will use randomly and interchangeably inside the similar chart, diagram or sentence; this is highly confusing. Also, there&#039;s no glossary, so you&#039;ve to waste time flipping back through the pages to look up acronyms they spelled out as soon as. Quite a few acronyms usually are not even defined - they are just mentioned as casual speak to define other acronyms (so have your web browser ready). -The author(s) often define topics and acronyms sections or chapters right after they are 1st mentioned. This is also very confusing and frustrating. -The book is filled with charts and graphs. Most of them you seriously need to study to understand simply because they use many little pictures for which there is no legend, and some you flat our will need an electrical engineering degree to know.</description>
		<content:encoded><![CDATA[<p>Strong Points: -The people who wrote it are absolutely knowledgeable: They&#8217;ve loads of information about nearly every single subject they talk about -Chapter organization: the chapters are well organized as far as the order in which to expose a reader to the topics, creating as much as the subsequent. Weak Points: -In just about just about every chapter, the author(s) regularly mention or compare the subject being discussed with an actual Cisco item. Although lots of individuals agree they make very good merchandise, which includes myself, this book needs to be about the VoIP as a standard (as the title implies), not Cisco’s products. -The author(s) clarify most topics by throwing tons of (or an excessive amount of) information and facts at the reader, such as exceptions to the rule &#8211; all within the exact same sentence. A number of the key points are not even mentioned or elaborated on, whilst the author goes to point out small or insignificant particulars. -While discussing the history of Telephony and VoIP technology, using acronyms is unavoidable, but the author(s) overuses them to the extreme. At occasions, you can find synonym acronyms that the author(s) will use randomly and interchangeably inside the similar chart, diagram or sentence; this is highly confusing. Also, there&#8217;s no glossary, so you&#8217;ve to waste time flipping back through the pages to look up acronyms they spelled out as soon as. Quite a few acronyms usually are not even defined &#8211; they are just mentioned as casual speak to define other acronyms (so have your web browser ready). -The author(s) often define topics and acronyms sections or chapters right after they are 1st mentioned. This is also very confusing and frustrating. -The book is filled with charts and graphs. Most of them you seriously need to study to understand simply because they use many little pictures for which there is no legend, and some you flat our will need an electrical engineering degree to know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Windows Phone</title>
		<link>http://msftkitchen.com/2010/02/more-windows-phone-7-confirmation.html/comment-page-1#comment-8669</link>
		<dc:creator>Windows Phone</dc:creator>
		<pubDate>Mon, 28 Jun 2010 21:55:55 +0000</pubDate>
		<guid isPermaLink="false">http://msftkitchen.com/?p=1748#comment-8669</guid>
		<description>it looks promising
i am waiting for it</description>
		<content:encoded><![CDATA[<p>it looks promising<br />
i am waiting for it</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ultrabrief: Microsoft Canada slips up and mentions &#8220;Windows Phone 7&#8243;</title>
		<link>http://msftkitchen.com/2010/02/more-windows-phone-7-confirmation.html/comment-page-1#comment-3150</link>
		<dc:creator>Ultrabrief: Microsoft Canada slips up and mentions &#8220;Windows Phone 7&#8243;</dc:creator>
		<pubDate>Fri, 12 Feb 2010 18:12:13 +0000</pubDate>
		<guid isPermaLink="false">http://msftkitchen.com/?p=1748#comment-3150</guid>
		<description>[...] Canada accidentally put some information on their site mentioning it and it has since been removed. Microsoft Kitchen was quick enough to grab these screenshots while the info was still [...]</description>
		<content:encoded><![CDATA[<p>[...] Canada accidentally put some information on their site mentioning it and it has since been removed. Microsoft Kitchen was quick enough to grab these screenshots while the info was still [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rhys</title>
		<link>http://msftkitchen.com/2010/02/more-windows-phone-7-confirmation.html/comment-page-1#comment-3098</link>
		<dc:creator>Rhys</dc:creator>
		<pubDate>Thu, 11 Feb 2010 22:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://msftkitchen.com/?p=1748#comment-3098</guid>
		<description>My understanding is that &quot;Windows Phone&quot; is the name of a specific platform type, like PocketPC used to be, and that the OS itself will still be named Windows Mobile.</description>
		<content:encoded><![CDATA[<p>My understanding is that &#8220;Windows Phone&#8221; is the name of a specific platform type, like PocketPC used to be, and that the OS itself will still be named Windows Mobile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://msftkitchen.com/2010/02/more-windows-phone-7-confirmation.html/comment-page-1#comment-3055</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 11 Feb 2010 15:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://msftkitchen.com/?p=1748#comment-3055</guid>
		<description>How about this Tweet from the Microsoft Partner Network:

Steve Ballmer to host Windows Phone Press Conference on Feb 15. Watch live or on-demand: http://bit.ly/b7wL2g (via @msuspartner)</description>
		<content:encoded><![CDATA[<p>How about this Tweet from the Microsoft Partner Network:</p>
<p>Steve Ballmer to host Windows Phone Press Conference on Feb 15. Watch live or on-demand: <a href="http://bit.ly/b7wL2g" rel="nofollow">http://bit.ly/b7wL2g</a> (via @msuspartner)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

