- From: <bugzilla@soe.ucsc.edu>
- Date: Tue, 11 Oct 2005 23:20:28 -0700
- To: w3c-dist-auth@w3.org
http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=91 Summary: chapter name for lock token uri schemes Product: WebDAV-RFC2518-bis Version: -07 Platform: Other URL: http://greenbytes.de/tech/webdav/draft-ietf-webdav- rfc2518bis-07.html#rfc.section.6.4 OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: 06. Locking AssignedTo: joe-bugzilla@cursive.net ReportedBy: julian.reschke@greenbytes.de QAContact: w3c-dist-auth@w3.org I think the rewrite of 6.4 may be read as if only "urn:uuid" or "opaquelocktoken" URIs are allowed. In fact, any legal URI is allowed, as long as the server makes sure that the tokens it is generating are unique. Maybe renaming the section to something like "Examples of applicable URI schemes for lock tokens" will do. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
Received on Wednesday, 12 October 2005 06:20:33 UTC