<?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: Does Microsoft Care About Web Standards?</title>
	<atom:link href="http://alttags.org/web-standards/does-microsoft-care-about-web-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/</link>
	<description></description>
	<lastBuildDate>Wed, 03 Mar 2010 02:14:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kirk Biglione</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-79</link>
		<dc:creator>Kirk Biglione</dc:creator>
		<pubDate>Sun, 17 Apr 2005 06:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-79</guid>
		<description>Hi hi, I need to stress that this post and the resulting comments have nothing to do with Internet Explorer&#039;s security (or lack thereof).  We&#039;re discussing Microsoft&#039;s lack of standards support and the hacks required to make a standards based web page display properly in the various legacy versions of IE.

Having said that I think it&#039;s probably time I closed this thread.  It&#039;s likely I&#039;ll revisit this issue when IE 7 is released.</description>
		<content:encoded><![CDATA[<p>Hi hi, I need to stress that this post and the resulting comments have nothing to do with Internet Explorer&#8217;s security (or lack thereof).  We&#8217;re discussing Microsoft&#8217;s lack of standards support and the hacks required to make a standards based web page display properly in the various legacy versions of IE.</p>
<p>Having said that I think it&#8217;s probably time I closed this thread.  It&#8217;s likely I&#8217;ll revisit this issue when IE 7 is released.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hi</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-78</link>
		<dc:creator>hi</dc:creator>
		<pubDate>Sat, 16 Apr 2005 23:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-78</guid>
		<description>The reason why there&#039;s so many hacks and bugs for internet explorer is because it&#039;s worth the time for malicious script writers to write stuff that&#039;ll slow down internet explorer (Also why many think firefox is fast when all they have are spywares and stuff attacking internet explorer). If 70% of the population uses Firefox or Netscape, people would be writing bad stuff for firefox and netscape instead of internet explorer and everyone would be saying Internet Explorer is safer and faster.</description>
		<content:encoded><![CDATA[<p>The reason why there&#8217;s so many hacks and bugs for internet explorer is because it&#8217;s worth the time for malicious script writers to write stuff that&#8217;ll slow down internet explorer (Also why many think firefox is fast when all they have are spywares and stuff attacking internet explorer). If 70% of the population uses Firefox or Netscape, people would be writing bad stuff for firefox and netscape instead of internet explorer and everyone would be saying Internet Explorer is safer and faster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Finance-Guru Blog</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-77</link>
		<dc:creator>Finance-Guru Blog</dc:creator>
		<pubDate>Sat, 01 Jan 2005 07:52:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-77</guid>
		<description>&lt;strong&gt;On Standardization, Microsoft...Why?&lt;/strong&gt;
Perhaps what we are seeing, is a manifestation of the issue of patent rights. Microsoft is no stranger to sparring with the W3C on patent issues, such as, for example, a similiar situation that arose in early 1999, and pertaining to CSS and . In an a...</description>
		<content:encoded><![CDATA[<p><strong>On Standardization, Microsoft&#8230;Why?</strong><br />
Perhaps what we are seeing, is a manifestation of the issue of patent rights. Microsoft is no stranger to sparring with the W3C on patent issues, such as, for example, a similiar situation that arose in early 1999, and pertaining to CSS and . In an a&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Levine</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-76</link>
		<dc:creator>Tom Levine</dc:creator>
		<pubDate>Sat, 01 Jan 2005 07:50:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-76</guid>
		<description>Perhaps what we are seeing, is a manifestation of the issue of patent rights. Microsoft is no stranger to sparring with the W3C on patent issues, such as, for example, a similiar situation that arose in early 1999, and pertaining to CSS and . In an article written by Paul Festa at CNET on 2-8-1999, he quotes Microsoft&#039;s Thomas Reardon as stating the following:

&quot;To ensure that the technology that we have submitted will be free from the cloud of potential patent questions...we have typically committed to freely sharing our patent rights, for use in implementing a standard that results from our submission, with other W3C members who are willing to do the same...

&quot;Microsoft agrees that, upon adoption of this contribution as a W3C recommendation, any W3C member will be able to obtain a license from Microsoft to implement and use the technology described in this contribution for the purposes of supporting the W3C recommendation on a royalty-free basis. One condition of this license shall be the party&#039;s agreement to not assert patent rights against Microsoft and other companies for their implementation of the W3C recommendation.

&quot;It would be unreasonable to require a company to develop a technology, submit the technology as a standard, give up its own patent rights in the standard submission, but remain exposed to claims of infringement by other companies, who are themselves free to use the technology and patents of the submitting company,&quot; Reardon wrote.



Now, a very interesting point that the CNET News entry reminds us to remember about 1999, is that Microsoft was a member of the W3C...But so was Netscape, who, on this particular issue, argued the following:



&quot;The original style sheet implementation dates from the mid-70&#039;s,&quot; said Netscape vice president of client products Jim Hamerly. &quot;At least 20 commercial systems have supported style sheets since that time. We view this patent as largely not an issue.&quot;



So, we&#039;re talking about standardizations, on the one hand. But, on the other hand, we&#039;re talking about a conglomeration of corporate entities that are competitive rivals, haplessly mulling around together under the thin umbrella of the W3C, and in the mix of all of this, is the topic of discussion: Namely, technology, patents, and future development, which of course, results ultimately, in future profits, or perhaps the lack thereof.</description>
		<content:encoded><![CDATA[<p>Perhaps what we are seeing, is a manifestation of the issue of patent rights. Microsoft is no stranger to sparring with the W3C on patent issues, such as, for example, a similiar situation that arose in early 1999, and pertaining to CSS and . In an article written by Paul Festa at CNET on 2-8-1999, he quotes Microsoft&#8217;s Thomas Reardon as stating the following:</p>
<p>&#8220;To ensure that the technology that we have submitted will be free from the cloud of potential patent questions&#8230;we have typically committed to freely sharing our patent rights, for use in implementing a standard that results from our submission, with other W3C members who are willing to do the same&#8230;</p>
<p>&#8220;Microsoft agrees that, upon adoption of this contribution as a W3C recommendation, any W3C member will be able to obtain a license from Microsoft to implement and use the technology described in this contribution for the purposes of supporting the W3C recommendation on a royalty-free basis. One condition of this license shall be the party&#8217;s agreement to not assert patent rights against Microsoft and other companies for their implementation of the W3C recommendation.</p>
<p>&#8220;It would be unreasonable to require a company to develop a technology, submit the technology as a standard, give up its own patent rights in the standard submission, but remain exposed to claims of infringement by other companies, who are themselves free to use the technology and patents of the submitting company,&#8221; Reardon wrote.</p>
<p>Now, a very interesting point that the CNET News entry reminds us to remember about 1999, is that Microsoft was a member of the W3C&#8230;But so was Netscape, who, on this particular issue, argued the following:</p>
<p>&#8220;The original style sheet implementation dates from the mid-70&#8242;s,&#8221; said Netscape vice president of client products Jim Hamerly. &#8220;At least 20 commercial systems have supported style sheets since that time. We view this patent as largely not an issue.&#8221;</p>
<p>So, we&#8217;re talking about standardizations, on the one hand. But, on the other hand, we&#8217;re talking about a conglomeration of corporate entities that are competitive rivals, haplessly mulling around together under the thin umbrella of the W3C, and in the mix of all of this, is the topic of discussion: Namely, technology, patents, and future development, which of course, results ultimately, in future profits, or perhaps the lack thereof.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-75</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 27 Dec 2004 07:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-75</guid>
		<description>In response to the last poster, I would say that Microsoft is a member of W3C, at least for now.  Here&#039;s a news post from back in 2003 that may shed some light on the subject : http://www.theinquirer.net/?article=8495</description>
		<content:encoded><![CDATA[<p>In response to the last poster, I would say that Microsoft is a member of W3C, at least for now.  Here&#8217;s a news post from back in 2003 that may shed some light on the subject : <a href="http://www.theinquirer.net/?article=8495" rel="nofollow">http://www.theinquirer.net/?article=8495</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .redSPLASH - Blog</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-74</link>
		<dc:creator>.redSPLASH - Blog</dc:creator>
		<pubDate>Wed, 17 Nov 2004 09:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-74</guid>
		<description>&lt;strong&gt;Does Microsoft Care About Web Standards?&lt;/strong&gt;
The question must seem absurd. After all, Microsoft is a member of the W3C and an active participant in the development of web standards. Each new Microsoft product announcement seems to include more standards compliant buzzwords than the last. True, Micr</description>
		<content:encoded><![CDATA[<p><strong>Does Microsoft Care About Web Standards?</strong><br />
The question must seem absurd. After all, Microsoft is a member of the W3C and an active participant in the development of web standards. Each new Microsoft product announcement seems to include more standards compliant buzzwords than the last. True, Micr</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karmakars.com</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-73</link>
		<dc:creator>Karmakars.com</dc:creator>
		<pubDate>Sat, 11 Sep 2004 08:11:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-73</guid>
		<description>&lt;strong&gt;IE(Internet Explorer) sucks&lt;/strong&gt;
IE sucks! The reasons are more than just obvious. If you are a web developer and conscientious about writing clean semantic code and if you care to know about why IE should really be avoided read on:</description>
		<content:encoded><![CDATA[<p><strong>IE(Internet Explorer) sucks</strong><br />
IE sucks! The reasons are more than just obvious. If you are a web developer and conscientious about writing clean semantic code and if you care to know about why IE should really be avoided read on:</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Beach</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-72</link>
		<dc:creator>Chris Beach</dc:creator>
		<pubDate>Mon, 02 Aug 2004 12:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-72</guid>
		<description>It&#039;s true, IE has made major improvements over vanilla CSS1/2. In particular it has developed an HTC model that ties javascript &quot;behaviours&quot; to HTML elements via a CSS property. Imagine being able to change not just the look of your whole site, but also the behaviour, via one .css file. You can with IE.

I prefer the way IE has implemented it&#039;s proprietary syntax. It does not pollute the w3c namespaces. Furthermore, I would say that Mozilla&#039;s &quot;MozOpacity&quot; property (for example) is the wrong way to go about extending the w3c spec. I don&#039;t think browsers should have their own namespaces - it&#039;s not in the spirit of the web.</description>
		<content:encoded><![CDATA[<p>It&#8217;s true, IE has made major improvements over vanilla CSS1/2. In particular it has developed an HTC model that ties javascript &#8220;behaviours&#8221; to HTML elements via a CSS property. Imagine being able to change not just the look of your whole site, but also the behaviour, via one .css file. You can with IE.</p>
<p>I prefer the way IE has implemented it&#8217;s proprietary syntax. It does not pollute the w3c namespaces. Furthermore, I would say that Mozilla&#8217;s &#8220;MozOpacity&#8221; property (for example) is the wrong way to go about extending the w3c spec. I don&#8217;t think browsers should have their own namespaces &#8211; it&#8217;s not in the spirit of the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: francey</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-71</link>
		<dc:creator>francey</dc:creator>
		<pubDate>Sat, 31 Jul 2004 19:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-71</guid>
		<description>In terms of propriety CSS, IE has invented so much more, for example, all of the alpha filters, as well as the scrollbar colour properties.</description>
		<content:encoded><![CDATA[<p>In terms of propriety CSS, IE has invented so much more, for example, all of the alpha filters, as well as the scrollbar colour properties.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Beach</title>
		<link>http://alttags.org/web-standards/does-microsoft-care-about-web-standards/#comment-70</link>
		<dc:creator>Chris Beach</dc:creator>
		<pubDate>Wed, 28 Jul 2004 13:53:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.alttags.org/archives/2004/04/29/33/#comment-70</guid>
		<description>Also I don&#039;t approve of the proprietary CSS that Mozilla has invented, like the &quot;MozOpacity&quot; property - More on that at http://www.chrisbeach.co.uk/core/scripts/entryViewer.php?ID=4753</description>
		<content:encoded><![CDATA[<p>Also I don&#8217;t approve of the proprietary CSS that Mozilla has invented, like the &#8220;MozOpacity&#8221; property &#8211; More on that at <a href="http://www.chrisbeach.co.uk/core/scripts/entryViewer.php?ID=4753" rel="nofollow">http://www.chrisbeach.co.uk/core/scripts/entryViewer.php?ID=4753</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

