Cleanup: Fix some whitespace, version control URL, and remove old acronym mapping of crypto -> cryptography
--- a/spec/Overview-WebCryptoAPI.xml Mon Dec 03 17:16:54 2012 -0800
+++ b/spec/Overview-WebCryptoAPI.xml Mon Dec 03 17:17:03 2012 -0800
@@ -16,8 +16,6 @@
<meta http-equiv='Content-Type' content='text/html; charset=UTF-8'/>
<title>Web Cryptography API</title>
- <meta name='revision' content='$Id: Overview-WebCryptoAPI.xml,v 1.53 2012-11-12 13:16:44 hhalpin Exp $'/>
-
<link rel='stylesheet' href='webcrypto.css' type='text/css'/>
<script src='section-links.js' type='application/ecmascript'/>
<script src='dfn.js' type='application/ecmascript'/>
@@ -73,14 +71,17 @@
<div class='section'>
<h2>Status of this Document</h2>
-<p>
-The Web Cryptography Working Group invites discussion and feedback on this draft document by web developers, companies, standardization bodies or forums interested in deployment of secure services with web applications. Specifically, Web Cryptography Working Group is looking for feedback on:
-</p>
-<ul>
- <li>developer convenience for managing keys and algorithms;</li>
- <li>comments on open issues the WG is currently dealing with, highlighted in this working draft;</li>
- <li>potential missing functionalities to deploy secure web applications.</li>
-</ul>
+ <p>
+ The Web Cryptography Working Group invites discussion and feedback on this draft document by
+ web developers, companies, standardization bodies or forums interested in deployment of secure
+ services with web applications. Specifically, Web Cryptography Working Group is looking for
+ feedback on:
+ </p>
+ <ul>
+ <li>developer convenience for managing keys and algorithms;</li>
+ <li>comments on open issues the WG is currently dealing with, highlighted in this working draft;</li>
+ <li>potential missing functionalities to deploy secure web applications.</li>
+ </ul>
<p>
This is the W3C Editor's Draft of the Web Cryptography API. Please send comments to
public-webcrypto-comments@w3.org (archived). This is an unfinished <strong>work in progress</strong>.
@@ -106,21 +107,21 @@
</p>
<p>
- This document is produced by the <a href="http://www.w3.org/2012/webcrypto">Web <acronym title="Cryptography">Cryptography</acronym>
+ This document is produced by the <a href="http://www.w3.org/2012/webcrypto">Web Cryptography
<acronym title="Working Group">WG</acronym></a> of the <acronym title="World Wide Web Consortium">W3C</acronym>.
</p>
<p>
Web content and browser developers are encouraged to review this draft. Please send comments to
<a href="mailto:public-webcrypto-comments@w3.org">public-webcrypto-comments@w3.org</a>,
the <acronym title="World Wide Web Consortium">W3C</acronym>'s public email list for issues related
- to Web <acronym title="Cryptography">Cryptography</acronym>.
+ to Web Cryptography.
<a href="http://lists.w3.org/Archives/Public/public-webcrypto-comments/">Archives</a> of the public list and
<a href="http://lists.w3.org/Archives/Public/public-webcrypto/">archives</a> of the member's-only list
are available.
</p>
<p>
Changes made to this document can be found in the
- <a href='http://dev.w3.org/cvsweb/2012/webcrypto/Overview-FA.xml'>W3C public CVS server</a>.
+ <a href='https://dvcs.w3.org/hg/webcrypto-api/file/tip/spec/'>W3C public Mercurial server</a>.
</p>
<?sotd-bottom http://www.w3.org/2004/01/pp-impl/42538/status?>
</div>
--- a/spec/Overview.html Mon Dec 03 17:16:54 2012 -0800
+++ b/spec/Overview.html Mon Dec 03 17:17:03 2012 -0800
@@ -12,8 +12,6 @@
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Web Cryptography API</title>
- <meta name="revision" content="$Id: Overview-WebCryptoAPI.xml,v 1.53 2012-11-12 13:16:44 hhalpin Exp $" />
-
<link rel="stylesheet" href="webcrypto.css" type="text/css" />
<script src="section-links.js" type="application/ecmascript"></script>
<script src="dfn.js" type="application/ecmascript"></script>
@@ -30,7 +28,7 @@
<link rel="stylesheet" href="//www.w3.org/StyleSheets/TR/W3C-ED" type="text/css" /></head>
<body>
- <div class="head"><div><a href="http://www.w3.org/"><img src="//www.w3.org/Icons/w3c_home" width="72" height="48" alt="W3C" /></a></div><h1>Web Cryptography API</h1><h2>W3C Editor’s Draft <em>2 December 2012</em></h2><dl><dt>Latest Editor’s Draft:</dt><dd><a href="http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html">http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html</a></dd><dt>Latest Published Version:</dt><dd><a href="http://www.w3.org/TR/WebCryptoAPI/">http://www.w3.org/TR/WebCryptoAPI/</a></dd><dt>Previous Version(s):</dt><dd><a href="http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html">http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html</a></dd><dt>Editors:</dt><dd><a href="http://ddahl.com/">David Dahl</a>, Mozilla Corporation <ddahl@mozilla.com></dd><dd><a href="http://www.google.com/">Ryan Sleevi</a>, Google, Inc. <sleevi@google.com></dd><dt>Participate:</dt><dd><p>Send feedback to <a href="mailto:public-webcrypto@w3.org?subject=%5BWebCryptoAPI%5D">public-webcrypto@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-webcrypto/">archives</a>), or <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=Web%20Cryptography&component=Web%20Cryptography%20API%20Document">file a bug</a>
+ <div class="head"><div><a href="http://www.w3.org/"><img src="//www.w3.org/Icons/w3c_home" width="72" height="48" alt="W3C" /></a></div><h1>Web Cryptography API</h1><h2>W3C Editor’s Draft <em>3 December 2012</em></h2><dl><dt>Latest Editor’s Draft:</dt><dd><a href="http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html">http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html</a></dd><dt>Latest Published Version:</dt><dd><a href="http://www.w3.org/TR/WebCryptoAPI/">http://www.w3.org/TR/WebCryptoAPI/</a></dd><dt>Previous Version(s):</dt><dd><a href="http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html">http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html</a></dd><dt>Editors:</dt><dd><a href="http://ddahl.com/">David Dahl</a>, Mozilla Corporation <ddahl@mozilla.com></dd><dd><a href="http://www.google.com/">Ryan Sleevi</a>, Google, Inc. <sleevi@google.com></dd><dt>Participate:</dt><dd><p>Send feedback to <a href="mailto:public-webcrypto@w3.org?subject=%5BWebCryptoAPI%5D">public-webcrypto@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-webcrypto/">archives</a>), or <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=Web%20Cryptography&component=Web%20Cryptography%20API%20Document">file a bug</a>
(see <a href="https://www.w3.org/Bugs/Public/buglist.cgi?product=Web%20Cryptography&component=Web%20Cryptography%20API%20Document&resolution=---">existing bugs</a>).</p></dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © view <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.org/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr />
<div class="section">
@@ -51,14 +49,17 @@
<div class="section">
<h2>Status of this Document</h2>
-<p>
-The Web Cryptography Working Group invites discussion and feedback on this draft document by web developers, companies, standardization bodies or forums interested in deployment of secure services with web applications. Specifically, Web Cryptography Working Group is looking for feedback on:
-</p>
-<ul>
- <li>developer convenience for managing keys and algorithms;</li>
- <li>comments on open issues the WG is currently dealing with, highlighted in this working draft;</li>
- <li>potential missing functionalities to deploy secure web applications.</li>
-</ul>
+ <p>
+ The Web Cryptography Working Group invites discussion and feedback on this draft document by
+ web developers, companies, standardization bodies or forums interested in deployment of secure
+ services with web applications. Specifically, Web Cryptography Working Group is looking for
+ feedback on:
+ </p>
+ <ul>
+ <li>developer convenience for managing keys and algorithms;</li>
+ <li>comments on open issues the WG is currently dealing with, highlighted in this working draft;</li>
+ <li>potential missing functionalities to deploy secure web applications.</li>
+ </ul>
<p>
This is the W3C Editor's Draft of the Web Cryptography API. Please send comments to
public-webcrypto-comments@w3.org (archived). This is an unfinished <strong>work in progress</strong>.
@@ -84,21 +85,21 @@
</p>
<p>
- This document is produced by the <a href="http://www.w3.org/2012/webcrypto">Web <acronym title="Cryptography">Cryptography</acronym>
+ This document is produced by the <a href="http://www.w3.org/2012/webcrypto">Web Cryptography
<acronym title="Working Group">WG</acronym></a> of the <acronym title="World Wide Web Consortium">W3C</acronym>.
</p>
<p>
Web content and browser developers are encouraged to review this draft. Please send comments to
<a href="mailto:public-webcrypto-comments@w3.org">public-webcrypto-comments@w3.org</a>,
the <acronym title="World Wide Web Consortium">W3C</acronym>'s public email list for issues related
- to Web <acronym title="Cryptography">Cryptography</acronym>.
+ to Web Cryptography.
<a href="http://lists.w3.org/Archives/Public/public-webcrypto-comments/">Archives</a> of the public list and
<a href="http://lists.w3.org/Archives/Public/public-webcrypto/">archives</a> of the member's-only list
are available.
</p>
<p>
Changes made to this document can be found in the
- <a href="http://dev.w3.org/cvsweb/2012/webcrypto/Overview-FA.xml">W3C public CVS server</a>.
+ <a href="https://dvcs.w3.org/hg/webcrypto-api/file/tip/spec/">W3C public Mercurial server</a>.
</p>
<p>
Publication as an Editor’s Draft does not imply endorsement by the