DAV:resourceid vs. DAV:versioned-resource-id

From: Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Date: Thu, Jan 20 2000

Next message: Eric Sedlar: "Re: "stable" href's"

Previous message: Geoffrey M. Clemm: ""stable" href's"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Other mail archives: [this mailing list] [other W3C mailing lists]
Mail actions: [ respond to this message ] [ mail a new topic ]

Date: Thu, 20 Jan 2000 23:08:15 -0500
Message-Id: <10001210408.AA26154@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: DAV:resourceid vs. DAV:versioned-resource-id

I propose that we just use require that a versioned resource
have a DAV:resourceid (as defined in the BINDING protocol),
rather than introducing a new DAV:versioned-resource-id.

I further propose (as suggested by someone earlier) that we
require that the DAV:resourceid of a working resource or revision
be the DAV:resourceid of its versioned resource.

Comments?

Cheers,
Geoff

Next message: Eric Sedlar: "Re: "stable" href's"
Previous message: Geoffrey M. Clemm: ""stable" href's"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Other mail archives: [this mailing list] [other W3C mailing lists]
Mail actions: [ respond to this message ] [ mail a new topic ]