Re: [VCARDDAV] Review of draft-fukuda-vcarddav-phonetic-transcription-00.txt

Pete Resnick <> Thu, 03 October 2013 05:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8113921F84DB for <>; Wed, 2 Oct 2013 22:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eoSxJTNYvmSs for <>; Wed, 2 Oct 2013 22:56:48 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 37F7F21F8E21 for <>; Wed, 2 Oct 2013 22:56:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=qcdkim; t=1380779787; x=1412315787; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=RLt6m0zsCuAwuLqiBLNixvKPb/MDR0sEB4TlercLjUg=; b=crE8YP1WnpGTCDH0vXKYanlX/0Om8zNQH3ZFuJjxtTeIj3B42fMdcxOJ 0KAEZNKc/R/NzIeF8MgqN7uMbxH0dtj4gJqk7p5TL+fREgSzeWMwbyqeD ucgJdLefvoTkN8dJBGComG3L347KfF0yK5sxfB6iHkiMrOZScp8ALbT6O g=;
X-IronPort-AV: E=McAfee;i="5400,1158,7216"; a="78151692"
Received: from ([]) by with ESMTP; 02 Oct 2013 22:56:17 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7216"; a="546690077"
Received: from ([]) by with ESMTP/TLS/RC4-SHA; 02 Oct 2013 22:56:17 -0700
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Wed, 2 Oct 2013 22:56:16 -0700
Message-ID: <>
Date: Thu, 03 Oct 2013 00:56:15 -0500
From: Pete Resnick <>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv: Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Cyrus Daboo <>
References: <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: []
Subject: Re: [VCARDDAV] Review of draft-fukuda-vcarddav-phonetic-transcription-00.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF vcarddav wg mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 03 Oct 2013 05:57:01 -0000

On 9/12/13 9:43 AM, Cyrus Daboo wrote:
> Hi Gren,
> --On September 12, 2013 at 3:17:13 PM +0100 Gren Elliot 
> <> wrote:
>>> Using TYPE instead of VALUE might be better.  VALUE represents a data
>>> type, which can be applied to other properties.  These settings are
>>> specific to this property alone.
>> I agree.  I think that makes more sense.
> Actually I would argue that the values should all have a corresponding 
> media type associated with them (MIME type) and then the MEDIATYPE 
> property parameter would be a better choice:
> PHONETIC-FULL-NAME;MEDIATYPE=text/ipa; option=x-sampa:/"sUSi/
> PHONETIC-FULL-NAME;MEDIATYPE=text/x-furigana:sushi
> Ideally we want these "types" registered for interoperability.


Fukuda-san asked whether Barry or I would be interested in sponsoring 
this document, so I had a read of it. I noticed the use of MEDIATYPE and 
found your message in the archive.

Please explain how MEDIATYPE is in any way correct for this. 6350 says:

    The MEDIATYPE parameter is used with properties whose value is a URI.
    Its use is OPTIONAL.  It provides a hint to the vCard consumer
    application about the media type [RFC2046] of the resource identified
    by the URI.

That's not even close to what this is. PHONETIC-NAME (as it currently is 
called) is a string that represents the phonetic pronunciation of the 
name. The string might be in a particular charset, but the string is 
certainly not going to change media type; it's always going to be 
"text/plain". I don't understand what "text/ipa" or "text/x-furigana" 
could possibly mean.

Now, I don't really understand why this thing needs a "type" anyway. If 
the string contains characters from the Hiragana range, it's Hirigana, 
and if it has characters from the IPA symbols range, it's IPA. In fact, 
adding a type that might disagree with the contents of the string seems 
problematic. And I think I agree with Simon that this should really be a 
property like "SORT-AS" that is added to a name property and simply 
contains the pronunciation, for example:

    FN;PHONETIC-NAME="<<blahblah>>:Rene van der Harten

But I am at a loss as to why MEDIATYPE makes any sense in this context. 
Can you explain?


Pete Resnick<>
Qualcomm Technologies, Inc. - +1 (858)651-4478