W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2001

RE: Removing the DAV:activity and DAV:version-history and DAV:bas eline resource type values

From: Clemm, Geoff <gclemm@rational.com>
Date: Thu, 21 Jun 2001 14:05:53 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B1018E24BB@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
For those (likely very few) new resource types that have exactly
the same properties and methods as an existing resource type, you would
be free to add an additional value to the DAV:resourcetype property.
But since none of the resources introduced by the versioning protocol
have this characteristic (i.e. they all have a set of new properties
or methods that they support), we needn't add new resource type values
in the DeltaV protocol.

Cheers,
Geoff 


-----Original Message-----
From: Jim Amsden [mailto:jamsden@us.ibm.com]
Sent: Thursday, June 21, 2001 10:16 AM
To: ietf-dav-versioning@w3.org
Subject: RE: Removing the DAV:activity and DAV:version-history and
DAV:bas eline resource type values


I agree with Geoff that *most* new resource types do result in at least 
one new method and/or property. But this is fundamentally a poor thing to 
depend on as we know there can be (and therefore probably will be) 
subtypes that don't add new methods or properties, but only override 
behavior of their superclass. By not resolving the resource type issue to 
support such situations, we may be just putting the problem off in such a 
way that it will need to be solved in some very different manner by some 
future protocol extension. This is what keeps nagging at me.
Received on Thursday, 21 June 2001 14:00:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:41 GMT