L2/07-135

Date: Thu, 26 Apr 2007
From: Mark Davis
Subject: Binary/Trinary property values

Please add to doc registry and agenda.

As per actions, PropertyValueAliases now has the binary properties in it,
with their values. For example,

# Math (Math)

Math; N        ; No                               ;
F                                ; False
Math; Y        ; Yes                              ;
T                                ; True

The primary values are N/Y for consistency, but F/T are added as alternates
since these are widely treated as booleans. The latter was not directed as a
part of the UTC action, so the UTC should decide whether it wants it.

Currently the QC properties have been left alone, such as:

# NFC_Quick_Check (NFC_QC)

NFC_QC; M      ; Maybe
NFC_QC; N      ; No
NFC_QC; Y      ; Yes

# NFD_Quick_Check (NFD_QC)

NFD_QC; N      ; No
NFD_QC; Y      ; Yes

# NFKC_Quick_Check (NFKC_QC)

NFKC_QC; M     ; Maybe
NFKC_QC; N     ; No
NFKC_QC; Y     ; Yes

# NFKD_Quick_Check (NFKD_QC)

NFKD_QC; N     ; No
NFKD_QC; Y     ; Yes

We have a few options.

0. Leave as is.
1. Add True/False as alternates for Yes/No to the binary QC properties
2. Add True/False as alternates for Yes/No to the binary and trinary QC
properties
3. Add True/False as alternates for Yes/No to the binary and trinary QC
properties, and Undetermined as an alternate for Maybe for the trinary ones.

I have a slight preference for #3.

-- 
Mark