W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2003


From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 31 Jul 2003 15:38:31 +0200
To: "Nevermann, Dr., Peter" <Peter.Nevermann@softwareag.com>, <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCAEHHIAAA.julian.reschke@gmx.de>

You can use a URN: scheme if you find one that satisifies the uniqueness
constraints. You could also register your own URN NID and come up with a
custom scheme.

I personally would recommend just to use the RFC2518 "opaquelocktoken"
scheme because it already has what you need.

Finally, the BIND spec isn't defining a new scheme for the simple reason we
don't need one.

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

  -----Original Message-----
  From: w3c-dist-auth-request@w3.org [mailto:w3c-dist-auth-request@w3.org]On
Behalf Of Nevermann, Dr., Peter
  Sent: Thursday, July 31, 2003 3:18 PM
  To: 'w3c-dist-auth@w3.org'
  Subject: BIND:

  The BIND spec (draft-ietf-webdav-bind-02) states at 3.1 DAV:resource-id

  "The value of DAV:resource-id is a URI, and may use any registered URI
scheme that guarantees the uniqueness of the value across all resources for
all time (e.g. the opaquelocktoken: scheme defined in [RFC2518])."

  I found registered URI schemes at:
http://www.iana.org/assignments/uri-schemes. So, can I choose one of them,
e.g. urn: ? Or should I invent my own? :-)

  Why doesn't the BIND spec define the URI scheme to be used?

Received on Thursday, 31 July 2003 09:38:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:29 UTC