Re: DAV:revision-resourcetype

From: Eric Sedlar (esedlar@us.oracle.com)
Date: Fri, Jan 21 2000

  • Next message: Geoffrey M. Clemm: "Re: DAV:revision-resourcetype"

    Message-ID: <003c01bf6440$5f4aded0$79442382@us.oracle.com>
    From: "Eric Sedlar" <esedlar@us.oracle.com>
    To: "Tim Ellison OTT" <Tim_Ellison@oti.com>, "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>, "ietf-dav-versioning" <ietf-dav-versioning@w3.org>
    Date: Fri, 21 Jan 2000 10:50:22 -0800
    Subject: Re: DAV:revision-resourcetype
    
    Only if you allow transmutation of types, e.g. version 1 of this resource
    was a "quote" and version 2 is a "purchase order", or some such.  In
    general, I think allowing transmutation is a bad idea, so we shouldn't have
    a revision-resourcetype different than resourcetype, ever.
    
    --Eric
    
    ----- Original Message -----
    From: Tim Ellison OTT <Tim_Ellison@oti.com>
    To: Geoffrey M. Clemm <geoffrey.clemm@rational.com>; ietf-dav-versioning
    <ietf-dav-versioning@w3.org>
    Sent: Friday, January 21, 2000 8:00 AM
    Subject: RE: DAV:revision-resourcetype
    
    
    >
    > In what instances would you expect DAV:resourcetype to be different to
    > DAV:revision-resourcetype ?
    >
    > Tim
    >  ----------
    > >From: Geoffrey M. Clemm
    > >To: ietf-dav-versioning
    > >Subject: DAV:revision-resourcetype
    > >Date: Thursday, January 20, 2000 10:48PM
    > >
    > ><<File Attachment: HEADER.TXT>>
    > >
    > >Most versioning systems require that you tell it what kind of
    > >versioned resource you want to create, when you create one.
    > >This means that to use MKRESOURCE, we need to be able to specify,
    > >on creation of a versioned resource, the DAV:resourcetype of the
    > >revisions of that versioned resource.
    > >
    > >I propose that we introduce a DAV:revision-resourcetype property
    > >on a versioned resource in order to do so.
    > >
    > >Comments?
    > >
    > >Cheers,
    > >Geoff
    > >
    > >
    >
    >