Hi, see <http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-latest.html#rfc.issue.3.1_uuids>: "Action item: if draft-mealling-uuid-urn gets accepted in time, consider referencing it and using urn:uuid URIs instead of opaquelocktoken URIs. See IETF I-D Tracker." In fact, the draft *has* been approved (see <https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=9352>) and now is in the RFC Editor's publication queue: <http://rfc-editor.org/queue.html#mealling-uuid-urn>. Thus, I'd propose to a) to mention urn:uuid URIs in the description of DAV:resource-id, b) to use them in examples and c) add an informative reference to draft-mealling-uuid-urn Feedback appreciated, Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760Received on Friday, 14 January 2005 16:10:02 UTC
This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:31 UTC