Re: Minor nit on v2.3 of webdav versioning spec
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Fri, 19 Nov 1999 08:49:16 -0500
Date: Fri, 19 Nov 1999 08:49:16 -0500
Message-Id: <9911191349.AA06412@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <00d001bf3255$1811c550$79442382@us.oracle.com>
Subject: Re: Minor nit on v2.3 of webdav versioning spec
From: "Eric Sedlar" <esedlar@us.oracle.com>
In Section 2.2.1 Boolean values
You specify that booleans should be either "0" or "1". The XML =
Schema--Datatypes draft specifies that booleans will be either "true" or =
"false" (case sensitive). Why not use those values?
Just to make life complicated, RFC-2518 (WebDAV) defines booleans as
"F" and "T". The latest version of the versioning spec (deltav-01)
uses "F" and "T" to be consistent with RFC-2518.
It is probably more important that versioning be consistent with 2518,
so we'll probably stick with "F" and "T" unless 2518 changes.
At some point we may just want to weasel out, and define false to be
any of:
"f" "F" "0" "false" "FALSE" "False"
and true to be any of:
"t" "T" "1" "true" "TRUE" "True"
Cheers,
Geoff