<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/link/2515479">
<title>Public marks on http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx</title>
<description>Public marks on http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx</description>
<link>http://blogmarks.net/marks/link/2515479</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1057645344"/>
<rdf:li resource="http://blogmarks.net/api/user/ms_michel/mark/1057527322"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1057645344">
<title>JScript Blog : ECMAScript 3 and beyond</title>
<link>http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx</link>
<description>&lt;blockquote&gt;&lt;p&gt;The point is that JavaScript developers shouldn’t have to detect and workaround such issues. JavaScript should work the same across all implementations. We believe this is the first step in making JavaScript better.

 

To make it possible to achieve such implementation conformance, the first step is knowing where the divergences are. We in the JScript team are looking into where various browser based implementations diverge, where our engine is incorrect in its interpretation of the specification, what if any de facto compatibility conventions have been reached, and the value of codifying such conventions into the standard. We’ve published the first draft of JScript Deviations from ES3 as a starting point.&lt;/p&gt;&lt;/blockquote&gt;

Cool</description>
<dc:date>2008-01-08T05:03:26Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>QA, interoperability, implementation, javascript</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx"><img border="0" src="http://blogmarks.net/screenshots/2008/01/08/2dcb91cfadf16fdd8ed1a048bf3296e8.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx">JScript Blog : ECMAScript 3 and beyond</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2515479">1 other(s)</a> 
<div class="description"><blockquote><p>The point is that JavaScript developers shouldn’t have to detect and workaround such issues. JavaScript should work the same across all implementations. We believe this is the first step in making JavaScript better.

 

To make it possible to achieve such implementation conformance, the first step is knowing where the divergences are. We in the JScript team are looking into where various browser based implementations diverge, where our engine is incorrect in its interpretation of the specification, what if any de facto compatibility conventions have been reached, and the value of codifying such conventions into the standard. We’ve published the first draft of JScript Deviations from ES3 as a starting point.</p></blockquote>

Cool</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/QA">QA</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/interoperability">interoperability</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/implementation">implementation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057645344">Copy</a> | 
<a href="http://blogmarks.net/link/2515479">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ms_michel/mark/1057527322">
<title>JScript Deviations from ES3 </title>
<link>http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx</link>
<description>&lt;cite&gt;We in the JScript team are looking into where various browser based implementations diverge, where our engine is incorrect in its interpretation of the specification, what if any de facto compatibility conventions have been reached, and the value of codifying such conventions into the standard.&lt;/cite&gt;</description>
<dc:date>2007-11-07T14:49:36Z</dc:date>
<dc:author>ms_michel</dc:author>
<dc:subject>javascript</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx"><img border="0" src="http://blogmarks.net/screenshots/2008/01/08/2dcb91cfadf16fdd8ed1a048bf3296e8.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx">JScript Deviations from ES3 </a></h4>
 
by <a href="http://blogmarks.net/user/ms_michel">ms_michel</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2515479">1 other(s)</a> 
<div class="description"><cite>We in the JScript team are looking into where various browser based implementations diverge, where our engine is incorrect in its interpretation of the specification, what if any de facto compatibility conventions have been reached, and the value of codifying such conventions into the standard.</cite></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057527322">Copy</a> | 
<a href="http://blogmarks.net/link/2515479">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>