<html xmlns="http://www.w3.org/1999/xhtml"><head></head><body><figure class="quote"><figcaption><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="1" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[1]</anchor-end> <cite>DUPLICITY(1) manual page</cite>
(<time>2015-05-07 01:40:02 +09:00</time> 版)
<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="http://duplicity.nongnu.org/duplicity.1.html#sect7">http://duplicity.nongnu.org/duplicity.1.html#sect7</anchor-external></p></figcaption><blockquote><p>WebDAV</p><p>webdav<strong>[</strong>s<strong>]</strong>://user<strong>[</strong>:password<strong>]</strong>@other.host<strong>[</strong>:port<strong>]</strong>/some_dir</p><p>alternatively try lftp+webdav<strong>[</strong>s<strong>]</strong>://</p></blockquote></figure><figure class="quote"><figcaption><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="2" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[2]</anchor-end> <cite xml:lang="en">RFC 4709 - Mounting Web Distributed Authoring and Versioning (WebDAV) Servers</cite>
(<time>2016-07-03 17:57:07 +09:00</time>)
<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="https://tools.ietf.org/html/rfc4709#appendix-A.2">https://tools.ietf.org/html/rfc4709#appendix-A.2</anchor-external></p></figcaption><blockquote><p>The &quot;kio&quot; library of the &quot;K Desktop Enviroment&quot;</p><p>(<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="http://www.kde.org/">http://www.kde.org/</anchor-external>) uses the URI scheme &quot;webdav&quot; to dispatch to</p><p>the system's WebDAV client.  This URI scheme is not registered, nor</p><p>is it supported on other platforms.  Furthermore, the W3C's</p><p>&quot;Architecture of the World Wide Web, Volume One&quot; explicitly advises</p><p>against defining new schemes when existing schemes can be used:</p><p>A specification SHOULD reuse an existing URI scheme (rather than</p><p>create a new one) when it provides the desired properties of</p><p>identifiers and their relation to resources.</p><p>(See <strong>[</strong>WEBARCH<strong>]</strong>, Section 2.4.)</p></blockquote></figure></body></html>