From w3c-dist-auth-request@w3.org Sat Dec 1 18:26:40 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24278 for ; Sat, 1 Dec 2001 18:26:40 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id SAA15140; Sat, 1 Dec 2001 18:20:59 -0500 (EST) Resent-Date: Sat, 1 Dec 2001 18:20:59 -0500 (EST) Resent-Message-Id: <200112012320.SAA15140@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id SAA14977 for ; Sat, 1 Dec 2001 18:20:30 -0500 (EST) Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id SAA20431 for ; Sat, 1 Dec 2001 18:20:31 -0500 Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22]) by e1.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id SAA306992 for ; Sat, 1 Dec 2001 18:17:15 -0500 Received: from d01ml243.pok.ibm.com (d01ml243.pok.ibm.com [9.117.200.72]) by northrelay02.pok.ibm.com (8.11.1m3/NCO v5.01) with ESMTP id fB1NJwC63052 for ; Sat, 1 Dec 2001 18:19:58 -0500 To: w3c-dist-auth@w3.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Jason Crawford" Date: Sat, 1 Dec 2001 18:08:43 -0500 X-MIMETrack: Serialize by Router on D01ML243/01/M/IBM(Release 5.0.9 |November 16, 2001) at 12/01/2001 06:19:57 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: RE: Purpose of Namespace Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5704 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: << So I'd say all that needs to be done is to get rid of the sentence that refers to concatenating the namespace URL with the local node name, and we are done with this issue. >> Sounds good. One other thing is that in places where it refers to a property with it's concatenated name, I'll have to change the reference to use a [URI, local name] pair. For example section 8.2.2... In this example, the client requests the server to set the value of the http://www.w3.com/standards/z39.50/Authors property, and to remove the property http://www.w3.com/standards/z39.50/Copyright- Owner. Since the Copyright-Owner property could not be removed, no becomes In this example, the client requests the server to set the value of the [http://www.w3.com/standards/z39.50/,Authors] property, and to remove the property [http://www.w3.com/standards/z39.50/,Copyright- Owner]. Since the Copyright-Owner property could not be removed, no or perhaps In this example, the client requests the server to set the value of the Authors property, and to remove the property Copyright- Owner. Since the Copyright-Owner property could not be removed, no If you have a preference for this, let me know, otherwise I'll just figure it out. J. ------------------------------------------ Phone: 914-784-7569, ccjason@us.ibm.com From w3c-dist-auth-request@w3.org Sat Dec 1 21:27:54 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26547 for ; Sat, 1 Dec 2001 21:27:54 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id VAA21966; Sat, 1 Dec 2001 21:22:44 -0500 (EST) Resent-Date: Sat, 1 Dec 2001 21:22:44 -0500 (EST) Resent-Message-Id: <200112020222.VAA21966@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id VAA21946 for ; Sat, 1 Dec 2001 21:22:28 -0500 (EST) Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id VAA07087 for ; Sat, 1 Dec 2001 21:22:29 -0500 Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22]) by e1.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id VAA202268; Sat, 1 Dec 2001 21:19:12 -0500 Received: from d01ml243.pok.ibm.com (d01ml243.pok.ibm.com [9.117.200.72]) by northrelay02.pok.ibm.com (8.11.1m3/NCO v5.01) with ESMTP id fB22LtC81202; Sat, 1 Dec 2001 21:21:55 -0500 To: rohit.marwaha@oracle.com, w3c-dist-auth@w3.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Jason Crawford" Date: Sat, 1 Dec 2001 21:13:36 -0500 X-MIMETrack: Serialize by Router on D01ML243/01/M/IBM(Release 5.0.9 |November 16, 2001) at 12/01/2001 09:21:55 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: Re: How to implement WebDav http extension methods in Java Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5705 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: See the following URL and search for "java" to see a pretty good list of what people have done with Java... http://www.webdav.org/projects/ J. -----Original Message----- From: Rohit.Marwaha [mailto:rohit.marwaha@oracle.com] Sent: Friday, November 30, 2001 1:18 AM To: w3c-dist-auth@w3.org Cc: Rohit.Marwaha Subject: [Moderator Action] [Fresher to webdav] How to implement WebDav http extension methods in Java Hi All, I am a new comer to this subject. I am looking to implement a client in Java which can communicate with WebDav enable server. However it looks like Java's networking classes like URL, URLConnection and HttpURLConnection only support standard HTTP methods. Do I need to look at sockets to implement a client or is there a better way available? Thanks in advance. - Rohit From w3c-dist-auth-request@w3.org Sun Dec 2 13:59:22 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27549 for ; Sun, 2 Dec 2001 13:59:21 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id NAA19674; Sun, 2 Dec 2001 13:54:42 -0500 (EST) Resent-Date: Sun, 2 Dec 2001 13:54:42 -0500 (EST) Resent-Message-Id: <200112021854.NAA19674@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id NAA19654 for ; Sun, 2 Dec 2001 13:54:35 -0500 (EST) Received: from server1.software-ag.de (server1.software-ag.de [193.26.194.2]) by tux.w3.org (8.9.3/8.9.3) with SMTP id NAA17308 for ; Sun, 2 Dec 2001 13:54:35 -0500 Message-ID: From: "Pill, Juergen" To: "'Jason Crawford'" , rohit.marwaha@oracle.com, w3c-dist-auth@w3.org Date: Sun, 2 Dec 2001 19:54:16 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Subject: RE: How to implement WebDav http extension methods in Java Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5706 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: You may want to have a look at http://jakarta.apache.org/slide/index.html. It includes a Java open source implementation of a WebDAV API. Best regards Juergen -----Original Message----- From: Jason Crawford [mailto:ccjason@us.ibm.com] Sent: Sonntag, 2. Dezember 2001 03:14 To: rohit.marwaha@oracle.com; w3c-dist-auth@w3.org Subject: Re: How to implement WebDav http extension methods in Java See the following URL and search for "java" to see a pretty good list of what people have done with Java... http://www.webdav.org/projects/ J. -----Original Message----- From: Rohit.Marwaha [mailto:rohit.marwaha@oracle.com] Sent: Friday, November 30, 2001 1:18 AM To: w3c-dist-auth@w3.org Cc: Rohit.Marwaha Subject: [Moderator Action] [Fresher to webdav] How to implement WebDav http extension methods in Java Hi All, I am a new comer to this subject. I am looking to implement a client in Java which can communicate with WebDav enable server. However it looks like Java's networking classes like URL, URLConnection and HttpURLConnection only support standard HTTP methods. Do I need to look at sockets to implement a client or is there a better way available? Thanks in advance. - Rohit From w3c-dist-auth-request@w3.org Sun Dec 2 14:10:16 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27733 for ; Sun, 2 Dec 2001 14:10:16 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id OAA20106; Sun, 2 Dec 2001 14:05:59 -0500 (EST) Resent-Date: Sun, 2 Dec 2001 14:05:59 -0500 (EST) Resent-Message-Id: <200112021905.OAA20106@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id OAA20065 for ; Sun, 2 Dec 2001 14:05:46 -0500 (EST) Received: from sus-ma1it00.rational.com (ext-37184.rational.com [192.229.37.184]) by tux.w3.org (8.9.3/8.9.3) with SMTP id OAA18165 for ; Sun, 2 Dec 2001 14:05:46 -0500 Received: from 192.168.215.70 by sus-ma1it00.rational.com (InterScan E-Mail VirusWall NT); Sun, 02 Dec 2001 14:05:15 -0500 Received: by sus-ma1it00.rational.com with Internet Mail Service (5.5.2653.19) id ; Sun, 2 Dec 2001 14:05:15 -0500 Message-ID: <3906C56A7BD1F54593344C05BD1374B1050291D5@SUS-MA1IT01> From: "Clemm, Geoff" To: w3c-dist-auth@w3.org Date: Sun, 2 Dec 2001 14:05:11 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: Purpose of Namespace Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5707 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: I'd vote for the latter (i.e. just refer to the property without the namespace), but either is OK by me. Cheers, Geoff -----Original Message----- From: Jason Crawford [mailto:ccjason@us.ibm.com] Sent: Saturday, December 01, 2001 6:09 PM To: w3c-dist-auth@w3.org Subject: RE: Purpose of Namespace << So I'd say all that needs to be done is to get rid of the sentence that refers to concatenating the namespace URL with the local node name, and we are done with this issue. >> Sounds good. One other thing is that in places where it refers to a property with it's concatenated name, I'll have to change the reference to use a [URI, local name] pair. For example section 8.2.2... In this example, the client requests the server to set the value of the http://www.w3.com/standards/z39.50/Authors property, and to remove the property http://www.w3.com/standards/z39.50/Copyright- Owner. Since the Copyright-Owner property could not be removed, no becomes In this example, the client requests the server to set the value of the [http://www.w3.com/standards/z39.50/,Authors] property, and to remove the property [http://www.w3.com/standards/z39.50/,Copyright- Owner]. Since the Copyright-Owner property could not be removed, no or perhaps In this example, the client requests the server to set the value of the Authors property, and to remove the property Copyright- Owner. Since the Copyright-Owner property could not be removed, no If you have a preference for this, let me know, otherwise I'll just figure it out. J. ------------------------------------------ Phone: 914-784-7569, ccjason@us.ibm.com From w3c-dist-auth-request@w3.org Mon Dec 3 04:10:50 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24584 for ; Mon, 3 Dec 2001 04:10:49 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id EAA20995; Mon, 3 Dec 2001 04:08:17 -0500 (EST) Resent-Date: Mon, 3 Dec 2001 04:08:17 -0500 (EST) Resent-Message-Id: <200112030908.EAA20995@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id EAA20965 for ; Mon, 3 Dec 2001 04:07:59 -0500 (EST) Received: from greenbytes.de (mail.greenbytes.de [217.5.201.10] (may be forged)) by tux.w3.org (8.9.3/8.9.3) with ESMTP id EAA04238 for ; Mon, 3 Dec 2001 04:07:58 -0500 Received: from apu [192.168.1.23] by greenbytes.de [217.5.201.11] with SMTP (MDaemon.v3.5.3.R) for ; Mon, 03 Dec 2001 10:07:48 +0100 From: "Stefan Eissing" To: Date: Mon, 3 Dec 2001 10:07:38 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3906C56A7BD1F54593344C05BD1374B1050291D5@SUS-MA1IT01> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-MDRemoteIP: 192.168.1.23 X-Return-Path: stefan.eissing@greenbytes.de X-MDaemon-Deliver-To: w3c-dist-auth@w3.org Subject: RE: Purpose of Namespace Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5708 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit I also think the latter is better readable. As an alternative (I think) James Clark once proposed to use a wording like {http://www.w3.com/standards/z39.50/}Authors if a name with namespace needs to be mentioned. But if the namespace is clear from the context, why bother... //Stefan > -----Original Message----- > From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Clemm, Geoff > Sent: Sunday, December 02, 2001 8:05 PM > To: w3c-dist-auth@w3.org > Subject: RE: Purpose of Namespace > > > I'd vote for the latter (i.e. just refer to the property without > the namespace), but either is OK by me. > > Cheers, > Geoff > > -----Original Message----- > From: Jason Crawford [mailto:ccjason@us.ibm.com] > Sent: Saturday, December 01, 2001 6:09 PM > To: w3c-dist-auth@w3.org > Subject: RE: Purpose of Namespace > > > > << > So I'd say all that needs to be done is to get rid of the sentence that > refers to concatenating the namespace URL with the local node name, > and we are done with this issue. > >> > Sounds good. > > One other thing is that in places where it refers to a property with it's > concatenated name, I'll have to change > the reference to use a [URI, local name] pair. > > For example section 8.2.2... > > In this example, the client requests the server to set the value of > the http://www.w3.com/standards/z39.50/Authors property, and to > remove the property http://www.w3.com/standards/z39.50/Copyright- > Owner. Since the Copyright-Owner property could not be removed, no > > becomes > > In this example, the client requests the server to set the value of > the [http://www.w3.com/standards/z39.50/,Authors] property, and to > remove the property [http://www.w3.com/standards/z39.50/,Copyright- > Owner]. Since the Copyright-Owner property could not be removed, no > > or perhaps > > In this example, the client requests the server to set the value of > the Authors > property, and to > remove the property Copyright- > Owner. Since the Copyright-Owner property could not be removed, no > > If you have a preference for this, let me know, otherwise I'll just figure > it out. > > J. > > ------------------------------------------ > Phone: 914-784-7569, ccjason@us.ibm.com > > > From w3c-dist-auth-request@w3.org Mon Dec 3 19:10:57 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14479 for ; Mon, 3 Dec 2001 19:10:56 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id TAA05365; Mon, 3 Dec 2001 19:08:54 -0500 (EST) Resent-Date: Mon, 3 Dec 2001 19:08:54 -0500 (EST) Resent-Message-Id: <200112040008.TAA05365@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id TAA05345 for ; Mon, 3 Dec 2001 19:08:32 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id TAA22263 for ; Mon, 3 Dec 2001 19:08:32 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id QAA29459 for ; Mon, 3 Dec 2001 16:08:36 -0800 (PST) From: "Jim Whitehead" To: "WebDAV" Date: Mon, 3 Dec 2001 16:08:04 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Subject: RE: java DAV Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5709 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Accidentally caught by the spam filter. I have added to the accept2 list for w3c-dist-auth. - Jim -----Original Message----- From: Michael Arick [mailto:michaelarick@yahoo.com] Sent: Monday, December 03, 2001 10:19 AM To: Pill, Juergen Cc: 'Jason Crawford'; rohit.marwaha@oracle.com; w3c-dist-auth@w3.org Subject: [Moderator Action] RE: java DAV I had some trouble with Jakarta Slide on the client side. I have had more success with SkunkDAV. It seems more intuitive to me. -marick On Sun, 2001-12-02 at 10:54, Pill, Juergen wrote: > You may want to have a look at http://jakarta.apache.org/slide/index.html. > It includes a Java open source implementation of a WebDAV API. > > Best regards > > Juergen > > > > -----Original Message----- > From: Jason Crawford [mailto:ccjason@us.ibm.com] > Sent: Sonntag, 2. Dezember 2001 03:14 > To: rohit.marwaha@oracle.com; w3c-dist-auth@w3.org > Subject: Re: How to implement WebDav http extension methods in Java > > > > See the following URL and search for "java" to see a pretty good list of > what people have done with Java... > > http://www.webdav.org/projects/ > > J. > > > -----Original Message----- > From: Rohit.Marwaha [mailto:rohit.marwaha@oracle.com] > Sent: Friday, November 30, 2001 1:18 AM > To: w3c-dist-auth@w3.org > Cc: Rohit.Marwaha > Subject: [Moderator Action] [Fresher to webdav] How to implement WebDav > http extension methods in Java > > Hi All, > > I am a new comer to this subject. I am looking to implement a client in > Java > which can communicate with WebDav enable server. However it looks like > Java's > networking classes like URL, URLConnection and HttpURLConnection only > support standard HTTP methods. Do I need to look at sockets to implement a > client > or is there a better way available? > > Thanks in advance. > > - Rohit > > From w3c-dist-auth-request@w3.org Mon Dec 3 20:31:26 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19114 for ; Mon, 3 Dec 2001 20:31:26 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id UAA08880; Mon, 3 Dec 2001 20:29:51 -0500 (EST) Resent-Date: Mon, 3 Dec 2001 20:29:51 -0500 (EST) Resent-Message-Id: <200112040129.UAA08880@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id UAA08860 for ; Mon, 3 Dec 2001 20:29:31 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id UAA32249 for ; Mon, 3 Dec 2001 20:29:31 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id RAA20349 for ; Mon, 3 Dec 2001 17:29:37 -0800 (PST) From: "Jim Whitehead" To: "WebDAV" Date: Mon, 3 Dec 2001 17:29:04 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Subject: End: WG Last Call on ACL specification Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5710 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit This message marks the end of the WebDAV Working Group last call for comments on the WebDAV Access Control Protocol specification, draft-ietf-webdav-acl-07. This last call period began on Friday, November 9, 2001, and ended December 3, 2001. The message starting the last call was: http://lists.w3.org/Archives/Public/w3c-dist-auth/2001OctDec/0178.html While the last call period has ended, you may still submit comments on the -07 (or later) revision of the specification. My best estimate for the completion of a new revision of draft-ietf-webdav-acl is December 7 (this Friday). As well, due to the IETF meeting, a new Internet-Draft can not be submitted until the end of this meeting (December 17), so any comments submitted before that time would be easily incorporated into the next revision. Note that with the end of the last call period, the burden of evidence required to effect a significant design change in the protocol is now much greater. My characterization of the comments received during this last call period is that fixing them requires generally minor changes to the specification. This leads me to believe that the specification has, in fact, resolved known technical tradeoffs, and is stable. As a result, unless feedback to the contrary is received from the Minneapolis IETF meeting, I intend on submitting the next revision (draft-ietf-webdav-acl-08) to the IESG for approval as a Proposed Standard. There will be no further last call for comments period within the working group, although there is one last IETF-wide call for comments that will occur, initiated by the IESG. - Jim From w3c-dist-auth-request@w3.org Tue Dec 4 13:22:54 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05384 for ; Tue, 4 Dec 2001 13:22:54 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id NAA13717; Tue, 4 Dec 2001 13:21:25 -0500 (EST) Resent-Date: Tue, 4 Dec 2001 13:21:25 -0500 (EST) Resent-Message-Id: <200112041821.NAA13717@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id NAA13569 for ; Tue, 4 Dec 2001 13:20:57 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id NAA21147 for ; Tue, 4 Dec 2001 13:20:57 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id KAA18294 for ; Tue, 4 Dec 2001 10:21:00 -0800 (PST) From: "Jim Whitehead" To: "WebDAV" Date: Tue, 4 Dec 2001 10:20:29 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: Subject: RE: WG Last Call on ACL specification Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5711 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit > As a result, unless feedback to the > contrary is received from the Minneapolis IETF meeting, Er, make that the *Salt Lake City* IETF meeting: - Jim From w3c-dist-auth-request@w3.org Wed Dec 5 17:30:43 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16840 for ; Wed, 5 Dec 2001 17:30:43 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id RAA07474; Wed, 5 Dec 2001 17:28:30 -0500 (EST) Resent-Date: Wed, 5 Dec 2001 17:28:30 -0500 (EST) Resent-Message-Id: <200112052228.RAA07474@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id RAA07300 for ; Wed, 5 Dec 2001 17:28:03 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA06989 for ; Wed, 5 Dec 2001 17:28:03 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id OAA09519 for ; Wed, 5 Dec 2001 14:28:07 -0800 (PST) From: "Jim Whitehead" To: "WebDAV" Date: Wed, 5 Dec 2001 14:27:35 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: Using WebDav Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5712 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Accidentally caught by the spam filter. I have added to the accept2 list. - Jim -----Original Message----- From: nupur.bhasin@india.birlasoft.com [mailto:nupur.bhasin@india.birlasoft.com] Sent: Wednesday, December 05, 2001 2:15 AM To: w3c-dist-auth@w3.org Subject: [Moderator Action] Using WebDav Hi, I am a beginner in this area.Just got an introduction to WebDav. I am supposed to create folders on my web server using webdav could anybody at your end get me started on how to get this done? Thanks and Regards, Nupur Bhasin From w3c-dist-auth-request@w3.org Wed Dec 5 18:11:51 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19512 for ; Wed, 5 Dec 2001 18:11:51 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id SAA09806; Wed, 5 Dec 2001 18:05:26 -0500 (EST) Resent-Date: Wed, 5 Dec 2001 18:05:26 -0500 (EST) Resent-Message-Id: <200112052305.SAA09806@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id SAA09784 for ; Wed, 5 Dec 2001 18:05:12 -0500 (EST) Received: from mail0.rawbw.com (mail0.rawbw.com [198.144.192.41]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id SAA12273 for ; Wed, 5 Dec 2001 18:05:12 -0500 Received: from moose ([198.144.203.249]) by mail0.rawbw.com (8.11.3/8.11.3) with SMTP id fB5N5AD42731 for ; Wed, 5 Dec 2001 15:05:11 -0800 (PST) (envelope-from lisa@xythos.com) From: "Lisa Dusseault" To: "Webdav WG" Date: Wed, 5 Dec 2001 15:03:10 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Subject: FW: 52nd IETF - WWW Distributed Authoring and Versioning WG (webdav) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5713 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Here's the agenda I sent in.. I canvased a few people very last-minute for agenda items, but if I've missed any we'll cover them during agenda bashing and surely be able to squeeze them in. lisa -----Original Message----- From: dinaras@cnri.reston.va.us [mailto:dinaras@cnri.reston.va.us]On Behalf Of agenda@ietf.org Sent: Wednesday, December 05, 2001 12:44 PM To: IETF-Announce: Subject: 52nd IETF - WWW Distributed Authoring and Versioning WG (webdav) WWW Distributed Authoring and Versioning WG (webdav) Monday, December 10 at 1530-1730 ================================ CHAIRS: Jim Whitehead (Not attending) Lisa Dusseault AGENDA: 1. Agenda bashing ( 5 min) 2. Review of ACL draft status & new issues (10 min) ACL draft currently in Working Group last call New draft expected shortly after IETF 3. Discussion of interop progress and plans (10 min) When to hold next interop? Virtual or real? 4. RFC 2518 revision issues (90 min) Error reporting Unused features Namespace usage From w3c-dist-auth-request@w3.org Wed Dec 5 18:14:31 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19691 for ; Wed, 5 Dec 2001 18:14:30 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id SAA10055; Wed, 5 Dec 2001 18:13:25 -0500 (EST) Resent-Date: Wed, 5 Dec 2001 18:13:25 -0500 (EST) Resent-Message-Id: <200112052313.SAA10055@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id SAA10030 for ; Wed, 5 Dec 2001 18:13:18 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id SAA13457 for ; Wed, 5 Dec 2001 18:13:18 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id PAA23112 for ; Wed, 5 Dec 2001 15:13:23 -0800 (PST) From: "Jim Whitehead" To: "WebDAV" Date: Wed, 5 Dec 2001 15:12:50 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: Announcing new Co-Chair: Lisa Dusseault Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5714 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit I am very pleased to announce that Lisa Dusseault, Xythos is now Co-Chair of the WebDAV Working Group. Lisa and I will be working together to finish existing specifications (access control, advanced collections), and to revise existing ones (RFC 2518 revision). There is a lot of work ahead of us, but I am confident that with Lisa as Chair, we'll be able to make steady progress towards reaching our goals. - Jim Whitehead Co-Chair, WebDAV Working Group From w3c-dist-auth-request@w3.org Wed Dec 5 18:27:57 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20418 for ; Wed, 5 Dec 2001 18:27:57 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id SAA11808; Wed, 5 Dec 2001 18:26:48 -0500 (EST) Resent-Date: Wed, 5 Dec 2001 18:26:48 -0500 (EST) Resent-Message-Id: <200112052326.SAA11808@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id SAA11765 for ; Wed, 5 Dec 2001 18:26:34 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id SAA15129 for ; Wed, 5 Dec 2001 18:26:34 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id PAA27010; Wed, 5 Dec 2001 15:26:38 -0800 (PST) From: "Jim Whitehead" To: "Peter Raymond" , Date: Wed, 5 Dec 2001 15:26:05 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20CF1CE11441D411919C0008C7C5A13B034B838B@stalmail.eu.merant.com> Subject: RE: Issues/questions about the bindings protocol specification... Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5715 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Peter Raymond writes: > A group of people here at MERANT have recently completed > reading/reviewing the bindings protocol document. We > recorded some issues/questions about the specification. Super -- thank you very much for posting your comments on this specification. > does anyone know the status of the document, there are open > issues etc, is there a timeframe for it becoming a > "proposed standard"? At present, it has gone through a last call, which resulted in a list of issues being recorded: http://www1.ics.uci.edu/pub/ietf/webdav/collection/bind-issues.html The editors of the document held a series of teleconferences about the specification, minutes from which are available towards the bottom of http://www.ics.uci.edu/pub/ietf/webdav/ Resolutions to issues have been recorded in the issues list. > Is anyone actively editing or revising the document? At present, no. It has been my intent to work on this as soon as the access control specification is completed. Since the ACL specification is nearly complete, I anticipate working on this specification soon. We'll have another last call, perhaps two, and then it'll get sent off. > BTW...are there any server vendors out there that implement > or are thinking of implementing the BIND method? Similarly > are any clients using it? None that I know of, though I have always felt that this capability is needed before most document management systems can expose their full functionality via DAV. - Jim From w3c-dist-auth-request@w3.org Wed Dec 5 19:20:53 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22465 for ; Wed, 5 Dec 2001 19:20:52 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id TAA16843; Wed, 5 Dec 2001 19:19:11 -0500 (EST) Resent-Date: Wed, 5 Dec 2001 19:19:11 -0500 (EST) Resent-Message-Id: <200112060019.TAA16843@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id TAA16798 for ; Wed, 5 Dec 2001 19:18:57 -0500 (EST) Received: from inet-mail4.oracle.com (inet-mail4.oracle.com [148.87.2.204]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id TAA20389; Wed, 5 Dec 2001 19:18:57 -0500 Received: from rgmgw6.us.oracle.com (rgmgw6.us.oracle.com [138.1.191.15]) by inet-mail4.oracle.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fB609vx15354; Wed, 5 Dec 2001 16:09:57 -0800 (PST) Received: from oracle.com (ikirnos-pc.us.oracle.com [130.35.68.81]) by rgmgw6.us.oracle.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fB60Itv09098; Wed, 5 Dec 2001 17:18:55 -0700 (MST) Message-ID: <3C0EBA0C.E8533979@oracle.com> Date: Wed, 05 Dec 2001 16:21:32 -0800 From: Ilya Kirnos X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: w3c-dist-auth@w3.org CC: www-webdav-dasl@w3.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: DASL? Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5716 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Sorry for the cross-post -- I suppose this should be going to just the DASL list, but there seems to be more spam on that than actual traffic. It seems like not much work is happening on DASL. I haven't seen any clients, for example, that use it. Is this a misimpression? Or is there just not enough interest in it? Or is it too hard to do? I'd like to be wrong about this, so please correct me if that's the case. Thanks. -ilya From w3c-dist-auth-request@w3.org Wed Dec 5 20:38:02 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24331 for ; Wed, 5 Dec 2001 20:38:02 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id UAA20535; Wed, 5 Dec 2001 20:37:04 -0500 (EST) Resent-Date: Wed, 5 Dec 2001 20:37:04 -0500 (EST) Resent-Message-Id: <200112060137.UAA20535@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id UAA20441 for ; Wed, 5 Dec 2001 20:36:36 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id UAA26870; Wed, 5 Dec 2001 20:36:35 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id RAA02255; Wed, 5 Dec 2001 17:36:39 -0800 (PST) From: "Jim Whitehead" To: "Ilya Kirnos" , Cc: Date: Wed, 5 Dec 2001 17:36:05 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <3C0EBA0C.E8533979@oracle.com> Subject: RE: DASL? Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5717 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Actually, I've been seeing a recent increase in interest for DASL -- there was a fairly substantial off-list thread last week. I've encouraged people to move discussion back on-list. > It seems like not much work is happening on DASL. I haven't seen any > clients, for example, that use it. Is this a misimpression? Or is > there just not enough interest in it? Or is it too hard to do? I'd > like to be wrong about this, so please correct me if that's the case. Unfortunately, there is currently limited client support (anyone out there have a DASL client?). The Xythos Storage Server supports DASL on the server side. I think this is more an indication of the lack of server support, and this, in turn, is due to the immaturity of the specification. I think there is a lot of interest in DASL, since it dramatically increases the value of DAV properties. - Jim From w3c-dist-auth-request@w3.org Wed Dec 5 23:06:15 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29849 for ; Wed, 5 Dec 2001 23:06:15 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id XAA02251; Wed, 5 Dec 2001 23:01:59 -0500 (EST) Resent-Date: Wed, 5 Dec 2001 23:01:59 -0500 (EST) Resent-Message-Id: <200112060401.XAA02251@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id XAA02195 for ; Wed, 5 Dec 2001 23:01:43 -0500 (EST) Received: from mail0.rawbw.com (mail0.rawbw.com [198.144.192.41]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id XAA08536; Wed, 5 Dec 2001 23:01:42 -0500 Received: from moose ([198.144.203.249]) by mail0.rawbw.com (8.11.3/8.11.3) with SMTP id fB641dD71021; Wed, 5 Dec 2001 20:01:39 -0800 (PST) (envelope-from lisa@xythos.com) From: "Lisa Dusseault" To: "Ilya Kirnos" , Cc: Date: Wed, 5 Dec 2001 19:59:33 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <3C0EBA0C.E8533979@oracle.com> Subject: RE: DASL? Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5718 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Hello, You're probably right about the clients; there are a few known servers that support all of DASL, but I don't know of any clients. (If there are any, please speak up.) I do know clients that support the DASL framework, but the search syntax is SQL rather than XML. Do you think there are any problems with the specification? Would you support it at some point if it started moving through the standards process again? Lisa > -----Original Message----- > From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Ilya Kirnos > Sent: Wednesday, December 05, 2001 4:22 PM > To: w3c-dist-auth@w3.org > Cc: www-webdav-dasl@w3.org > Subject: DASL? > > > Sorry for the cross-post -- I suppose this should be going to just the > DASL list, but there seems to be more spam on that than actual traffic. > > It seems like not much work is happening on DASL. I haven't seen any > clients, for example, that use it. Is this a misimpression? Or is > there just not enough interest in it? Or is it too hard to do? I'd > like to be wrong about this, so please correct me if that's the case. > > Thanks. > > -ilya From w3c-dist-auth-request@w3.org Thu Dec 6 19:09:41 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17634 for ; Thu, 6 Dec 2001 19:09:39 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id TAA24320; Thu, 6 Dec 2001 19:07:02 -0500 (EST) Resent-Date: Thu, 6 Dec 2001 19:07:02 -0500 (EST) Resent-Message-Id: <200112070007.TAA24320@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id TAA24258 for ; Thu, 6 Dec 2001 19:06:41 -0500 (EST) Received: from inet-mail3.oracle.com (inet-mail3.oracle.com [148.87.2.203]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id TAA16833; Thu, 6 Dec 2001 19:06:41 -0500 Received: from rgmgw5.us.oracle.com (rgmgw5.us.oracle.com [138.1.191.14]) by inet-mail3.oracle.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fB700Kv26634; Thu, 6 Dec 2001 16:00:20 -0800 (PST) Received: from oracle.com (ikirnos-pc.us.oracle.com [130.35.68.81]) by rgmgw5.us.oracle.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fB706XX24433; Thu, 6 Dec 2001 17:06:33 -0700 (MST) Message-ID: <3C1008B4.B0DE79F1@oracle.com> Date: Thu, 06 Dec 2001 16:09:24 -0800 From: Ilya Kirnos X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Lisa Dusseault CC: w3c-dist-auth@w3.org, www-webdav-dasl@w3.org References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: DASL? Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5719 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Lisa - > > Do you think there are any problems with the specification? I've only briefly looked at the spec, will let you know once I take a closer look. > Would you support it at some point if it started moving through the standards > process > again? We're definitely interested, but of course the lack of client support makes it somewhat academic right now. Hopefully that will change if/when the process starts moving forward. -ilya > > > Lisa > > > -----Original Message----- > > From: w3c-dist-auth-request@w3.org > > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Ilya Kirnos > > Sent: Wednesday, December 05, 2001 4:22 PM > > To: w3c-dist-auth@w3.org > > Cc: www-webdav-dasl@w3.org > > Subject: DASL? > > > > > > Sorry for the cross-post -- I suppose this should be going to just the > > DASL list, but there seems to be more spam on that than actual traffic. > > > > It seems like not much work is happening on DASL. I haven't seen any > > clients, for example, that use it. Is this a misimpression? Or is > > there just not enough interest in it? Or is it too hard to do? I'd > > like to be wrong about this, so please correct me if that's the case. > > > > Thanks. > > > > -ilya From w3c-dist-auth-request@w3.org Fri Dec 7 03:27:41 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16258 for ; Fri, 7 Dec 2001 03:27:41 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id DAA17964; Fri, 7 Dec 2001 03:26:23 -0500 (EST) Resent-Date: Fri, 7 Dec 2001 03:26:23 -0500 (EST) Resent-Message-Id: <200112070826.DAA17964@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id DAA17915 for ; Fri, 7 Dec 2001 03:25:55 -0500 (EST) Received: from io.mds.rmit.edu.au (io.mds.rmit.edu.au [131.170.70.10]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id DAA11506 for ; Fri, 7 Dec 2001 03:25:55 -0500 Received: by io.mds.rmit.edu.au (Postfix, from userid 301) id D5C8D49B6E; Fri, 7 Dec 2001 19:25:23 +1100 (EST) Date: Fri, 7 Dec 2001 19:25:23 +1100 From: Alan Kent To: WebDAV Message-ID: <20011207192523.F29734@io.mds.rmit.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Subject: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5720 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: I remember the recent question about DASL (was it this list?). I was wondering if part of the problem with DASL is the question of whether it addresses a need, or addresses it appropriately. We have a text searching engine that can do lots of funky searches etc. on the content of resources using fields (lets say dublin core elements). But this would be quite a different thing to querying on WebDAV properties. Hence I was interested to understand better the goal of DASL. Is it to be able to query WebDAV properities (and nothing else). Or was it intended to be broader and cover the harder problem of querying content as well? Just curious to understand the intended scope better before I jump in. I found a reference to a dasl requirements document (I have not looked it up yet). But is it still valid? I ask only because if its been a while and if no one has implemented it, is it because they have been busy, or because DASL has missed the mark in some way? Alan ps: I noticed that DASL seems to allow other queries to be plugged in. While this is good, for the above I am not after an answer like "you can do anything you like". I am more interested in "what do people like/want?" pps: I also noticed that the "basic" query langauge looked rather long when you got down to it - orderby, contains, like, three value logic... Convienient if you have an SQL engine around I guess. From w3c-dist-auth-request@w3.org Fri Dec 7 13:46:06 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27631 for ; Fri, 7 Dec 2001 13:46:05 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id NAA07300; Fri, 7 Dec 2001 13:42:54 -0500 (EST) Resent-Date: Fri, 7 Dec 2001 13:42:54 -0500 (EST) Resent-Message-Id: <200112071842.NAA07300@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id NAA07278 for ; Fri, 7 Dec 2001 13:42:47 -0500 (EST) Received: from server1.software-ag.de (server1.software-ag.de [193.26.194.2]) by tux.w3.org (8.9.3/8.9.3) with SMTP id NAA07927 for ; Fri, 7 Dec 2001 13:42:47 -0500 Message-ID: From: "Pill, Juergen" To: "'Alan Kent'" , WebDAV Date: Fri, 7 Dec 2001 19:42:32 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5721 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Hello Alan, You mentioned it, DASL define a mini query language to query property mostly and "server-defined" query languages, that can do want they want (the only thing those languages need is clients supporting those languages). I have the feeling, that also the mini query language should be extendable to define additional content operators. A query covering both content and properties is required to my understanding (again the question of available clients). An extendable mini query language would reduce the need to define an own "server-defined" query language and you get both content and property query in a more "standard" way. Best regards, juergen pill -----Original Message----- From: Alan Kent [mailto:ajk@mds.rmit.edu.au] Sent: Friday, December 07, 2001 09.25 AM To: WebDAV Subject: DASL - who wants to use it? (requirements spec?) I remember the recent question about DASL (was it this list?). I was wondering if part of the problem with DASL is the question of whether it addresses a need, or addresses it appropriately. We have a text searching engine that can do lots of funky searches etc. on the content of resources using fields (lets say dublin core elements). But this would be quite a different thing to querying on WebDAV properties. Hence I was interested to understand better the goal of DASL. Is it to be able to query WebDAV properities (and nothing else). Or was it intended to be broader and cover the harder problem of querying content as well? Just curious to understand the intended scope better before I jump in. I found a reference to a dasl requirements document (I have not looked it up yet). But is it still valid? I ask only because if its been a while and if no one has implemented it, is it because they have been busy, or because DASL has missed the mark in some way? Alan ps: I noticed that DASL seems to allow other queries to be plugged in. While this is good, for the above I am not after an answer like "you can do anything you like". I am more interested in "what do people like/want?" pps: I also noticed that the "basic" query langauge looked rather long when you got down to it - orderby, contains, like, three value logic... Convienient if you have an SQL engine around I guess. From w3c-dist-auth-request@w3.org Fri Dec 7 14:06:10 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28000 for ; Fri, 7 Dec 2001 14:06:10 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id OAA09985; Fri, 7 Dec 2001 14:05:11 -0500 (EST) Resent-Date: Fri, 7 Dec 2001 14:05:11 -0500 (EST) Resent-Message-Id: <200112071905.OAA09985@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id OAA09961 for ; Fri, 7 Dec 2001 14:05:01 -0500 (EST) Received: from lsmail.office.lightsurf.com (lsmail.office.lightsurf.com [204.30.31.25]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id OAA11400 for ; Fri, 7 Dec 2001 14:05:01 -0500 Received: from urchin (urchin.office.lightsurf.com [10.10.10.133]) by lsmail.office.lightsurf.com (Mirapoint) with SMTP id AAO19788; Fri, 7 Dec 2001 11:04:23 -0800 (PST) Reply-To: From: "Adam Freeman" To: "Pill, Juergen" , "'Alan Kent'" , "WebDAV" Date: Fri, 7 Dec 2001 11:04:55 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: Subject: RE: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5722 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Is that a rhetorical question? I would think anybody with a searchable website would want to use DASL... -----Original Message----- From: w3c-dist-auth-request@w3.org [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Pill, Juergen Sent: Friday, December 07, 2001 10:43 AM To: 'Alan Kent'; WebDAV Subject: RE: DASL - who wants to use it? (requirements spec?) Hello Alan, You mentioned it, DASL define a mini query language to query property mostly and "server-defined" query languages, that can do want they want (the only thing those languages need is clients supporting those languages). I have the feeling, that also the mini query language should be extendable to define additional content operators. A query covering both content and properties is required to my understanding (again the question of available clients). An extendable mini query language would reduce the need to define an own "server-defined" query language and you get both content and property query in a more "standard" way. Best regards, juergen pill -----Original Message----- From: Alan Kent [mailto:ajk@mds.rmit.edu.au] Sent: Friday, December 07, 2001 09.25 AM To: WebDAV Subject: DASL - who wants to use it? (requirements spec?) I remember the recent question about DASL (was it this list?). I was wondering if part of the problem with DASL is the question of whether it addresses a need, or addresses it appropriately. We have a text searching engine that can do lots of funky searches etc. on the content of resources using fields (lets say dublin core elements). But this would be quite a different thing to querying on WebDAV properties. Hence I was interested to understand better the goal of DASL. Is it to be able to query WebDAV properities (and nothing else). Or was it intended to be broader and cover the harder problem of querying content as well? Just curious to understand the intended scope better before I jump in. I found a reference to a dasl requirements document (I have not looked it up yet). But is it still valid? I ask only because if its been a while and if no one has implemented it, is it because they have been busy, or because DASL has missed the mark in some way? Alan ps: I noticed that DASL seems to allow other queries to be plugged in. While this is good, for the above I am not after an answer like "you can do anything you like". I am more interested in "what do people like/want?" pps: I also noticed that the "basic" query langauge looked rather long when you got down to it - orderby, contains, like, three value logic... Convienient if you have an SQL engine around I guess. From w3c-dist-auth-request@w3.org Fri Dec 7 15:03:20 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29009 for ; Fri, 7 Dec 2001 15:03:20 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id OAA13148; Fri, 7 Dec 2001 14:58:31 -0500 (EST) Resent-Date: Fri, 7 Dec 2001 14:58:31 -0500 (EST) Resent-Message-Id: <200112071958.OAA13148@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id OAA13123 for ; Fri, 7 Dec 2001 14:58:19 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id OAA19598 for ; Fri, 7 Dec 2001 14:58:19 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id LAA00675 for ; Fri, 7 Dec 2001 11:58:23 -0800 (PST) From: "Jim Whitehead" To: "WebDAV" Date: Fri, 7 Dec 2001 11:57:48 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: FW: WebDav and Java authorization Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5723 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Accidentally caught by the spam filter. - Jim -----Original Message----- From: Golder, Robert [mailto:RGolder@imaginecrm.com] Sent: Friday, December 07, 2001 1:17 AM To: w3c-dist-auth@w3.org Subject: [Moderator Action] WebDav and Java authorization Hello, I am trying to create a text file on a URL in a Java class. The directory requires username and password to access. How/where can I set these in the code? url = new URL("http://myserver/webdav/myFile.txt"); connection = (HttpURLConnection)aUrl.openConnection(); connection.setRequestMethod("PUT"); connection.setDoOutput(true); out = new PrintWriter(connection.getOutputStream()); out.println("Some Text"); out.close(); Currently I get a 401 authorization error. Thanks, Rob. o--Disclaimer--------------------------------------------------------------o Legally privileged/confidential information may be contained in this message. If you are not the intended addressee(s) of this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message, and notify us immediately by calling telephone 01753 219900. Please note that Imagin Europe Limited does not accept any responsibility for viruses and it is your responsibility to scan attachments (if any). Whilst Imagin Europe Limited scans both incoming and outgoing emails for viruses using current anti-virus software it is still possible for a virus to become attached to an email's attachment(s). Imagin Europe Limited is not liable for any damage caused or loss suffered by your failure to scan any attachments for viruses and deal with any such viruses appropriately. o-------------------------------------------------------------------------o From w3c-dist-auth-request@w3.org Fri Dec 7 17:48:56 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01856 for ; Fri, 7 Dec 2001 17:48:55 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id RAA20944; Fri, 7 Dec 2001 17:47:49 -0500 (EST) Resent-Date: Fri, 7 Dec 2001 17:47:49 -0500 (EST) Resent-Message-Id: <200112072247.RAA20944@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id RAA20896 for ; Fri, 7 Dec 2001 17:47:33 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA15082 for ; Fri, 7 Dec 2001 17:47:33 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id OAA10529; Fri, 7 Dec 2001 14:47:36 -0800 (PST) From: "Jim Whitehead" To: "'Alan Kent'" , "WebDAV" Date: Fri, 7 Dec 2001 14:47:00 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: RE: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5724 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit > Just curious to understand the intended scope better before > I jump in. I found a reference to a dasl requirements document > (I have not looked it up yet). But is it still valid? In the past, we produced both a Scenarios and a Requirements specification. I believe that both are still largely valid. The only significant new factor that has emerged since these documents were initially drafted is the XML Query effort. The scenarios and requirements documents can be found at: http://www.webdav.org/dasl/ - Jim From w3c-dist-auth-request@w3.org Fri Dec 7 20:30:50 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04167 for ; Fri, 7 Dec 2001 20:30:49 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id UAA28755; Fri, 7 Dec 2001 20:29:29 -0500 (EST) Resent-Date: Fri, 7 Dec 2001 20:29:29 -0500 (EST) Resent-Message-Id: <200112080129.UAA28755@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id UAA28733 for ; Fri, 7 Dec 2001 20:29:15 -0500 (EST) Received: from inet-mail4.oracle.com (inet-mail4.oracle.com [148.87.2.204]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id UAA02604 for ; Fri, 7 Dec 2001 20:29:15 -0500 Received: from rgmgw4.us.oracle.com (rgmgw4.us.oracle.com [138.1.191.13]) by inet-mail4.oracle.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fB81KCm15605; Fri, 7 Dec 2001 17:20:12 -0800 (PST) Received: from oracle.com (ikirnos-pc.us.oracle.com [130.35.68.81]) by rgmgw4.us.oracle.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fB81T9D15742; Fri, 7 Dec 2001 18:29:09 -0700 (MST) Message-ID: <3C116D8F.F9F44DD8@oracle.com> Date: Fri, 07 Dec 2001 17:31:59 -0800 From: Ilya Kirnos X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: afreeman@lightsurf.com CC: "Pill, Juergen" , "'Alan Kent'" , WebDAV References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5725 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit That's what I would think as well... Both properties and content searchability would be good. Adam Freeman wrote: > Is that a rhetorical question? I would think anybody with a searchable > website would want to use DASL... > > -----Original Message----- > From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Pill, Juergen > Sent: Friday, December 07, 2001 10:43 AM > To: 'Alan Kent'; WebDAV > Subject: RE: DASL - who wants to use it? (requirements spec?) > > Hello Alan, > > You mentioned it, DASL define a mini query language to query property mostly > and "server-defined" query languages, that can do want they want (the only > thing those languages need is clients supporting those languages). > > I have the feeling, that also the mini query language should be extendable > to define additional content operators. A query covering both content and > properties is required to my understanding (again the question of available > clients). > > An extendable mini query language would reduce the need to define an own > "server-defined" query language and you get both content and property query > in a more "standard" way. > > Best regards, > > juergen pill > > -----Original Message----- > From: Alan Kent [mailto:ajk@mds.rmit.edu.au] > Sent: Friday, December 07, 2001 09.25 AM > To: WebDAV > Subject: DASL - who wants to use it? (requirements spec?) > > I remember the recent question about DASL (was it this list?). > I was wondering if part of the problem with DASL is the question > of whether it addresses a need, or addresses it appropriately. > > We have a text searching engine that can do lots of funky searches > etc. on the content of resources using fields (lets say dublin > core elements). But this would be quite a different thing to > querying on WebDAV properties. > > Hence I was interested to understand better the goal of DASL. > Is it to be able to query WebDAV properities (and nothing else). > Or was it intended to be broader and cover the harder problem > of querying content as well? > > Just curious to understand the intended scope better before > I jump in. I found a reference to a dasl requirements document > (I have not looked it up yet). But is it still valid? I ask > only because if its been a while and if no one has implemented > it, is it because they have been busy, or because DASL has > missed the mark in some way? > > Alan > > ps: I noticed that DASL seems to allow other queries to be > plugged in. While this is good, for the above I am not after > an answer like "you can do anything you like". I am more > interested in "what do people like/want?" > > pps: I also noticed that the "basic" query langauge looked > rather long when you got down to it - orderby, contains, like, > three value logic... Convienient if you have an SQL engine around > I guess. From w3c-dist-auth-request@w3.org Mon Dec 10 13:52:21 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08664 for ; Mon, 10 Dec 2001 13:52:21 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id NAA13175; Mon, 10 Dec 2001 13:49:30 -0500 (EST) Resent-Date: Mon, 10 Dec 2001 13:49:30 -0500 (EST) Resent-Message-Id: <200112101849.NAA13175@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id NAA13124 for ; Mon, 10 Dec 2001 13:49:01 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id NAA08680 for ; Mon, 10 Dec 2001 13:49:01 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id KAA04607 for ; Mon, 10 Dec 2001 10:49:04 -0800 (PST) From: "Jim Whitehead" To: "WebDAV" Date: Mon, 10 Dec 2001 10:48:29 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01C18168.33F487D0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Subject: urn:schemas:calendar:contact !!! Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5726 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_0016_01C18168.33F487D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Accidentally caught by the spam filter. I have added to the accept2 list. - Jim -----Original Message----- From: Cristi Gafita [mailto:gcris80@hotmail.com] Sent: Saturday, December 08, 2001 2:40 AM To: w3c-dist-auth@w3.org Subject: [Moderator Action] urn:schemas:calendar:contact !!! Hi, I try to recover the contacts from an appointment, how can I do that ? I become just the response: HTTP/1.1 404 Resource Not Found. I make a request to an Exchange2000 server like this: PROPFIND /exchange/admi/Calendar/{6D83D401-155F-460D-AF4F-B74C546A9C48}.EML HTTP/1.1 Host: 192.165.5.17:80 Accept-Language: en-us Accept: text/xml Authorization: Basic YWRtaW5ldXI6RERERVZYWA== Connection: close Content-Type: text/xml; charset="utf-8" Content-Length: 140 Can somebody help me ? Thanks -Chris ------=_NextPart_000_0016_01C18168.33F487D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Accidentally caught by the spam filter. I = have added=20 <gcris80@hotmail.com> = to the=20 accept2 list.
 
-=20 Jim
-----Original Message-----
From: Cristi Gafita=20 [mailto:gcris80@hotmail.com]
Sent: Saturday, December 08, 2001 = 2:40=20 AM
To: w3c-dist-auth@w3.org
Subject: [Moderator = Action]=20 urn:schemas:calendar:contact !!!

Hi,
I try to recover the contacts from an = appointment,=20 how can I do that ?
I become just the response: HTTP/1.1 = 404 Resource=20 Not Found.
I make a request to an Exchange2000 = server like=20 this:
 
PROPFIND=20 /exchange/admi/Calendar/{6D83D401-155F-460D-AF4F-B74C546A9C48}.EML=20 HTTP/1.1
Host: 192.165.5.17:80
Accept-Language: en-us
Accept:=20 text/xml
Authorization: Basic = YWRtaW5ldXI6RERERVZYWA=3D=3D
Connection:=20 close
Content-Type: text/xml; charset=3D"utf-8"
Content-Length:=20 140
 
<?xml version=3D"1.0" = encoding=3D"utf-8"=20 ?><D:propfind xmlns:D=3D"DAV:"><D:prop=20 xmlns:e=3D"urn:schemas:calendar:"><e:contact/></D:prop><= ;/D:propfind>
 
Can somebody help me ?
 
Thanks
 
-Chris
------=_NextPart_000_0016_01C18168.33F487D0-- From w3c-dist-auth-request@w3.org Tue Dec 11 19:20:46 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28280 for ; Tue, 11 Dec 2001 19:20:46 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id TAA20919; Tue, 11 Dec 2001 19:15:39 -0500 (EST) Resent-Date: Tue, 11 Dec 2001 19:15:39 -0500 (EST) Resent-Message-Id: <200112120015.TAA20919@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id TAA20845 for ; Tue, 11 Dec 2001 19:15:21 -0500 (EST) Received: from cats.ucsc.edu (rumpleteazer.ucsc.edu [128.114.129.45]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id TAA04739 for ; Tue, 11 Dec 2001 19:15:22 -0500 Received: from Tycho (dhcp-63-177.cse.ucsc.edu [128.114.63.177]) by cats.ucsc.edu (8.9.3/8.8.4.cats-athena) with SMTP id QAA28124 for ; Tue, 11 Dec 2001 16:15:26 -0800 (PST) From: "Jim Whitehead" To: "WebDAV" Date: Tue, 11 Dec 2001 16:14:48 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: Re: Using WebDav Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5727 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Accidentally caught by the spam filter. I have added to the accept2 list. - Jim -----Original Message----- From: FUKA, CHRISTOPHER (SBCSI) [mailto:cf1636@sbc.com] Sent: Tuesday, December 11, 2001 3:51 PM To: 'w3c-dist-auth@w3.org' Subject: [Moderator Action] Re: Using WebDav My company just upgraded my web servers from Windows NT to Windows 2000 with IIS 5.0. I was using the Posting Acceptor to upload documents to my intranet site. All the documentation that I have read so far has said not to use the Posting Acceptor for Windows 2000 but to use this WebDAV. My question is really simple. HOW??? I need to have the ability to have users go to my site and upload documents to the site. Is this something that WebDAV can do? I have no idea where to begin with this. Help Please. Chris Fuka Web Developer Phone: 925-468-5396 Pager:877-289-1136 From w3c-dist-auth-request@w3.org Thu Dec 13 02:31:39 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15083 for ; Thu, 13 Dec 2001 02:31:38 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id CAA18507; Thu, 13 Dec 2001 02:30:22 -0500 (EST) Resent-Date: Thu, 13 Dec 2001 02:30:22 -0500 (EST) Resent-Message-Id: <200112130730.CAA18507@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id CAA18455 for ; Thu, 13 Dec 2001 02:29:44 -0500 (EST) Received: from sus-ma1it00.rational.com (ext-37184.rational.com [192.229.37.184]) by tux.w3.org (8.9.3/8.9.3) with SMTP id CAA24040 for ; Thu, 13 Dec 2001 02:29:45 -0500 Received: from 192.168.215.70 by sus-ma1it00.rational.com (InterScan E-Mail VirusWall NT); Thu, 13 Dec 2001 02:29:14 -0500 Received: by sus-ma1it00.rational.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Dec 2001 02:29:14 -0500 Message-ID: <3906C56A7BD1F54593344C05BD1374B1052AD4AB@SUS-MA1IT01> From: "Clemm, Geoff" To: w3c-dist-auth@w3.org Date: Thu, 13 Dec 2001 02:29:04 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: More detail on the DAV:bindings property... Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5729 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: From: Peter Raymond [mailto:Peter.Raymond@merant.com] In my earlier e-mail I mentioned that I was unsure about the contents of the DAV:bindings property. Here is some more detail about why I think it is unclear, also find attached some PowerPoint slides which I used to try to understand the bindings property. I guess there are two things in the text that mislead me: 1) Section 13.1 says that the property "contains a complete list of all bindings to that resource", but also says it is necessary to select one URI mapping for a collection. It seems to contradict itself, it is not complete because it only contains one URI mapping for a collection. A binding is an named association between a collection and a resource, where the "name" is a URI segement. You perhaps are confusing a "binding" with a "mapping" (where a "mapping" is an association between a URL and a resource). 2) It also says you should preferably use the mapping in the request-URI of the BIND request. But I am unclear as to which BIND request. The BIND request that created the binding named "bar" from C1 to R2. It is a PROPFIND request which was issued to find the DAV:bindings property, not a BIND request. Yes, but that is not relevant for naming all the bindings (since the collections containing the bindings are in general unrelated to the request-URL of the PROPFIND request). Perhaps it means the last BIND request for that collection or perhaps it means the first bind request for the resource in the collection? No, the BIND request that created the binding that is being identified. So using the example in Figure 1 of the bindings document you have the URI paths: /coll1/bar /coll2/bar /coll3/foo /coll1/ and /coll2/ are the same collection resource but all these URIs point to the same resource (R2). OK. Imagine you make a PROPFIND request on /coll2/bar, asking for the DAV:bindings property...should you get: /coll1/ bar /coll2/ bar /coll3/ foo That is a "complete" list of all bindings for resource R2... /coll1/bar and /coll2/bar both identify the same binding (from C1 to R2), so you shouldn't have both in the dav:bindings list. BUT section 13.1 says you should pick only one URI for a given collection, so perhaps it should return: /coll2/ bar /coll3/ foo Because /coll1/ and /coll2/ are the same collection I have picked just one URI mapping for that collection... Yes. in this case I used the URI mapping from the PROPFIND request. The URI mapping from the PROPFIND request is not relevant. What is relevant is whether the binding was created by BIND /coll3/foo Destination: http://host.com/coll1/bar or BIND /coll3/foo Destination: http://host.com/coll2/bar In the first case, http://host.com/coll1/bar should be in the DAV:bindings property for R2, while in the second case, http://host.com/coll2/bar should be in the DAV:bindings property for R2. Cheers, Geoff From w3c-dist-auth-request@w3.org Thu Dec 13 02:31:44 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15106 for ; Thu, 13 Dec 2001 02:31:44 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id CAA18489; Thu, 13 Dec 2001 02:30:04 -0500 (EST) Resent-Date: Thu, 13 Dec 2001 02:30:04 -0500 (EST) Resent-Message-Id: <200112130730.CAA18489@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id CAA18416 for ; Thu, 13 Dec 2001 02:29:35 -0500 (EST) Received: from sus-ma1it00.rational.com (ext-37184.rational.com [192.229.37.184]) by tux.w3.org (8.9.3/8.9.3) with SMTP id CAA24036 for ; Thu, 13 Dec 2001 02:29:35 -0500 Received: from 192.168.215.70 by sus-ma1it00.rational.com (InterScan E-Mail VirusWall NT); Thu, 13 Dec 2001 02:29:04 -0500 Received: by sus-ma1it00.rational.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Dec 2001 02:29:04 -0500 Message-ID: <3906C56A7BD1F54593344C05BD1374B1052AD4AA@SUS-MA1IT01> From: "Clemm, Geoff" To: w3c-dist-auth@w3.org Date: Thu, 13 Dec 2001 02:29:02 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Issues/questions about the bindings protocol specification... Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5728 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: From: Peter Raymond [mailto:Peter.Raymond@merant.com] 1) Section 9 says that methods MUST produce the same results when submitted on different bindings to the same resource. I disagree, if you issue a PROPFIND request on /coll1/bar the href returned would be /coll1/bar, if you issue the same PROPFIND request on /coll2/bar (which is bound to the same resource) the href returned would be /coll2/bar. The responses would not be the same. I am sure there could be other examples of this. Yeah, trying to define the semantics of a "binding" is tricky. I'd have to look up in our notes whether we came up with something better, or just didn't try. We might just need to give a method by method definition of the semantics, and then let folks infer from that how they should act for future extensions. 2) We found the definition of the DAV:bindings property in section 13.1 very confusing. It would be good to show an example of this property, an interesting example would be the DAV:bindings on resource R2 from Figure 1. I will send a separate e-mail on this issue. OK. 3) Section 15 describes capability discovery and shows the use of a header called Public. I cannot find a definition of this header in RFC2518 or RFC2616 (there is a Cache-Control public directive but no Public header). In what specification is this header defined? Maybe I just missed it. This is a deprecated header from an earlier version of the HTTP-1.1 draft (rfc 2068). The reference should be removed. 4) Also on the subject of section 15, it seems we have many ways of finding out what capabilities a server or a resource has...Allow header, Public header, DAV header, DAV:supported-method-set property (in DeltaV). I find this confusing, and I know in the various WebDAV groups there has been some discussion of these and the differences between them, I think they should be defined clearly and consistently in all the WebDAV related specifications. The Public header is gone, but the rest remain. We have defined DAV:supported-method-set to be the same as Allow, so it really is DAV header, combined with the DAV:supported-xxx properties. And we hope to add these properties to the next 2518 draft, so that they are generally available, and not just in DeltaV. 5) Section 18 there is a missing space in the last sentence (after the 507 code). Yup. 6) Is there anyone looking at how bindings affect the other protocols, for example have we looked at how DeltaV features (like Baseline etc) are affected by bindings? I tried to keep bindings in mind for all of the of the DeltaV features. If you notice anything that might be a problem, please let me know. BTW...are there any server vendors out there that implement or are thinking of implementing the BIND method? Yes. Similarly are any clients using it? Not yet, as far as I know. Cheers, Geoff From w3c-dist-auth-request@w3.org Mon Dec 17 13:49:11 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14670 for ; Mon, 17 Dec 2001 13:49:10 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id NAA27235; Mon, 17 Dec 2001 13:40:26 -0500 (EST) Resent-Date: Mon, 17 Dec 2001 13:40:26 -0500 (EST) Resent-Message-Id: <200112171840.NAA27235@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id NAA27137 for ; Mon, 17 Dec 2001 13:40:05 -0500 (EST) Received: from front1.mail.megapathdsl.net (front1.mail.megapathdsl.net [66.80.60.31]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id NAA09435 for ; Mon, 17 Dec 2001 13:40:05 -0500 Received: from [216.36.111.249] (HELO moose) by front1.mail.megapathdsl.net (CommuniGate Pro SMTP 3.4.8a) with SMTP id 14129019; Mon, 17 Dec 2001 10:37:19 -0800 From: "Lisa Dusseault" To: "Alan Kent" , "WebDAV" Date: Mon, 17 Dec 2001 10:37:33 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-reply-to: <20011207192523.F29734@io.mds.rmit.edu.au> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: RE: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5730 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Not sure if anybody ever answered your basic question about whether DASL addresses content querying. It does. Here is the query fragment that would search the body of a document: Peter Forsberg This is similar to the property queries, but it does not name a property, therefore it's the content that must be searched for the string. Note that it's possible to do exact string matching ("Peter Forsberg") and string-by-string matching ("Peter" and "Forsberg", not necessarily together). Section 5.13.1 of DASL shows both examples. Lisa > -----Original Message----- > From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Alan Kent > Sent: Friday, December 07, 2001 12:25 AM > To: WebDAV > Subject: DASL - who wants to use it? (requirements spec?) > > > I remember the recent question about DASL (was it this list?). > I was wondering if part of the problem with DASL is the question > of whether it addresses a need, or addresses it appropriately. > > We have a text searching engine that can do lots of funky searches > etc. on the content of resources using fields (lets say dublin > core elements). But this would be quite a different thing to > querying on WebDAV properties. > > Hence I was interested to understand better the goal of DASL. > Is it to be able to query WebDAV properities (and nothing else). > Or was it intended to be broader and cover the harder problem > of querying content as well? > > Just curious to understand the intended scope better before > I jump in. I found a reference to a dasl requirements document > (I have not looked it up yet). But is it still valid? I ask > only because if its been a while and if no one has implemented > it, is it because they have been busy, or because DASL has > missed the mark in some way? > > Alan > > ps: I noticed that DASL seems to allow other queries to be > plugged in. While this is good, for the above I am not after > an answer like "you can do anything you like". I am more > interested in "what do people like/want?" > > pps: I also noticed that the "basic" query langauge looked > rather long when you got down to it - orderby, contains, like, > three value logic... Convienient if you have an SQL engine around > I guess. From w3c-dist-auth-request@w3.org Mon Dec 17 14:30:01 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15713 for ; Mon, 17 Dec 2001 14:30:01 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id OAA01235; Mon, 17 Dec 2001 14:22:12 -0500 (EST) Resent-Date: Mon, 17 Dec 2001 14:22:12 -0500 (EST) Resent-Message-Id: <200112171922.OAA01235@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id OAA01207 for ; Mon, 17 Dec 2001 14:22:05 -0500 (EST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by tux.w3.org (8.9.3/8.9.3) with SMTP id OAA16727 for ; Mon, 17 Dec 2001 14:22:05 -0500 Received: (qmail 29234 invoked by uid 0); 17 Dec 2001 19:22:04 -0000 Received: from pd9e513a9.dip.t-dialin.net (HELO lisa) (217.229.19.169) by mail.gmx.net (mp009-rz3) with SMTP; 17 Dec 2001 19:22:04 -0000 From: "Julian Reschke" To: "Lisa Dusseault" , "Alan Kent" , "WebDAV" Date: Mon, 17 Dec 2001 20:22:02 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: RE: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5731 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit > From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Lisa Dusseault > Sent: Monday, December 17, 2001 7:38 PM > To: Alan Kent; WebDAV > Subject: RE: DASL - who wants to use it? (requirements spec?) > > > Not sure if anybody ever answered your basic question about whether DASL > addresses content querying. It does. > > Here is the query fragment that would search the body of a document: > > Peter Forsberg > > > This is similar to the property queries, but it does not name a property, > therefore it's the content that must be searched for the string. > > Note that it's possible to do exact string matching ("Peter Forsberg") and > string-by-string matching ("Peter" and "Forsberg", not necessarily > together). Section 5.13.1 of DASL shows both examples. > > Lisa Lisa, which version are you referring to? According to [1], - "contains" is an optional operator (so cou can't rely on it being supported) - the method of matching is only loosely defined; in particular you can't rely on it doing "exact" matching. [1] From w3c-dist-auth-request@w3.org Mon Dec 17 21:14:20 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23369 for ; Mon, 17 Dec 2001 21:14:20 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id TAA00015; Mon, 17 Dec 2001 19:32:10 -0500 (EST) Resent-Date: Mon, 17 Dec 2001 19:32:10 -0500 (EST) Resent-Message-Id: <200112180032.TAA00015@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id TAA29892 for ; Mon, 17 Dec 2001 19:31:28 -0500 (EST) Received: from front1.mail.megapathdsl.net (front1.mail.megapathdsl.net [66.80.60.31]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id TAA01749 for ; Mon, 17 Dec 2001 19:31:28 -0500 Received: from [216.36.111.249] (HELO moose) by front1.mail.megapathdsl.net (CommuniGate Pro SMTP 3.4.8a) with SMTP id 14180878; Mon, 17 Dec 2001 16:28:46 -0800 From: "Lisa Dusseault" To: "Julian Reschke" , "Alan Kent" , "WebDAV" Date: Mon, 17 Dec 2001 16:28:59 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: Subject: RE: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5732 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit > - "contains" is an optional operator (so cou can't rely on it being > supported) true > - the method of matching is only loosely defined; in particular you can't > rely on it doing "exact" matching. true. > [1] > I was looking at the same draft. But I think Alan wanted to know if DASL addressed body content searching at all, which it does. If the server supports it, the client can use it (as usual). lisa From w3c-dist-auth-request@w3.org Tue Dec 18 01:07:46 2001 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27990 for ; Tue, 18 Dec 2001 01:07:46 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id AAA11306; Tue, 18 Dec 2001 00:54:51 -0500 (EST) Resent-Date: Tue, 18 Dec 2001 00:54:51 -0500 (EST) Resent-Message-Id: <200112180554.AAA11306@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id AAA11147 for ; Tue, 18 Dec 2001 00:53:55 -0500 (EST) Received: from io.mds.rmit.edu.au (io.mds.rmit.edu.au [131.170.70.10]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id AAA15340 for ; Tue, 18 Dec 2001 00:53:54 -0500 Received: by io.mds.rmit.edu.au (Postfix, from userid 301) id 4206649B6E; Tue, 18 Dec 2001 16:53:22 +1100 (EST) Date: Tue, 18 Dec 2001 16:53:21 +1100 From: Alan Kent To: WebDAV Message-ID: <20011218165321.I24222@io.mds.rmit.edu.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Lisa Dusseault on Mon, Dec 17, 2001 at 04:28:59PM -0800 Subject: Re: DASL - who wants to use it? (requirements spec?) Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/5733 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: On Mon, Dec 17, 2001 at 04:28:59PM -0800, Lisa Dusseault wrote: > I was looking at the same draft. But I think Alan wanted to know if DASL > addressed body content searching at all, which it does. If the server > supports it, the client can use it (as usual). > > lisa This may be a bit of a can of worms, but is there any interest in using the structure of content in queries? For example, being able to query on the content's "Title" or "Author". I am thinking of Dublin Core metadata sort of approach - not XPath or XML Query since the content can be anything (PDF, GIF, etc). Allowing something like Dublin Core would allow a level of structure to be imposed. If this was considered useful, would the better approach be to define additional live properites that were automatically extracted from the content (hence its really just querying on properties after all, not content itself), or to allow querying on properties or content. I guess I am sort of asking should return the Dublin Core like elements too? (It could be expensive to compute). I do a fair bit of work with a search and retrieval protocol, Z39.50. It is based on the Dublin Core idea of separating your access points for searching from the physical representation of the data. It allows querying on "Title" as an abstract concept, without requiring that it be possible to return a "Title" out from the data. It takes a different view on query capabilities too - it says you have terms that can have constraints applied. Specifying a property name to search within is a constraint. Specifying > (greater than) is a constraint. It does not use 3 value logic. It more says 'return all records that contain some data that match the condition'. WebDAV might not have the same problem of repeating values as properites have only one value. Personally I would like to search on parts of the content using Dublin Core (or other) metadata standards. Should I do this using WebDAV properties bound to parts of the content of the resource? Any other ideas? Thanks Alan ps: I am not likely to do this any time soon. Just thinking about the future.