Skip to main content

Appendix C. The 'opaquelocktoken' Scheme and URIs

Appendix C. The 'opaquelocktoken' Scheme and URIs​

The 'opaquelocktoken' URI scheme was defined in [RFC2518] (and registered by IANA) in order to create syntactically correct and easy-to-generate URIs out of UUIDs, intended to be used as lock tokens and to be unique across all resources for all time.

An opaquelocktoken URI is constructed by concatenating the 'opaquelocktoken' scheme with a UUID, along with an optional extension. Servers can create new UUIDs for each new lock token. If a server wishes to reuse UUIDs, the server MUST add an extension, and the algorithm generating the extension MUST guarantee that the same extension will never be used twice with the associated UUID.

OpaqueLockToken-URI = "opaquelocktoken:" UUID [Extension]
  ; UUID is defined in Section 3 of [RFC4122].  Note that LWS
  ; is not allowed between elements of
  ; this production.

Extension = path
  ; path is defined in Section 3.3 of [RFC3986]
Last updated on