Re: Last Call: draft-snell-atompub-bidi (Atom Bidirectional Attribute) to Experimental RFC

James M Snell <jasnell@gmail.com> Tue, 22 April 2008 17:18 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AD263A67B3; Tue, 22 Apr 2008 10:18:31 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CBD628C4D0 for <ietf@core3.amsl.com>; Tue, 22 Apr 2008 10:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.132
X-Spam-Level:
X-Spam-Status: No, score=-2.132 tagged_above=-999 required=5 tests=[AWL=0.467, BAYES_00=-2.599]
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 ItLnSZzYW56U for <ietf@core3.amsl.com>; Tue, 22 Apr 2008 10:18:21 -0700 (PDT)
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by core3.amsl.com (Postfix) with ESMTP id 22F3328C4F3 for <ietf@ietf.org>; Tue, 22 Apr 2008 10:17:01 -0700 (PDT)
Received: by py-out-1112.google.com with SMTP id x19so2985574pyg.24 for <ietf@ietf.org>; Tue, 22 Apr 2008 10:17:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; bh=+qQqpyKluwFJNOsBXmhLfIW2vB1F1VYwu2N5mVTctYQ=; b=LF/xsoSdKdiGztsmF8ZTxw5k4NtycdFOF2rhKZZK/8RIR5HTnfMBYuT9dxI1NJCqB0HlVFsOfFbpx6ckrVsdV+Uh63wDUgvIMnBX6EVxPnd6rutRtU1v0GAdelV4yWFXw27eQRgG7CsT4fN8Y0iCDALgpxcIXXKgXS1cimxu1/E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=I30PLnzRIGIAkSK82JBlKOwIcIuY1zvC36uNLtAJbDljpoTn4J3G57QnnPjTtUna7s//dI5uF0tZOrnGHeM0YXlFYoX+AqgLfjS4S32mgCHTSxSkA/ScFfg7KNIvG81Mvb0nZUJ5j/ASZ87lJSpJtr8GQE9czokJxwjxiogHmCg=
Received: by 10.35.68.3 with SMTP id v3mr788676pyk.32.1208884626731; Tue, 22 Apr 2008 10:17:06 -0700 (PDT)
Received: from ?192.168.2.2? ( [67.181.217.27]) by mx.google.com with ESMTPS id x56sm16433234pyg.36.2008.04.22.10.17.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Apr 2008 10:17:03 -0700 (PDT)
Message-ID: <480E1D85.6040006@gmail.com>
Date: Tue, 22 Apr 2008 10:16:53 -0700
From: James M Snell <jasnell@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Subject: Re: Last Call: draft-snell-atompub-bidi (Atom Bidirectional Attribute) to Experimental RFC
References: <20080411190345.DD6DC28C28B@core3.amsl.com><517bf110804111247g100af6bbh471420f451647f76@mail.gmail.com> <47FFC306.7020100@gmail.com><ftojjk$c81$1@ger.gmane.org> <480D7C98.2010801@gmail.com> <ful3ft$v8r$1@ger.gmane.org>
In-Reply-To: <ful3ft$v8r$1@ger.gmane.org>
X-Enigmail-Version: 0.95.6
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

I have had a number of conversations with i18n experts on the topic and 
none have complained about it thus far... which, of course, doesn't mean 
that much.  I would very much appreciate having folks like Harald, 
Martin and Tex weigh in on the issue.

Another comment that has come up is a question about why we can't just 
use the W3C ITS spec for this, which is definitely a valid question.  I 
would definitely appreciate feedback on that issue as well.

When it comes to the rendering of feeds in a UI, dir="" is likely not to 
have any significant effect since, as you and others have pointed out, 
(x)html has no similar notion and a direction has to be assumed.  The 
main point of dir="" is to ensure that the original directional context 
of an entry is preserved regardless of the specific feed that happens to 
contain the entry.

- James

Frank Ellermann wrote:
> James M Snell wrote:
> 
>> My apologies for not getting back to this sooner.
> 
> No problem, it's only that the proposal to "rename" 
> the draft attracted my attention, and after I said
> that this is dubious in a "Last Call" thread I read
> the text, not only the file name... ;-)
> 
> All I know about BiDi issues could be summarized as
> "if Harald / Martin / Tex / ... think it works it's
> supposed to work".  But the acknowledgements in your
> draft did not mention anybody I know as BiDi-expert,
> that was the point when I started to worry about it.
> 
> Apparently 'dir' is strictly binary, "LTR" or "RTL",
> and your draft adds a third value "".  Maybe this is
> a good idea.  Or it is a case of "ternary bits", I
> can't judge it.
> 
> Possibly you could convince me that it's a good idea
> by giving an example where dir="ltr" and dir="" make
> a difference, and/or by stating that dir="" MUST NOT
> be used within the (X)HTML parts of an Atom document,
> but actually that's beside the point.  What's really
> interesting, did any BiDi expert confirm dir="" as a
> good idea ?  If dir="" is a part of the experiment -
> fine, let's see what happens.
> 
>  Frank
> 
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf