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

RE: use of attribute to qualify property value

From: Chris Kaler (Exchange) <ckaler@Exchange.Microsoft.com>
Date: Mon, 24 May 1999 13:54:29 -0700
Message-ID: <FD7A762E588AD211A7BC00805FFEA54B01C2980B@HYDRANT>
To: WEBDAV WG <w3c-dist-auth@w3.org>

I disagree that DASL is the right approach.  The different "types" of
history are really about semantic interpretation by the store.  I don't
believe this can be expressed in DASL short of using an attribute. 

I also don't believe that content negotiation is viable.  What if the report
was a document that it, itself, could be subject to content negotiation.

It seems, to me at least, that a property attirbute or multiple properties
is still the best way to go.  The later means an "explosion" of properties
(n * m).

Chris

-----Original Message-----
From: Jim Whitehead [mailto:ejw@ics.uci.edu]
Sent: Monday, May 24, 1999 11:29 AM
To: WEBDAV WG
Subject: RE: use of attribute to qualify property value


Caught by the spam filter.

- Jim

-----Original Message-----
From: Geoffrey Clemm [mailto:geoffrey.clemm@rational.com]
Sent: Friday, May 21, 1999 7:50 PM
To: ietf-dav-versioning@w3.org; w3c-dist-auth@w3.org
Subject: [Moderator Action] RE: use of attribute to qualify property
value


At 09:57 AM 5/20/99 -0700, Chris Kaler (Exchange) wrote:
>The reason we had this was because there are different "types" of histories
>that are available and different ways to "view" the history.  We modeled
>this (in this draft) as a property, and rather than having "n*m"
properties,
>we used a qualifier.

I agree that there are different ways to view the history.  But I believe
that a general query mechanism such as DASL would be a better
way to provide these reports, rather than a set of predefined property
types and attributes.

Until the DASL query mechanisms are defined, we get at least some
level of report customizability through standard PROPFIND mechanisms.

>I, personally, don't think that modeling history as a resource is viable
>since there are several different ways that I want to view the history.
>History information should be an XML "report".

The results of PROPFIND is an XML report.  It has the advantage of
being understood by all browsers that implement PROPFIND, rather than
being limited to just those browsers that understand the DeltaV extensions.

Cheers,
Geoff
Received on Monday, 24 May 1999 16:54:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:49 GMT