New issue (?): locktoken (12.1.2) syntax


12.1.2 ([1]) states:

The lock token associated with a lock. Description: The href contains one or
more opaque lock token URIs which all refer to the same lock (i.e., the
OpaqueLockToken-URI production in section 6.4).

   <!ELEMENT locktoken (href+) >"

Question: why would multiple lock tokens refer to the same lock? And *if*
there are multiple URIs referring to the same lock (a consequence of
BINDs???), what's the point in reporting more than one? Is anybody using
this? Has interoperability been tested?

[1] <>

Received on Wednesday, 10 July 2002 03:43:07 UTC