From: jamsden@us.ibm.com To: ietf-dav-versioning@w3.org Message-ID: <8525685E.00463B97.00@d54mta03.raleigh.ibm.com> Date: Thu, 6 Jan 2000 07:36:17 -0500 Subject: Re: nested DAV:rsr-or and DAV:rsr-merge A simple list connected by or and merge operators is OK with me. "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>@w3.org on 01/05/2000 01:42:38 PM Sent by: ietf-dav-versioning-request@w3.org To: ietf-dav-versioning@w3.org cc: Subject: nested DAV:rsr-or and DAV:rsr-merge In a fit of excess generality, I originally proposed that the these RSR elements be allowed to nest. Since nested DAV:rsr-or's are identical to a flattened single DAV:rsr-or (and similarly for DAV:rsr-merge), the only point for this is to allow intermingled DAV:rsr-or and DAV:rsr-merge. Since I expect few (if any) servers will implement intermingled DAV:rsr-or's and DAV:rsr-merge's in our lifetime, it seems more sensible to leave this as a possible future extension. So I propose that DAV:rsr-or and DAV:rsr-merge no longer be specified as nesting in the current protocol. Comments? Cheers, Geoff