update W3C Notes as per http://lists.w3.org/Archives/Public/public-device-apis/2013Dec/0038.html
--- a/contacts/NOTE.src.html Mon Dec 30 14:13:05 2013 +0200
+++ b/contacts/NOTE.src.html Tue Dec 31 14:37:11 2013 +0200
@@ -56,9 +56,24 @@
</strong>
</p>
<p>
- This is a historical document. The domain covered by this document
- is still within the scope of the Working Group as defined in its
- Charter.
+ The Pick Contacts Intent defines how
+ <a href="http://www.w3.org/TR/web-intents/">Web Intents</a> may be used
+ enable access to a user's address book. Work on this specification has
+ been discontinued since the
+ <a href="http://www.w3.org/TR/web-intents/">Web Intents</a>
+ specification has been published as a W3C Working Group Note indicating
+ no further development on the Recommendation track at this time.
+ Implementation support has also been removed from existing systems
+ (e.g. <a href="https://lists.webkit.org/pipermail/webkit-dev/2013-January/023537.html">WebKit</a>)
+ precluding interoperability testing. Issues related to Web Intents were
+ outlined in a
+ <a href="http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0023.html">mail
+ message on the DAP mailing list </a>.
+ </p>
+ <p>
+ The Charter of the <a href="http://www.w3.org/2009/dap/">Device APIs Working Group</a>
+ continues to include this work as "in scope", so the working group
+ could decide to resume work if warranted by new information.
</p>
</section>
</body>
--- a/gallery/NOTE.src.html Mon Dec 30 14:13:05 2013 +0200
+++ b/gallery/NOTE.src.html Tue Dec 31 14:37:11 2013 +0200
@@ -50,9 +50,24 @@
</strong>
</p>
<p>
- This is a historical document. The domain covered by this document
- is still within the scope of the Working Group as defined in its
- Charter.
+ The Pick Media Intent defines how
+ <a href="http://www.w3.org/TR/web-intents/">Web Intents</a> may be used
+ to enable access to a user's gallery. Work on this specification has
+ been discontinued since the
+ <a href="http://www.w3.org/TR/web-intents/">Web Intents</a>
+ specification has been published as a W3C Working Group Note indicating
+ no further development on the Recommendation track at this time.
+ Implementation support has also been removed from existing systems
+ (e.g. <a href="https://lists.webkit.org/pipermail/webkit-dev/2013-January/023537.html">WebKit</a>)
+ precluding interoperability testing. Issues related to Web Intents were
+ outlined in a
+ <a href="http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0023.html">mail
+ message on the DAP mailing list</a>.
+ </p>
+ <p>
+ The Charter of the <a href="http://www.w3.org/2009/dap/">Device APIs Working Group</a>
+ continues to include this work as "in scope", so the working group
+ could decide to resume work if warranted by new information.
</p>
</section>
</body>
--- a/wi-addendum-local-services/NOTE.src.html Mon Dec 30 14:13:05 2013 +0200
+++ b/wi-addendum-local-services/NOTE.src.html Tue Dec 31 14:37:11 2013 +0200
@@ -46,9 +46,24 @@
</strong>
</p>
<p>
- This is a historical document. The domain covered by this document
- is still within the scope of the Working Group as defined in its
- Charter.
+ The Web Intents Addendum defines how
+ <a href="http://www.w3.org/TR/web-intents/">Web Intent</a> may be used
+ to discover services on a local network. Work on this specification
+ has been discontinued since the
+ <a href="http://www.w3.org/TR/web-intents/">Web Intent</a>
+ specification has been published as a W3C Working Group Note indicating
+ no further development on the Recommendation track at this time.
+ Implementation support has also been removed from existing systems
+ (e.g. <a href="https://lists.webkit.org/pipermail/webkit-dev/2013-January/023537.html">WebKit</a>)
+ precluding interoperability testing. Issues related to Web Intents were
+ outlined in a
+ <a href="http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0023.html">mail
+ message on the DAP mailing list </a>.
+ </p>
+ <p>
+ The Charter of the <a href="http://www.w3.org/2009/dap/">Device APIs Working Group</a>
+ continues to include this work as "in scope", so the working group
+ could decide to resume work if warranted by new information.
</p>
</section>
</body>