From: jamsden@us.ibm.com To: ietf-dav-versioning@w3.org Message-ID: <852568BE.004291F8.00@d54mta03.raleigh.ibm.com> Date: Tue, 11 Apr 2000 08:07:03 -0400 Subject: Re: Questions on activities <geoff> The majority of web servers (such as Apache and IIS) only handle a few top level name mappings, and hand the rest of the processing off to the underlying repository. So it is reasonable to associate some collection with a class of metadata, and map the URL of that collection to the appropriate underlying repository, but this does not allow you to make arbitrary associations between URL's and different kinds of metadata potentially from different repositories. </geoff> <jra> This won't be true of WebDAV servers that support BIND. They will have to have much more support for mappings. </jra> While we are waiting for such WebDAV servers to be written, I'd like to make it possible to have implementations that are significantly simpler, and assume all but the top level name mappings are being maintained by the underlying repository. <jra> These are not repository semantics, but WebDAV binding and versioning semantics. The implementation shouldn't be in the repository managers as this would require repository managers to know and implement WebDAV semantics, something they shouldn't be expected to do. </jra>