If header simplification Proposal Existing header: too complicated to determine which assertions are checked and against which resource Require all assertions be evaluated, because “resources affected by” is too vague Untagged assertions apply only to request-URI Issues from list Does this mean we need a lock model? Do we clarify which operations require which locks? Do we allow clients to submit locks in non-conditional headers? Basic design principle: make implementations “fix up”, or |