<?xml version="1.0"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Engadget - Comments for IEEE at work on revised Li-ion battery standard</title>
<link>http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</link>
<description>Engadget Comments for IEEE at work on revised Li-ion battery standard</description>
<image>
<url>http://www.engadget.com/media/feedlogo.gif</url>
<title>Engadget</title>
<link>http://www.engadget.com</link>
</image>
<language>en-us</language>
<copyright>Copyright 2012 Weblogs, Inc. The contents of this feed are available for non-commercial use only.</copyright>
<generator>Blogsmith http://www.blogsmith.com/</generator><item><title><![CDATA[Comments on IEEE at work on revised Li-ion battery standard]]></title><link>http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</link><guid isPermaLink="true">http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</guid><description><![CDATA[By the way check out the latest release from The Exploding Misfits coming out soon on myspace.<br><br>(They're the ginchiest!)]]></description><dc:creator><![CDATA[strider_mt2k]]></dc:creator><pubDate>Sep 27th 2006 8:47AM</pubDate></item><item><title><![CDATA[Comments on IEEE at work on revised Li-ion battery standard]]></title><link>http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</link><guid isPermaLink="true">http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</guid><description><![CDATA[it's not like anyone at engadget knows anything about batteries...]]></description><dc:creator><![CDATA[battery person]]></dc:creator><pubDate>Sep 27th 2006 1:35PM</pubDate></item><item><title><![CDATA[Comments on IEEE at work on revised Li-ion battery standard]]></title><link>http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</link><guid isPermaLink="true">http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</guid><description><![CDATA[I'd love to see an actual corporation run the way IEEE is run.  If their finalization rate determined their successfulness, they'd be long gone by now.<br><br>Don't get me wrong, I love standardization, but there has to be a better way to get things done.]]></description><dc:creator><![CDATA[Wonderboy]]></dc:creator><pubDate>Sep 27th 2006 9:47AM</pubDate></item><item><title><![CDATA[Comments on IEEE at work on revised Li-ion battery standard]]></title><link>http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</link><guid isPermaLink="true">http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</guid><description><![CDATA[Nick is exactly right - the IEEE is the executive which handles the standardization efforts of tens of thousands of volunteers worldwide. In fact, the 802.xx family of standards is actually managed by the IEEE Computer Society's standards group, which is distinct from (and funded separately from) the mainline IEEE standards group.<br><br>As for standards taking so long to finalize - trust me, I've been there. The more important a standard is (i.e. the more money it will cost you to change to conform to it, or the more money it will cost your competitors, or the more impact it has on your other businesses...) the more people get involved. The more people, the more opinions. <br><br>The rules of developing standards *require* the committee to consider and *respond to* every objection. 1000 smart engineers working for 450 companies who see high stakes in the 802.11n standard means the ballot resolution committee probably got drowned in thousands of objections and comments. Since the ballot resolution committee is made up of real people from real companies with real day jobs to do, they can steal at best a week here or a week there to do resolution. It takes significant time to properly address concerns.<br><br>The IEEE has strict rules about standards. A bad electrical standard can cost real users dollars and time; but a bad standard can also cost people their lives. Damage as a result of excess EMI or RFI is bad. A standard which doesn't nail everything down, which allows two people to make products which conform to what the standard says but still don't work with each other, is a bad standard. Getting it right takes time.<br><br>If you don't believe me - get involved. Join a standards committee. Pretty much anyone can.]]></description><dc:creator><![CDATA[Jason Zions]]></dc:creator><pubDate>Sep 27th 2006 6:03PM</pubDate></item><item><title><![CDATA[Comments on IEEE at work on revised Li-ion battery standard]]></title><link>http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</link><guid isPermaLink="true">http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</guid><description><![CDATA[Jason wrote:<br>"Nick is exactly right "<br><br>Hahaha. Except that they deleted my comment. Nothing like censoring the truth, eh?]]></description><dc:creator><![CDATA[Nick]]></dc:creator><pubDate>Sep 27th 2006 11:01PM</pubDate></item><item><title><![CDATA[Comments on IEEE at work on revised Li-ion battery standard]]></title><link>http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</link><guid isPermaLink="true">http://www.engadget.com/2006/09/27/ieee-at-work-on-revised-li-ion-battery-standard/</guid><description><![CDATA[It's a shame the dropped Nick's comments, but I have to say, Jason pretty much nailed it.<br><br>Engadget should chagrined to have allowed an obvious misrepresentation of the situation between the wifi and battery standards groups. Trust me; these are NOT the same folks. The commenter was either incredibly naive, or trying to spread misinformation.<br><br>To his point on .11n, yeah, the latest I've heard; comments in the thousands, and at least half of them are 'technical' not 'editorial', so there is still a big chunk of work going on.<br><br><br>]]></description><dc:creator><![CDATA[Been there Done That...]]></dc:creator><pubDate>Sep 28th 2006 12:10PM</pubDate></item></channel></rss>
