W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2001

Re: DASL - who wants to use it? (requirements spec?)

From: Ilya Kirnos <ilya.kirnos@oracle.com>
Date: Fri, 07 Dec 2001 17:31:59 -0800
Message-ID: <3C116D8F.F9F44DD8@oracle.com>
To: afreeman@lightsurf.com
CC: "Pill, Juergen" <Juergen.Pill@softwareag.com>, "'Alan Kent'" <ajk@mds.rmit.edu.au>, WebDAV <w3c-dist-auth@w3.org>
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.
Received on Friday, 7 December 2001 20:29:16 UTC

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