Next message: Tim Ellison/OTT/OTI: "RE: Revision of a stable-URL versioned resource"
To: ietf-dav-versioning@w3.org
Message-ID: <OF02375865.EB511D69-ON852568B9.004EEC9C@ott.oti.com>
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Thu, 6 Apr 2000 10:29:39 -0400
Subject: RE: Stable URLs
<geoff>
So the bottom line is that I agree with most of your
description, except for requiring a special header be
used to access stable URL's, ...
</geoff>
So I will assume that we shall drop the requirement to specify
Workspace:
to mean that the URL is stable.
I agree that having the ability to have a link to a stable URL is
desirable. Therefore we must introduce the concept of a metadata area of
the URL namespace so that the server knows a URL is stable.
I'm not sure that using virtual hosting will be acceptable, it would
clearly be strange to be told that a resource's stable URL is on a
different host.
<geoff>
... and that the effect of a method on a stable URL to
a resource will always be the same as the operation on
a dynamic URL to a resource.
</geoff>
Then we have different views of what a stable URL is<g>
I see them as unique identifiers of a resource. With this view, whether
you got to the resource via its unique identifier, or via a dynamically
resolved graph walk is immaterial.
Regards,
Tim