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

AW: Removing the DAV:activity and DAV:version-history and DAV :baseline resource type values

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Wed, 6 Jun 2001 12:27:18 +0200
To: "DeltaV \(E-mail\)" <ietf-dav-versioning@w3.org>
Message-ID: <NDBBKJABLJNMLJELONBKAENPCNAA.stefan.eissing@greenbytes.de>


> [mailto:ietf-dav-versioning-request@w3.org]Im Auftrag von
> Tim_Ellison@uk.ibm.com
> [...]
>
> My view of the world...
>
> Here's the list of elements that could appear in a DAV:resourcetype.  Some
> of these can be combined to provide a really meaningful experience for the
> client.  Obviously, some combinations are invalid.
>      <DAV:checked-in/>
>      <DAV:checked-out/>
>      <DAV:collection/>
>      <DAV:working-resource/>
>      <DAV:version-controlled-resource/>
>      <DAV:version/>
>      <DAV:version-history/>
>      <DAV:workspace/>
>      <DAV:version-controlled-configuration/>
>      <DAV:baseline/>
>      <DAV:activity/>
>

What is your rationale for checked-in/out in the type? I think
I have missed something in the spec, since it feels like a
property to me.

> So,
> <DAV:resourcetype>
>      <DAV:activity/>
> </DAV:resourcetype
>
> would be good, that is, not surprisingly, an activity resource.
>
> <DAV:resourcetype>
>      <DAV:checked-out/>
>      <DAV:version-controlled-resource/>
>      <DAV:collection/>
>      <DAV:workspace/>
> </DAV:resourcetype>
>
> would be good too, it is a checked-out, version-controlled resource for a
> workspace collection.  And so on.
>
> Tim
>
>
Received on Wednesday, 6 June 2001 06:28:21 GMT

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