W3C home > Mailing lists > Public > public-dap-commits@w3.org > January 2010

2009/dap/contacts FPWD.html,1.3,1.4

From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 20 Jan 2010 10:34:53 +0000
To: public-dap-commits@w3.org
Message-Id: <E1NXXtl-0003WM-5D@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv13378

Modified Files:
	FPWD.html 
Log Message:
updated sotd with non-boilerplate text


Index: FPWD.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/FPWD.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- FPWD.html	19 Jan 2010 17:23:12 -0000	1.3
+++ FPWD.html	20 Jan 2010 10:34:50 -0000	1.4
@@ -442,7 +442,15 @@
 </style><link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"></head><body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p><h1>The Contacts API</h1><h2><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 21 January 2010</h2><dl><dt>This Version:</dt><dd><a href="http://www.w3.org/TR/2010/WD-contacts-api-20100121/">http://www.w3.org/TR/2010/WD-contacts-api-20100121/</a></dd><dt>Latest Published Version:</dt><dd><a href="http://www.w3.org/TR/contacts-api/">http://www.w3.org/TR/contacts-api/</a></dd><dt>Latest Editor's Draft:</dt><dd><a href="http://dev.w3.org/2009/dap/contacts/">http://dev.w3.org/2009/dap/contacts/</a></dd><dt>Editor:</dt><dd>Richard Tibbett, France Telecom</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium"><acronym title="World Wide Web Consortium">W3C</acronym></acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology"><acronym title="Massachusetts Institute of Technology">MIT</acronym></acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <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><hr></div>
         <div class="introductory section" id="abstract"><h2>Abstract</h2>
             <p>This specification defines an API that provides access to a user's unified address book.</p>		
-        </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p><p>This document was published by the <a href="http://www.w3.org/2009/dap/">Device APIs and Policy Working Group</a> as a First Public Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-device-apis@w3.org">public-device-apis@w3.org</a> (<a href="mailto:public-device-apis-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-device-apis/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/43696/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li><a href="#conformance"><span class="secno">1. </span>Conformance</a></li><li><a href="#introduction"><span class="secno">2. </span>Introduction</a></li><li><ul class="toc"><li><a href="#usage-examples"><span class="secno">2.1 </span>Usage Examples</a></li></ul></li><li><a href="#security-and-privacy-considerations"><span class="secno">3. </span>Security and Privacy Considerations</a></li><li><ul class="toc"><li><a href="#privacy-considerations-for-implementors-of-the-contacts-api"><span class="secno">3.1 </span>Privacy considerations for implementors of the Contacts API</a></li><li><a href="#privacy-considerations-for-recipients-of-contact-information"><span class="secno">3.2 </span>Privacy considerations for recipients of contact information</a></li><li><a href="#additional-implementation-considerations"><span class="secno">3.3 </span>Additional implementation considerations</a></li></ul></li><li><a href="#api-description"><span class="secno">4. </span>API Description</a></li><li><ul class="toc"><li><a href="#servicecontacts-interface"><span class="secno">4.1 </span><span class="idlType formerLink idlType"><code>ServiceContacts</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes"><span class="secno">4.1.1 </span>Attributes</a></li></ul></li><li><a href="#contacts-interface"><span class="secno">4.2 </span><span class="idlType formerLink idlType"><code>Contacts</code></span> interface</a></li><li><ul class="toc"><li><a href="#methods"><span class="secno">4.2.1 </span>Methods</a></li></ul></li><li><a href="#contact-interface"><span class="secno">4.3 </span><span class="idlType formerLink idlType"><code>Contact</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-1"><span class="secno">4.3.1 </span>Attributes</a></li><li><a href="#methods-1"><span class="secno">4.3.2 </span>Methods</a></li></ul></li><li><a href="#contactproperties-interface"><span class="secno">4.4 </span><span class="idlType formerLink idlType"><code>ContactProperties</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-2"><span class="secno">4.4.1 </span>Attributes</a></li></ul></li><li><a href="#contactfield-interface"><span class="secno">4.5 </span><span class="idlType formerLink idlType"><code>ContactField</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-3"><span class="secno">4.5.1 </span>Attributes</a></li></ul></li><li><a href="#contactaddress-interface"><span class="secno">4.6 </span><span class="idlType formerLink idlType"><code>ContactAddress</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-4"><span class="secno">4.6.1 </span>Attributes</a></li></ul></li><li><a href="#contactoptions-interface"><span class="secno">4.7 </span><span class="idlType formerLink idlType"><code>ContactOptions</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-5"><span class="secno">4.7.1 </span>Attributes</a></li></ul></li><li><a href="#contactfindsuccesscb-interface"><span class="secno">4.8 </span><span class="idlType formerLink idlType"><code>ContactFindSuccessCB</code></span> interface</a></li><li><ul class="toc"><li><a href="#methods-2"><span class="secno">4.8.1 </span>Methods</a></li></ul></li><li><a href="#contactsuccesscb-interface"><span class="secno">4.9 </span><span class="idlType formerLink idlType"><code>ContactSuccessCB</code></span> interface</a></li><li><ul class="toc"><li><a href="#methods-3"><span class="secno">4.9.1 </span>Methods</a></li></ul></li><li><a href="#contacterrorcb-interface"><span class="secno">4.10 </span><span class="idlType formerLink idlType"><code>ContactErrorCB</code></span> interface</a></li><li><ul class="toc"><li><a href="#methods-4"><span class="secno">4.10.1 </span>Methods</a></li></ul></li><li><a href="#contacterror-interface"><span class="secno">4.11 </span><span class="idlType formerLink idlType"><code>ContactError</code></span> interface</a></li><li><ul class="toc"><li><a href="#constants"><span class="secno">4.11.1 </span>Constants</a></li></ul></li></ul></li><li><a href="#general-api-support"><span class="secno">5. </span>General API Support</a></li><li><ul class="toc"><li><a href="#genericerror-interface"><span class="secno">5.1 </span><span class="idlType formerLink idlType"><code>GenericError</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-6"><span class="secno">5.1.1 </span>Attributes</a></li><li><a href="#constants-1"><span class="secno">5.1.2 </span>Constants</a></li></ul></li></ul></li><li><a href="#contact-search-processing-rules"><span class="secno">6. </span><span class="formerLink">Contact Search Processing Rules</span></a></li><li><a href="#use-cases-and-requirements"><span class="secno">7. </span>Use Cases and Requirements</a></li><li><ul class="toc"><li><a href="#use-cases"><span class="secno">7.1 </span>Use Cases</a></li><li><a href="#requirements"><span class="secno">7.2 </span>Requirements</a></li></ul></li><li><a href="#features-for-future-consideration"><span class="secno">A. </span>Features for Future Consideration</a></li><li><a href="#acknowledgements"><span class="secno">B. </span>Acknowledgements</a></li><li><a href="#references"><span class="secno">C. </span>References</a></li><li><ul class="toc"><li><a href="#normative-references"><span class="secno">C.1 </span>Normative references</a></li><li><a href="#informative-references"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
+        </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
+<p>        This document was published by the  <a href="http://www.w3.org/2009/dap/">Device APIs and Policy
+        Working Group</a> as a First Public Working Draft, and represents
+        the early consensus of the group on the scope and features of
+        the proposed Contacts API. Issues and editors note in the
+        document highlight some of the points on which the group is
+        still working and would particularly like to get feedback. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation.</p>
+
+<p>If you wish to make comments regarding this document, please send them to <a href="mailto:public-device-apis@w3.org">public-device-apis@w3.org</a> (<a href="mailto:public-device-apis-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-device-apis/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/43696/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li><a href="#conformance"><span class="secno">1. </span>Conformance</a></li><li><a href="#introduction"><span class="secno">2. </span>Introduction</a></li><li><ul class="toc"><li><a href="#usage-examples"><span class="secno">2.1 </span>Usage Examples</a></li></ul></li><li><a href="#security-and-privacy-considerations"><span class="secno">3. </span>Security and Privacy Considerations</a></li><li><ul class="toc"><li><a href="#privacy-considerations-for-implementors-of-the-contacts-api"><span class="secno">3.1 </span>Privacy considerations for implementors of the Contacts API</a></li><li><a href="#privacy-considerations-for-recipients-of-contact-information"><span class="secno">3.2 </span>Privacy considerations for recipients of contact information</a></li><li><a href="#additional-implementation-considerations"><span class="secno">3.3 </span>Additional implementation considerations</a></li></ul></li><li><a href="#api-description"><span class="secno">4. </span>API Description</a></li><li><ul class="toc"><li><a href="#servicecontacts-interface"><span class="secno">4.1 </span><span class="idlType formerLink idlType"><code>ServiceContacts</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes"><span class="secno">4.1.1 </span>Attributes</a></li></ul></li><li><a href="#contacts-interface"><span class="secno">4.2 </span><span class="idlType formerLink idlType"><code>Contacts</code></span> interface</a></li><li><ul class="toc"><li><a href="#methods"><span class="secno">4.2.1 </span>Methods</a></li></ul></li><li><a href="#contact-interface"><span class="secno">4.3 </span><span class="idlType formerLink idlType"><code>Contact</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-1"><span class="secno">4.3.1 </span>Attributes</a></li><li><a href="#methods-1"><span class="secno">4.3.2 </span>Methods</a></li></ul></li><li><a href="#contactproperties-interface"><span class="secno">4.4 </span><span class="idlType formerLink idlType"><code>ContactProperties</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-2"><span class="secno">4.4.1 </span>Attributes</a></li></ul></li><li><a href="#contactfield-interface"><span class="secno">4.5 </span><span class="idlType formerLink idlType"><code>ContactField</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-3"><span class="secno">4.5.1 </span>Attributes</a></li></ul></li><li><a href="#contactaddress-interface"><span class="secno">4.6 </span><span class="idlType formerLink idlType"><code>ContactAddress</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-4"><span class="secno">4.6.1 </span>Attributes</a></li></ul></li><li><a href="#contactoptions-interface"><span class="secno">4.7 </span><span class="idlType formerLink idlType"><code>ContactOptions</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-5"><span class="secno">4.7.1 </span>Attributes</a></li></ul></li><li><a href="#contactfindsuccesscb-interface"><span class="secno">4.8 </span><span class="idlType formerLink idlType"><code>ContactFindSuccessCB</code></span> interface</a></li><li><ul class="toc"><li><a href="#methods-2"><span class="secno">4.8.1 </span>Methods</a></li></ul></li><li><a href="#contactsuccesscb-interface"><span class="secno">4.9 </span><span class="idlType formerLink idlType"><code>ContactSuccessCB</code></span> interface</a></li><li><ul class="toc"><li><a href="#methods-3"><span class="secno">4.9.1 </span>Methods</a></li></ul></li><li><a href="#contacterrorcb-interface"><span class="secno">4.10 </span><span class="idlType formerLink idlType"><code>ContactErrorCB</code></span> interface</a></li><li><ul class="toc"><li><a href="#methods-4"><span class="secno">4.10.1 </span>Methods</a></li></ul></li><li><a href="#contacterror-interface"><span class="secno">4.11 </span><span class="idlType formerLink idlType"><code>ContactError</code></span> interface</a></li><li><ul class="toc"><li><a href="#constants"><span class="secno">4.11.1 </span>Constants</a></li></ul></li></ul></li><li><a href="#general-api-support"><span class="secno">5. </span>General API Support</a></li><li><ul class="toc"><li><a href="#genericerror-interface"><span class="secno">5.1 </span><span class="idlType formerLink idlType"><code>GenericError</code></span> interface</a></li><li><ul class="toc"><li><a href="#attributes-6"><span class="secno">5.1.1 </span>Attributes</a></li><li><a href="#constants-1"><span class="secno">5.1.2 </span>Constants</a></li></ul></li></ul></li><li><a href="#contact-search-processing-rules"><span class="secno">6. </span><span class="formerLink">Contact Search Processing Rules</span></a></li><li><a href="#use-cases-and-requirements"><span class="secno">7. </span>Use Cases and Requirements</a></li><li><ul class="toc"><li><a href="#use-cases"><span class="secno">7.1 </span>Use Cases</a></li><li><a href="#requirements"><span class="secno">7.2 </span>Requirements</a></li></ul></li><li><a href="#features-for-future-consideration"><span class="secno">A. </span>Features for Future Consideration</a></li><li><a href="#acknowledgements"><span class="secno">B. </span>Acknowledgements</a></li><li><a href="#references"><span class="secno">C. </span>References</a></li><li><ul class="toc"><li><a href="#normative-references"><span class="secno">C.1 </span>Normative references</a></li><li><a href="#informative-references"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
         <div class="section" id="conformance"><h2><span class="secno">1. </span>Conformance</h2><p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p>
 <p>The key words <em title="must" class="rfc2119">must</em>, <em title="must not" class="rfc2119">must not</em>, <em title="required" class="rfc2119">required</em>, <em title="should" class="rfc2119">should</em>, <em title="should not" class="rfc2119">should not</em>, <em title="recommended" class="rfc2119">recommended</em>, <em title="may" class="rfc2119">may</em>, and <em title="optional" class="rfc2119">optional</em> in this specification are to be interpreted as described in [<a href="#bib-RFC2119" rel="biblioentry" class="bibref">RFC2119</a>].</p>
 
@@ -1339,4 +1347,4 @@
         The editor would like to thank the input from the PhoneGap, Nokia, and OMTP BONDI groups and the feedback received from <acronym title="World Wide Web Consortium">W3C</acronym> DAP members to date ... 
       </p>
     </div>
-  <div class="appendix section" id="references"><h2><span class="secno">C. </span>References</h2><div class="section" id="normative-references"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> </dd></dl></div><div class="section" id="informative-references"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-CORE-DEVICE">[CORE-DEVICE]</dt><dd>Robin Berjon. <a href="http://dev.w3.org/2009/dap/device/"><cite>Core Device Interfaces.</cite></a> 02 December 2009. W3C Editor's Draft. (Work in progress.) URL: <a href="http://dev.w3.org/2009/dap/device/">http://dev.w3.org/2009/dap/device/</a> </dd><dt id="bib-DAP-REQS">[DAP-REQS]</dt><dd>Robin Berjon; et al. <a href="http://dev.w3.org/2009/dap/api-reqs/"><cite>Device API Requirements.</cite></a> 05 October 2009. Editor's Draft. (Work in progress.) URL: <a href="http://dev.w3.org/2009/dap/api-reqs/">http://dev.w3.org/2009/dap/api-reqs/</a> </dd><dt id="bib-HTML5">[HTML5]</dt><dd>Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/2009/WD-html5-20090825/"><cite>HTML 5.</cite></a> 25 August 2009. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2009/WD-html5-20090825/">http://www.w3.org/TR/2009/WD-html5-20090825/</a> </dd><dt id="bib-RFC4122">[RFC4122]</dt><dd>P. Leach; M. Mealling; R. Salz. <a href="http://www.ietf.org/rfc/rfc4122.txt"><cite>A Universally Unique IDentifier (UUID) URN Namespace</cite></a> July 2005. Internet RFC 4122. URL: <a href="http://www.ietf.org/rfc/rfc4122.txt">http://www.ietf.org/rfc/rfc4122.txt</a> </dd></dl></div></div></body></html>
\ No newline at end of file
+  <div class="appendix section" id="references"><h2><span class="secno">C. </span>References</h2><div class="section" id="normative-references"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> </dd></dl></div><div class="section" id="informative-references"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-CORE-DEVICE">[CORE-DEVICE]</dt><dd>Robin Berjon. <a href="http://dev.w3.org/2009/dap/device/"><cite>Core Device Interfaces.</cite></a> 02 December 2009. W3C Editor's Draft. (Work in progress.) URL: <a href="http://dev.w3.org/2009/dap/device/">http://dev.w3.org/2009/dap/device/</a> </dd><dt id="bib-DAP-REQS">[DAP-REQS]</dt><dd>Robin Berjon; et al. <a href="http://dev.w3.org/2009/dap/api-reqs/"><cite>Device API Requirements.</cite></a> 05 October 2009. Editor's Draft. (Work in progress.) URL: <a href="http://dev.w3.org/2009/dap/api-reqs/">http://dev.w3.org/2009/dap/api-reqs/</a> </dd><dt id="bib-HTML5">[HTML5]</dt><dd>Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/2009/WD-html5-20090825/"><cite>HTML 5.</cite></a> 25 August 2009. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2009/WD-html5-20090825/">http://www.w3.org/TR/2009/WD-html5-20090825/</a> </dd><dt id="bib-RFC4122">[RFC4122]</dt><dd>P. Leach; M. Mealling; R. Salz. <a href="http://www.ietf.org/rfc/rfc4122.txt"><cite>A Universally Unique IDentifier (UUID) URN Namespace</cite></a> July 2005. Internet RFC 4122. URL: <a href="http://www.ietf.org/rfc/rfc4122.txt">http://www.ietf.org/rfc/rfc4122.txt</a> </dd></dl></div></div></body></html>
Received on Wednesday, 20 January 2010 10:34:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 20 January 2010 10:34:56 GMT