W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2000

RE: Moving Labels Back to Core?

From: Dennis E. Hamilton <infonuovo@email.com>
Date: Wed, 18 Oct 2000 13:38:56 -0700
To: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>, <ietf-dav-versioning@w3.org>
Message-ID: <NDBBKEGCNONMNKGDINPFEELGEOAA.infonuovo@email.com>
I would say that, so long as label support is optional, and they don't
depend on any non-core mechanism, that the core is a good place to put them.

Mostly I see it encouraging developers to notice them and consider their
support rather than come up with substitutes at the core level that don't
scale into advanced.

It may be a small thing, and I recommend it anyhow.

-- Dennis

AIIM DMware Technical Coordinator
AIIM DMware http://www.infonuovo.com/dmware
ODMA Support http://www.infonuovo.com/odma
Dennis E. Hamilton
tel. +1-206-779-9430 (gsm)
fax. +1-425-793-0283

-----Original Message-----
From: ietf-dav-versioning-request@w3.org
[mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Geoffrey M.
Sent: Wednesday, October 18, 2000 09:07
To: ietf-dav-versioning@w3.org
Subject: deltav-10.2 now available


Changes since deltav-10:

- Moved version selector DAV:predecessor-set property to core. (Boris)
- Made label support optional. (Lisa)
- Removed Workspace header (Geoff)
- Added DAV:must-not-be-checked-out precondition for LABEL (John)
- Only require Multi-Status if there was an error in a Depth operation
  (e.g. LABEL and SET-TARGET). (John)
- Got rid of "parent workspace" for MKWORKSPACE (Tim/Geoff)
- Added DAV:no-checkout argument to MERGE (Tim)
- Fixed BASELINE-CONTROL so that baseline (not baseline history)
  is the argument (Tim).

Outstanding Issues:

- Should labels be moved back to core?

Received on Wednesday, 18 October 2000 16:35:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:45 UTC