- From: Richard Tibbett via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 18 Feb 2010 18:18:35 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/contacts
In directory hutz:/tmp/cvs-serv2346
Modified Files:
Overview.html
Log Message:
- Removed recommendation that UUID be used as the Contact.id attribute. Updated the example to demonstrate a URL based id approach.
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/contacts/Overview.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- Overview.html 18 Feb 2010 18:16:00 -0000 1.42
+++ Overview.html 18 Feb 2010 18:18:33 -0000 1.43
@@ -357,15 +357,11 @@
readonly attribute DOMString id
</dt>
<dd>
- <p class='note'>
- Perhaps we don't want to recommend the use of UUID URN here. Saying that id must be globally unique could suffice, and there may be good reasons why someone would want to use something else (e.g. a SHA mailbox as in FOAF).
- </p>
<p>A globally unique identifier for the given <code>Contact</code> object. Each <code>Contact</code> referenced from <code>Contacts</code> MUST include a non-empty <code>id</code> value.</p>
<p>An implementation MUST maintain this globally unique resource identifier when a Contact is added to, or present within, an Address Book.</p>
<p>An implementation MAY use an IANA registered identifier format. The value can also be a non-standard format.</p>
- <p>It is RECOMMENDED that an implementation assign the id attribute as a <abbr title="Universally Unique IDentifier">UUID</abbr> URN as defined in [[RFC4122]].</p>
- <pre class="example sh_javascript">{id: 'urn:uuid:d13d4fd0-4ce9-1cef-b1f2-10a9c1446bf0'}</pre>
+ <pre class="example sh_javascript">{id: 'http://foo.com/myservice/contacts/contact/45fye54dVx'}</pre>
</dd>
<dt>
Contact clone ()
Received on Thursday, 18 February 2010 18:18:36 UTC