W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > April to June 1998

RE: no Versioning or Variants

From: Judith Slein <slein@wrc.xerox.com>
Date: Tue, 21 Apr 1998 07:00:13 PDT
Message-Id: <3.0.3.32.19980421100013.00a0d100@pop-server.wrc.xerox.com>
To: "Saveen Reddy (Exchange)" <saveenr@Exchange.Microsoft.com>
Cc: "'www-webdav-dasl@w3.org'" <www-webdav-dasl@w3.org>
I think I am the only one pushing in the opposite direction.  And only
because variants can exist today, and if we don't say anything about them,
I guess it is up to each individual server what it wants to do in the event
that there are multiple variants for a resource.  Maybe that's ok until
WebDAV has a versioning spec ready, which shouldn't be too long in any case.

I guess if you search on any variant-related properties, they will not be
the HTTP headers Content-Language, etc., but the corresponding DAV
properties getcontentlanguage, etc.  I do not think you can get access to
all available variants by doing this.  The WebDAV property definitions say
they have the value you would see in an HTTP GET response where the request
had no accept headers.  This should identify the variant that would be
returned if the client expressed no preference, not give you a list of all
available variants.

--Judy

At 02:56 PM 4/20/98 PDT, Saveen Reddy (Exchange) wrote:
>To be specific ... I agree that DASl should say nothing about versioning or
>variants until WebDAV does.
>
>We are in agreement on the second point as well -- DASL supports searching
>on those properties but (for the time being at least) takes no further
>stance on variants.
>
>-Saveen
>
>-----Original Message-----
>From: Jim Davis [mailto:jdavis@parc.xerox.com]
>Sent: Monday, April 20, 1998 2:17 PM
>To: www-webdav-dasl@w3.org
>Subject: RE: no Versioning or Variants
>
>
>At 02:00 PM 4/20/98 PDT, Saveen Reddy (Exchange) wrote:
>>At 04:01 PM 4/16/98 PDT, Jim Davis wrote:
>>>As I recall, at the IETF BOF we agreed to remove any mention of versioning
>>>or variants from the DASL spec until such time as the WebDAV protocol (or
>>>some other relevant protocol) defines them.
>
>> HTTP/1.1 defines them but only within the context of
>>content-negotiation -- authoring is less clear. ...
>> The further complication is that, as I understand it,
>>versioning and variants will use the same model on WEBDAV (this is based on
>>comments I heard at the LA IETF). We would need to have the DAV models for
>>both before we can address them in DASL.
>
>Does this mean you agree that DASL should say nothing about either
>versioning and variants (until WebDAV does)?
>
>As for the small amount of variant support in HTTP, well naturally DASL
>should be able to search on any exposed property (e.g. content-language or
>content-type) there's nothing special we need to do there.  But there's
>nothing else to say about variants beyond that.  I mean, how is searching
>against the content-type property and different than searching against the
>foobar:quux property?  
>
>
>
Name:			Judith A. Slein
E-Mail:		slein@wrc.xerox.com
Internal Phone:  	8*222-5169
Fax:			(716) 422-2938
MailStop:		105-50C
Web Site:    http://www.nde.wrc.xerox.com/users/Slein/slein.htm
Received on Tuesday, 21 April 1998 09:54:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:03 GMT