W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2000

RE: DAV: header values

From: Clemm, Geoff <gclemm@Rational.Com>
Date: Thu, 18 May 2000 12:46:52 -0400
Message-ID: <65B141FB11CCD211825700A0C9D609BC01D4D8B6@chef.lex.rational.com>
To: w3c-dist-auth@w3.org
I'd probably vote for

  extend = Coded-URL | token

so that standard DAV defined extensions can be specified in a terse form.


-----Original Message-----
From: Greg Stein [mailto:gstein@lyra.org]
Sent: Monday, April 10, 2000 5:37 PM
To: Juergen Reuter
Cc: jjh@ira.uka.de; w3c-dist-auth@w3.org
Subject: Re: DAV: header values 

On Mon, 10 Apr 2000, Juergen Reuter wrote:
> P.S.:
> However, the rule
>    extend = Coded-URL
> should be fine, because the rule
>    Coded-URL = "<" absoluteURI ">"
> implies that, as soon as you have encountered a "<", you can
> accept as many "," as you find, belonging all to the absoluteURI,
> until you finally reach a ">". (I suppose that is the reason why
> people think that the brackets are needed. :-))


All righty then... I'll resubmit my proposal:

   extend = "<" absoluteURI ">"

For semantic purposes, I expanded Coded-URL since we will certainly have
URI values in there (e.g. DAV:bindings) rather than URLs. In an If:
header, the "URL" term makes sense.

Back to my original point, then: does anybody see a problem if I updated
mod_dav to use the following DAV: header:

  DAV: 1,2,<http://apache.org/dav/0.9.16>



Greg Stein, http://www.lyra.org/
Received on Thursday, 18 May 2000 12:52:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:21 UTC