…e URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ([ RFC4122 ]). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaque…

…he URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ([RFC4122]). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaquel…

…across all resources for all time (e.g., the urn:uuid: URN namespace defined in RFC4122 ] or the opaquelocktoken: URI scheme defined in [ RFC4918 ]). <!ELEMENT resource-id (href)> 3.2 . DAV:parent-set Property The DAV:parent-set property is an OPTIONAL property that enables clien…

…across all resources for all time (e.g., the urn:uuid: URN namespace defined in RFC4122 ] or the opaquelocktoken: URI scheme defined in [ RFC4918 ]). <!ELEMENT resource-id (href)> 3.2 . DAV:parent-set Property The DAV:parent-set property is an OPTIONAL property that enables clien…

…e URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ([ RFC4122 ]). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaque…

…e URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ([ RFC4122 ]). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaque…

…e URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ([ RFC4122 ]). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaque…

…he URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ([RFC4122]). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaquel…

…e URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ([ RFC4122 ]). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaque…

…across all resources for all time (e.g., the urn:uuid: URN namespace defined in RFC4122 ] or the opaquelocktoken: URI scheme defined in [ RFC4918 ]). <!ELEMENT resource-id (href)> 3.2 . DAV:parent-set Property The DAV:parent-set property is an OPTIONAL property that enables clien…

…e URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ( [RFC4122] ). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaque…

…e URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ( [RFC4122] ). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaque…

…e URI form defined by "A Universally Unique Identifier (UUID) URN Namespace" ([ RFC4122 ]). However, servers are free to use any URI (e.g., from another scheme) so long as it meets the uniqueness requirements. For example, a valid lock token might be constructed using the "opaque…

…serialized to result . Append U+0024 SOLIDUS ( / ) to result . Generate a UUID [RFC4122] as a string and append it to result . Return result . An example of a blob URL that can be generated by this algorithm is blob:https://example.org/40a5fb5a-d56d-4a33-b4e2-0acf6a8e5f64 . To re…

…ifies how the stream id must be initialized. A good practice is to use a UUID [[rfc4122]], which is 36 characters long in its canonical form. To avoid fingerprinting, implementations SHOULD use the forms in section 4.4 or 4.5 of RFC 4122 when generating UUIDs. An example of an al…