- From: Tim Ellison <Tim_Ellison@uk.ibm.com>
- Date: Tue, 19 Jun 2001 14:55:25 +0100
- To: ietf-dav-versioning@w3.org
"Jim Amsden" <jamsden@us.ibm.com> wrote: > The reason we can't introduce new resource types for > all of the versioning resources is because we have to > support down-level clients that only know about > DAV:collection. Not sure that I follow this argument, since 'down-level' clients will only be looking for DAV:collection. But I take this to mean you do not support extending DAV:resourcetype. > For new resources that down-level clients couldn't > possibly know about, workspaces, activities, baselines, > etc., we don't have this restriction. What do you mean? I thought you just stated that we can't introduce new resource types to retain forward compatibility. > I agree with Greg and Tim. We should be as specific > as we can about declared type and only compromise when > required by interoperability considerations. The type is made quite explicit by the supported live properties and supported methods. The only debate was how to marshal the 'type'. Tim
Received on Tuesday, 19 June 2001 09:55:28 UTC