Re: [Ltru] clear guidance on tagging in cases involving a related macrolanguage

"Broome, Karen" <Karen_Broome@spe.sony.com> Fri, 23 May 2008 02:49 UTC

Return-Path: <ltru-bounces@ietf.org>
X-Original-To: ltru-archive@megatron.ietf.org
Delivered-To: ietfarch-ltru-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAD303A6C0B; Thu, 22 May 2008 19:49:28 -0700 (PDT)
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B7EA3A6C06 for <ltru@core3.amsl.com>; Thu, 22 May 2008 19:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 w6WSFOKwegDo for <ltru@core3.amsl.com>; Thu, 22 May 2008 19:49:27 -0700 (PDT)
Received: from outbound8-sin-R.bigfish.com (outbound-sin.frontbridge.com [207.46.51.80]) by core3.amsl.com (Postfix) with ESMTP id AC3623A6BA9 for <ltru@ietf.org>; Thu, 22 May 2008 19:49:26 -0700 (PDT)
Received: from outbound8-sin.bigfish.com (localhost.localdomain [127.0.0.1]) by outbound8-sin-R.bigfish.com (Postfix) with ESMTP id A73C57802AB; Fri, 23 May 2008 02:49:23 +0000 (UTC)
Received: from mail129-sin-R.bigfish.com (unknown [10.3.40.3]) by outbound8-sin.bigfish.com (Postfix) with ESMTP id 99B5B4E8060; Fri, 23 May 2008 02:49:23 +0000 (UTC)
Received: from mail129-sin (localhost.localdomain [127.0.0.1]) by mail129-sin-R.bigfish.com (Postfix) with ESMTP id 76BC1A80403; Fri, 23 May 2008 02:49:23 +0000 (UTC)
X-BigFish: V
X-MS-Exchange-Organization-Antispam-Report: OrigIP: 160.33.98.75;Service: EHS
Received: by mail129-sin (MessageSwitch) id 1211510962238578_20139; Fri, 23 May 2008 02:49:22 +0000 (UCT)
Received: from mail8.fw-bc.sony.com (mail8.fw-bc.sony.com [160.33.98.75]) by mail129-sin.bigfish.com (Postfix) with ESMTP id 88284B8069; Fri, 23 May 2008 02:49:21 +0000 (UTC)
Received: from mail1.sgo.in.sel.sony.com (mail1.sgo.in.sel.sony.com [43.130.1.111]) by mail8.fw-bc.sony.com (8.12.11/8.12.11) with ESMTP id m4N2nJrC017911; Fri, 23 May 2008 02:49:20 GMT
Received: from ussdixhub21.spe.sony.com ([43.130.141.76]) by mail1.sgo.in.sel.sony.com (8.12.11/8.12.11) with ESMTP id m4N2nJiu016688; Fri, 23 May 2008 02:49:19 GMT
Received: from USSDIXMSG20.spe.sony.com ([43.130.141.74]) by ussdixhub21.spe.sony.com ([43.130.141.76]) with mapi; Thu, 22 May 2008 19:49:19 -0700
From: "Broome, Karen" <Karen_Broome@spe.sony.com>
To: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 22 May 2008 19:47:25 -0700
Thread-Topic: [Ltru] clear guidance on tagging in cases involving a related macrolanguage
Thread-Index: Aci8e0Y3mWxzFpDdSHaAiqy2Bl3rvwABA7xD
Message-ID: <E19FDBD7A3A7F04788F00E90915BD36C13C2528AA6@USSDIXMSG20.spe.sony.com>
References: <01c301c8bbe5$8c2810c0$6801a8c0@oemcomputer> <30b660a20805221029k13cdb18asf31bcb6f9fc491a1@mail.gmail.com> <DDB6DE6E9D27DD478AE6D1BBBB83579562E2683F73@NA-EXMSG-C117.redmond.corp.microsoft.com> <C9BF0238EED3634BA1866AEF14C7A9E56157008C2B@NA-EXMSG-C116.redmond.corp.microsoft.com> <DDB6DE6E9D27DD478AE6D1BBBB83579562E2683FA7@NA-EXMSG-C117.redmond.corp.microsoft.com> <C9BF0238EED3634BA1866AEF14C7A9E56157008C4B@NA-EXMSG-C116.redmond.corp.microsoft.com> <E19FDBD7A3A7F04788F00E90915BD36C13C251B147@USSDIXMSG20.spe.sony.com> <DDB6DE6E9D27DD478AE6D1BBBB83579562E268407E@NA-EXMSG-C117.redmond.corp.microsoft.com> <E19FDBD7A3A7F04788F00E90915BD36C13C251B160@USSDIXMSG20.spe.sony.com>, <DDB6DE6E9D27DD478AE6D1BBBB83579562E268410A@NA-EXMSG-C117.redmond.corp.microsoft.com> <E19FDBD7A3A7F04788F00E90915BD36C13C2528A9E@USSDIXMSG20.spe.sony.com>, <48362950.9010904@w3.org>
In-Reply-To: <48362950.9010904@w3.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ltru@ietf.org" <ltru@ietf.org>
Subject: Re: [Ltru] clear guidance on tagging in cases involving a related macrolanguage
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

Yes, that's why I thought the question was a false choice. I could imagine scenarios where I might find it acceptable to use only "cmn". But I'm not convinced this is the best solution given the history of the tag and my needs. I'm not so sure my needs are unique. Don Osborn's situation sounded similar to mine. As did Leif's, though I think I disagree with him about various solutions.

When there starts to be too much preferred tag logic based on subjective judgments (such as the relative dominance of encompassed languages) and there are different tags for the same thing -- that *could* in some rare cases mean something completely different (zh and cmn); and you're about to make nonsense of a rather popular set of grandfathered tags as grandfathered tags go (zh-yue, zh-min-nan, etc.)... Well? I'm having a hard time just writing that sentence, much less explaining that to the people that scowl at my explanation for the de-CH/gsw situation.

I'm thinking a lot of fallback situations in my world are really carefully considered business decisions so my primary concern is precise identification of the language. I figure if I can do that and have confidence in what those tags mean, I can throw any logic I want on top of it.

Regards,

Karen Broome


________________________________________
From: Felix Sasaki [fsasaki@w3.org]
Sent: Thursday, May 22, 2008 7:17 PM
To: Broome, Karen
Cc: Peter Constable; ltru@ietf.org
Subject: Re: [Ltru] clear guidance on tagging in cases involving a related macrolanguage

Broome, Karen さんは書きました:
> I think extlang will likely be a cleaner solution to me than what you might offer, but I'm open to that as long as the preferred tagging and associated semantics are clear.
>

this sounds like your vote

1: C
2: A

could also be

1: B (if there is a clear guidance on tagging in cases involving a related
macrolanguage available)
2: A

but given the long discussion about sec.
http://tools.ietf.org/html/draft-ietf-ltru-4646bis-14#section-4.1.1
it seems difficult to formulate that guidance.

Felix

> I think de-CH is a problem. I see more problems like this if we move forward extlangless with multiple "preferred" tag choices for the same thing and subjective distinctions. In the face of that, I start to like ISO 639-6.
>
> I *like* hierarchies.
>
> Karen
>
> ________________________________________
> From: Peter Constable [petercon@microsoft.com]
> Sent: Thursday, May 22, 2008 6:40 PM
> To: Broome, Karen
> Cc: LTRU Working Group
> Subject: RE: clear guidance on tagging in cases involving a related     macrolanguage
>
> Could you live without extlang provided those conditions were met, or do you think those conditions can't be met without extlang?
>
>
> Peter
>
>
>> -----Original Message-----
>> From: Broome, Karen [mailto:Karen_Broome@spe.sony.com]
>> Sent: Thursday, May 22, 2008 5:01 PM
>> To: Peter Constable
>> Cc: LTRU Working Group
>> Subject: RE: clear guidance on tagging in cases involving a related
>> macrolanguage
>>
>> Yes, Peter.
>>
>>
>>> -----Original Message-----
>>> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf
>>> Of Peter Constable
>>> Sent: Thursday, May 22, 2008 4:58 PM
>>> To: LTRU Working Group
>>> Subject: [Ltru] clear guidance on tagging in cases involving a
>>> related macrolanguage
>>>
>>> [changing the subject per Randy's request]
>>>
>>>
>>>> From: Broome, Karen [mailto:Karen_Broome@spe.sony.com]
>>>>
>>>> Either way, zh-yue will remain valid, but not necessarily
>>>>
>>> preferred.
>>>
>>>> Having clear preferences is very important to me. I really don't
>>>>
>>> want
>>>
>>>> to recommend that people use "zh" for Mandarin or have to explain
>>>>
>>> to
>>>
>>>> someone why I think a deprecated tag is preferred in this industry
>>>>
>>> but
>>>
>>>> not others.
>>>>
>>> And in another msg,
>>>
>>>
>>>> I care more about identification than applications.
>>>>
>>> So, it sounds to me like what you really care about are the
>>> following:
>>>
>>> - Don't have a recommendation "tag Madarin content as zh"
>>>
>>> - Have a single clear recommendation for how to tag each language
>>> (one or the other of "cmn" or "zh-cmn" for Mandarin would do).
>>>
>>>
>>> Is that right?
>>>
>>>
>>> Peter
>>> _______________________________________________
>>> Ltru mailing list
>>> Ltru@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ltru
>>>
>
>
>
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www.ietf.org/mailman/listinfo/ltru
>



_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www.ietf.org/mailman/listinfo/ltru