Subject: RFC2518 errata in boolean logic applied to untagged-token-list production?

From: "Lisa Dusseault" <[email-masked]>
Date: Mon, 17 Sep 2001 09:45:57 -0700

Section 9.4.1 states that untagged tokens in a token list are to be OR'ed
together:

"If multiple No-tag-list productions are used then one only
   needs to match the state of the resource for the method to be allowed
   to continue."

However, section 9.4.3 throws "Not" into the mix and uses the word AND to
describe the logic combining two untagged tokens:

"If: (Not <locktoken:write1> <locktoken:write2>)

   When submitted with a request, this If header requires that all
   operand resources must not be locked with locktoken:write1 and must
   be locked with locktoken:write2."

I assume the last 'and' must be replaced with 'or'?

lisa