--- a/contacts/.htaccess Thu Nov 10 16:46:10 2011 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,1 +0,0 @@
-Header add Access-Control-Allow-Origin "*"
\ No newline at end of file
--- a/contacts/Overview.html Thu Nov 10 16:46:10 2011 +0100
+++ b/contacts/Overview.html Thu Nov 10 16:49:05 2011 +0100
@@ -3,8 +3,8 @@
<head>
<title>Contacts API</title>
<meta http-equiv='Content-Type' content='text/html; charset=utf-8'/>
- <script type="text/javascript" src='../ReSpec.js/js/respec.js' class='remove'></script>
- <script type="text/javascript" src='../ReSpec.js/js/sh_main.min.js' class='remove'></script>
+ <script type="text/javascript" src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+ <script type="text/javascript" src='http://dev.w3.org/2009/dap/ReSpec.js/js/sh_main.min.js' class='remove'></script>
<script type="text/javascript" class='remove'>
var respecConfig = {
specStatus: "ED",
@@ -17,11 +17,11 @@
previousPublishDate: "2011-06-16",
lcEnd: "2011-07-14",
previousMaturity: "LC",
- edDraftURI: "http://dev.w3.org/2009/dap/contacts/",
+ edDraftURI: "http://w3c-test.org/2009/dap/contacts/",
noIDLIn: true,
};
</script>
- <script type="text/javascript" src='../common/config.js' class='remove'></script>
+ <script type="text/javascript" src='http://dev.w3.org/2009/dap/common/config.js' class='remove'></script>
<style type="text/css">
/* ReSpec.js CSS optimizations (Richard Tibbett) */
div.example {
--- a/contacts/tests/Overview.html Thu Nov 10 16:46:10 2011 +0100
+++ b/contacts/tests/Overview.html Thu Nov 10 16:49:05 2011 +0100
@@ -253,7 +253,7 @@
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
-<script>var SPEC_URL = "http://dev.w3.org/2009/dap/contacts/";</script>
+<script>var SPEC_URL = "http://w3c-test.org/dap/contacts/";</script>
<script src="http://dev.w3.org/2006/waf/widgets-shared/javascript/ShowTestSuite.js"></script>
</body>
--- a/proposals/intents-tf.txt Thu Nov 10 16:46:10 2011 +0100
+++ b/proposals/intents-tf.txt Thu Nov 10 16:49:05 2011 +0100
@@ -1,7 +1,22 @@
-The Web Intents Task Force works on a joint deliverable of the WebApps and Device APIs WGs that aims to produce a way for web applications to register themselves as handlers for services, and for other web applications to interact with these through simple requests brokered by the user agent (a system commonly known as Intents, or Activities).
+The Web Intents Task Force works on a joint deliverable of the WebApps
+and Device APIs WGs that aims to produce a way for web applications to
+register themselves as handlers for services, and for other web
+applications to interact with these through simple requests brokered by
+the user agent (a system commonly known as Intents, or Activities).
-The mailing list on which the TF's discussions take place is public-intents@w3.org. The chair is Robin Berjon.
+The mailing list on which the TF's discussions take place is
+public-intents@w3.org. The chair is Robin Berjon.
-Operational modalities such as whether or not to have phone and/or face to face meetings, as well as where to store the draft document are left to the TF to decide for itself. Decisions are made by consensus inside of the task force and do not require separate ratification by the wider groups.
+Operational modalities such as whether or not to have phone and/or face
+to face meetings, as well as where to store the draft document are left
+to the TF to decide for itself. Decisions are made by consensus inside
+of the task force and do not require separate ratification by the wider
+groups.
-It is important to note that until such a time as the WebApps WG is rechartered with Intents in its list of deliverables, it will be necessary for participants in WebApps who are not in Device APIs and wish to make substantive contributions (just joining the discussion and providing comments is always fine) to make an RF commitment for this deliverable (not necessarily for other DAP deliverables, naturally). For more details on this, please contact the W3C Team.
+It is important to note that until such a time as the WebApps WG is
+rechartered with Intents in its list of deliverables, it will be
+necessary for participants in WebApps who are not in Device APIs and
+wish to make substantive contributions (just joining the discussion and
+providing comments is always fine) to make an RF commitment for this
+deliverable (not necessarily for other DAP deliverables, naturally).
+For more details on this, please contact the W3C Team.