<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Client and Server JavaScript APIs Community Group</title>
	<atom:link href="http://www.w3.org/community/jseverywhere/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.w3.org/community/jseverywhere</link>
	<description></description>
	<lastBuildDate>Thu, 01 Nov 2012 23:57:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Starting activity in Client and Server JavaScript APIs Community Group</title>
		<link>http://www.w3.org/community/jseverywhere/2012/11/01/welcome/</link>
		<comments>http://www.w3.org/community/jseverywhere/2012/11/01/welcome/#comments</comments>
		<pubDate>Thu, 01 Nov 2012 11:23:25 +0000</pubDate>
		<dc:creator>Alexandre Morgaut</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/jseverywhere/?p=8</guid>
		<description><![CDATA[This community group wants to provide: a transversal work encouraging W3C API Working Groups to make their specifications: more easily applicable in workers and server-side contexts providing both Synchronous and Asynchronous APIs* a proposal to have a standard web worker &#8230; <a href="http://www.w3.org/community/jseverywhere/2012/11/01/welcome/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This community group wants to provide:</p>
<ul>
<li>a transversal work encouraging W3C API Working Groups to make their specifications:</li>
<ul>
<li>more easily applicable in workers and server-side contexts</li>
<li>providing both Synchronous and Asynchronous APIs*</li>
</ul>
<li>a proposal to have a standard web worker like interface in Server-Side JavaScript contexts and maybe define the concept of remote workers</li>
<li>evangelisation for having any JS implementation providing as most as possible W3C API (or at least standard ones) instead of proprietary APIs.</li>
</ul>
<p>You can  start to learn more about this group via those few resources:</p>
<ul>
<li>the community group <a href="http://www.w3.org/community/jseverywhere/wiki/Main_Page" rel="external nofollow">wiki main page</a></li>
<li>the <a href="http://www.slideshare.net/alexandre_morgaut/endtoend-w3c-apis-tpac-2012" rel="external nofollow">slides</a> and <a href="http://www.w3.org/2012/10/31-jseverywhere-minutes.html" rel="external nofollow">minutes</a> of the &#8220;<a href="http://www.w3.org/wiki/TPAC2012/SessionIdeas#End-to-end_W3C_APIs" rel="external nofollow">End-to-end W3C APIs</a>&#8221; TPAC 2012 breakout session</li>
</ul>
<p>More resources will come progressively. We are looking for representative members of most the W3C API (at least) specifications, as well as representative members of server-side (or even desktop) implementations of JavaScript.</p>
<p><em>* most server-side JavaScript implementations work synchronously, and synchronous code is non-blocking in Web Workers. Synchronous JavaScript code can then work either on the client and the server.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/jseverywhere/2012/11/01/welcome/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
