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

DataPacRat <> Thu, 12 September 2013 11:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B900111E8218 for <>; Thu, 12 Sep 2013 04:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Tfs-EpELD7DR for <>; Thu, 12 Sep 2013 04:38:25 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c00::232]) by (Postfix) with ESMTP id AA0E911E820E for <>; Thu, 12 Sep 2013 04:38:24 -0700 (PDT)
Received: by with SMTP id f12so417303wgh.17 for <>; Thu, 12 Sep 2013 04:38:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VXLUgRFxYgTY0+cp4DB5YbrGncoTDSGyQrIfVym7/fE=; b=ot9J+7/+992oGFo9KMRlbp795ShyW8zpB/T+kaQHICnaFPwzgdXdUgTl56QHZde8kz NLmdpko7l6IX5FsWR5VU9s+X5I/lSnH8KkwnbpAgrW0/AEnJ76SMc56jjXAg3MJG/+Hz qg0vMQ0eo5bqx2uVfMaoBCnWb9YfanKZjYjR2rWxLEuaQiDdWC33o4GjfM7f92C8YRtI ppMAdLJN3iKp+9vB9mcZTNGcHntmK49/GbWeH4Az/Qkt0DHJMlu10uFKfXIbMRqNL33+ p0GOEDY/BpyCA4Zlsj/aXstYsz9fttENinZFw5mekRwxmmUP1Tn4xXivKv4BdiVb/yzi oQaQ==
MIME-Version: 1.0
X-Received: by with SMTP id pk1mr5697336wjc.36.1378985903754; Thu, 12 Sep 2013 04:38:23 -0700 (PDT)
Received: by with HTTP; Thu, 12 Sep 2013 04:38:23 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Thu, 12 Sep 2013 07:38:23 -0400
Message-ID: <>
From: DataPacRat <>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "" <>
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, 12 Sep 2013 11:38:25 -0000

On Thu, Sep 12, 2013 at 6:18 AM, Gren Elliot <> wrote:

> For Japanese people, using Katakana and/or Hiragana is more
> convenient, because they can write and understand it.  However, many
> non-Japanese people would not understand it and it would be more
> useful for Japanese name phonetic information to be provided in
> another form, perhaps IPA or in a phonetic script that they are
> familiar with.

> A simple example (I'm sure others can do better):
> For the Japanese food stuff "Sushi", the VCARD could contain the 2
> properties, one useful to English students studying Japanese who
> haven't mastered Hiragana or Katakana yet and use the simple phonetic
> system called Furigana and one which is hopefully universally useful
> and could be used by generic international software to produce audio
> for one proper way (according to
> to say the word.
> We would need new IANA tokens for acceptable VALUE settings.  I suggest:
> IPA - The International Phonetic Alphabet (IPA).  Unicode supports IPA
> symbols, so this should be usable.
> IPA-X-SAMPA - The Extended Speech Assessment Methods Phonetic Alphabet
> (X-SAMPA).  Using IPA-X-SAMPA rather than X-SAMPA because the latter
> begins with "X-" and thus can't be used as a registered token.
> FURIGANA - Japanese phonetic alphabet
> HIRAGANA - Japanese phonetic alphabet
> I don't propose that we actually register FURIGANA as an accepted IANA
> token - I'm using it here because it is ASCII.

There's already a well-developed set of language and script tags at
- it may be possible to mine that namespace instead of coming up with
new tags. There's jp-Hira and jp-Kana , plus jp-Hrkt is "Japanese
syllabaries (alias for Hiragana + Katakana)" and jp-Jpan "Japanese
(alias for Han + Hiragana + Katakana)". jp-fonipa for direct IPA
characters, and jp-fonxsamp for X-SAMPA ones.

RFC5646, , is the reference for
such tags, and user-created tags for private use are in section 2.2.7, . I'm not sure if
it's a good idea to write an RFC which depends on the use of such
tags. If furigana isn't listed in the IANA registry under another
name, then perhaps a good first step would be to submit it there?

Thank you for your time,
"Then again, I could be wrong."