Re: [VCARDDAV] two component GENDER

Peter Saint-Andre <stpeter@stpeter.im> Thu, 16 December 2010 15:30 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: vcarddav@core3.amsl.com
Delivered-To: vcarddav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34E8A3A67A3 for <vcarddav@core3.amsl.com>; Thu, 16 Dec 2010 07:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.41
X-Spam-Level:
X-Spam-Status: No, score=-101.41 tagged_above=-999 required=5 tests=[AWL=-0.911, BAYES_00=-2.599, J_CHICKENPOX_61=0.6, J_CHICKENPOX_64=0.6, J_CHICKENPOX_65=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5B1Uy-kYtn+3 for <vcarddav@core3.amsl.com>; Thu, 16 Dec 2010 07:30:30 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id F0EC93A68DB for <vcarddav@ietf.org>; Thu, 16 Dec 2010 07:30:29 -0800 (PST)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7B78B4009B; Thu, 16 Dec 2010 08:44:48 -0700 (MST)
Message-ID: <4D0A30FC.20201@stpeter.im>
Date: Thu, 16 Dec 2010 08:32:12 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: =?UTF-8?B?VGFudGVrIMOHZWxpaw==?= <tantek@cs.stanford.edu>
References: <AANLkTikmTKSwBVYYtUmEnPB=9Vd9d9ei8KxS5e_-MWTQ@mail.gmail.com>
In-Reply-To: <AANLkTikmTKSwBVYYtUmEnPB=9Vd9d9ei8KxS5e_-MWTQ@mail.gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030608000701000006050502"
Cc: vcarddav@ietf.org
Subject: Re: [VCARDDAV] two component GENDER
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Dec 2010 15:30:31 -0000

On 12/16/10 1:11 AM, Tantek Çelik wrote:
> On Wed, Dec 15, 2010 at 21:48, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>> Hi Tantek, thanks for the feedback.
>>
>> On 12/15/10 8:31 PM, Tantek Çelik wrote:
>>
>>> One particularly important feature change that I wanted to comment on
>>> without delay however is the adoption of the new GENDER property.
>>>
>>> GENDER
>>>
>>> While I certainly applaud the increasing of flexibility from an enum
>>> to plain text field, I'd like to please ask the group to consider
>>> adopting the GENDER property as originally proposed with two
>>> components, a sex enum (M(ale),F(emale),N(one),O(ther),U(nknown)) and
>>> a plain text gender identity label. Both of these are necessary for
>>> supporting flexibility for human diversity and for representing
>>> existing publishing practices and gender specific search user
>>> interfaces.
>>>
>>> The two component GENDER property proposal was met with approval by
>>> Kevin Marks and Sarah Dopp:
>>>
>>> http://www.ietf.org/mail-archive/web/vcarddav/current/msg01784.html
>>>
>>> And as a result I had presumed there was at least weak consensus in
>>> the group on this specific proposal since there were no objections and
>>> no further messages on that thread. I must admit I was a little
>>> surprised to see a single component GENDER property instead (I am
>>> assuming this was simply a minor oversight rather than an explicit
>>> decision).
>>>
>>> I am more than happy to contribute specification text if necessary.
>>> I've iterated a bit more here:
>>>
>>> https://wiki.mozilla.org/VCard4-draft-13-review#GENDER
>>
>> The meeting notes said:
>>
>>  - Resolution: Rename SEX to GENDER. Change values to (male, female,
>>  <free-form text>). IANA registry for additional values that could be
>>  reserved.
> 
> Right, this is what I didn't understand, as just a single text value
> with 2 predefined values and <free-form text> was not proposed before
> this.
> 
>> If I recall correctly, the idea was that free-form text would be
>> allowed, such as:
>>
>>   GENDER:VALUE=text:Fellow
> 
> I think that's where the miscommunication was, probably due to my
> failure to provide specific syntax examples at the time.  The idea was
> that free-form text would be allowed IN ADDITION, such as:
> 
> GENDER:M;Fellow
> 
> 
>> Instead of:
>>
>>   GENDER:male
> 
> Instead of
> 
> GENDER:M
> 
> 
>> People could also register well-known values, such as:
>>
>>   GENDER:queer
>>
>> You seem to be proposing that the free-form text would supplement one of
>> the defined values (or no value at all). Correct? I just want to make
>> sure that I understand the proposal.
> 
> Close.
> 
> GENDER:;queer
> 
> (though in practice I'd expect many values, like 'queer', to be left
> unregistered, as different people have quite different definitions).

That seems to be endemic to the topic.

But, if someone registers "queer", the result would be what?

1. GENDER:;queer

or

2. GENDER:queer

My impression from the discussion in Beijing was #2, not #1 (if, again,
someone registered "queer" with IANA).

Peter

--
Peter Saint-Andre
https://stpeter.im/