Re: [webfinger] [appsawg] #12: Semantic gap for the client side
"Paul E. Jones" <paulej@packetizer.com> Fri, 28 June 2013 10:46 UTC
Return-Path: <paulej@packetizer.com>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD91921F9EFE for <webfinger@ietfa.amsl.com>; Fri, 28 Jun 2013 03:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5hnf+mct4OT for <webfinger@ietfa.amsl.com>; Fri, 28 Jun 2013 03:46:39 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 252F621F9EF7 for <webfinger@ietf.org>; Fri, 28 Jun 2013 03:46:39 -0700 (PDT)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r5SAkcCQ027784 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 28 Jun 2013 06:46:38 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1372416398; bh=RQwoLBH8i0AidP4BspQxbJIsHRtMt7uQHcTqBkLABaQ=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=hInTv6QNABwh9QAZtwDziVMpVSCVTvSTWEf10a4KOnYwpURhCJfCVx7a4m2TaSJtA xEDvcisDzDpl8PzVCc2msc26ez5NAeKWrJGnMl9UFdacKr8nOo7KtNMnZz57d/cjM/ 6in8SUxNVwtcLxaP16uxj5YB1heqejEkXQuj0rsE=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'Stephane Bortzmeyer' <bortzmeyer@nic.fr>
References: <071.1f5cc037d908127f5ac6f4afd3d8842a@trac.tools.ietf.org> <026701ce5cdb$2e7d2630$8b777290$@packetizer.com> <CAKaEYhLX5o9XM-t0iX5fMAXBrcmv1f2pYbPhP+DVNK=OUjSe=w@mail.gmail.com> <024301ce5d92$f7d06080$e7712180$@packetizer.com> <51B9E0AC.5070508@qti.qualcomm.com> <002a01ce68a3$8501aac0$8f050040$@packetizer.com> <20130614065904.GA30932@nic.fr> <005f01ce68ce$2665a3b0$7330eb10$@packetizer.com> <20130614142735.GA10799@nic.fr> <00b701ce691c$29354200$7b9fc600$@packetizer.com> <20130628101033.GA22661@nic.fr>
In-Reply-To: <20130628101033.GA22661@nic.fr>
Date: Fri, 28 Jun 2013 06:47:02 -0400
Message-ID: <073401ce73ec$d2b6e240$7824a6c0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFNWMcWAQ1n5b22xM4UdUF6Zyw7DQLrgow+AwtEfrIBDFDY6AJtOwD0Amz+c8MBpoKlLAHOxQXMAoqTx4cB9PKMGwH0pdfCmZ7wJpA=
Content-Language: en-us
Cc: webfinger@ietf.org
Subject: Re: [webfinger] [appsawg] #12: Semantic gap for the client side
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2013 10:46:49 -0000
Stephane, If I am entering the text that goes into the WF output and I spell words using US English, then en-us is the appropriate thing to put. Just because the spelling in that particular example aligns with British spelling does not mean there is no significance. Following your example, I assume you would agree with this: { "en-us" : "The Magical Theater of Bob", "fr" : "Le Théâtre magique de Bob" } But the software didn't change. And my WF server is not going to have a language analyzer to know the least restrictive value to use. The language tag is likely going to be fairly automatic and derived from the user's locale. Paul > -----Original Message----- > From: 'Stephane Bortzmeyer' [mailto:bortzmeyer@nic.fr] > Sent: Friday, June 28, 2013 6:11 AM > To: Paul E. Jones > Cc: webfinger@ietf.org > Subject: Re: [webfinger] [appsawg] #12: Semantic gap for the client side > > On Fri, Jun 14, 2013 at 12:28:10PM -0400, > Paul E. Jones <paulej@packetizer.com> wrote > a message of 66 lines which said: > > > > OK for me (except the erroneous "en-us" that I already mentioned here) > > > > What's the issue with "en-us"? > > http://www.ietf.org/mail-archive/web/webfinger/current/msg00555.html > > RFC 5646 says: > > > Use as precise a tag as possible, but no more specific than is > > justified. Avoid using subtags that are not important for > > distinguishing content in an application. > > > > * For example, 'de' might suffice for tagging an email written > > in German, while "de-CH-1996" is probably unnecessarily > > precise for such a task. > > Which seems to apply exactly here (there is nothing US-specific in the > sentence). May be, instead: > > "titles" : > { > "en-us" : "The Magical Theater of Bob", > "en-gb" : "The Magical Theatre of Bob", > ...
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Melvin Carvalho
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Mike Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Melvin Carvalho
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Melvin Carvalho
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Melvin Carvalho
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Pete Resnick
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Stephane Bortzmeyer
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Pete Resnick
- Re: [webfinger] [appsawg] #12: Semantic gap for t… 'Stephane Bortzmeyer'
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Cyrus Daboo
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Stephane Bortzmeyer
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Barry Leiba
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Pete Resnick
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Pete Resnick
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Peter Saint-Andre
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Evan Prodromou
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Evan Prodromou
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Mike Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Peter Saint-Andre
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Gonzalo Salgueiro
- [webfinger] R: [appsawg] #12: Semantic gap for th… Goix Laurent Walter
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Melvin Carvalho
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Pete Resnick
- [webfinger] R: [appsawg] #12: Semantic gap for th… Goix Laurent Walter
- Re: [webfinger] [appsawg] #12: Semantic gap for t… 'Stephane Bortzmeyer'
- Re: [webfinger] [appsawg] #12: Semantic gap for t… Paul E. Jones