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

James M Snell <jasnell@gmail.com> Tue, 22 April 2008 05:44 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 46FF128C44D; Mon, 21 Apr 2008 22:44:04 -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 41ED928C449 for <ietf@core3.amsl.com>; Mon, 21 Apr 2008 22:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level:
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067, 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 WW7jkGX7oPWv for <ietf@core3.amsl.com>; Mon, 21 Apr 2008 22:44:02 -0700 (PDT)
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by core3.amsl.com (Postfix) with ESMTP id 6A6793A68B6 for <ietf@ietf.org>; Mon, 21 Apr 2008 22:44:02 -0700 (PDT)
Received: by py-out-1112.google.com with SMTP id x19so2703828pyg.24 for <ietf@ietf.org>; Mon, 21 Apr 2008 22:44:08 -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=BjNtENXnm/vEu+6/Hb4NwGyIRO1/HbaHrIZ55O7Nrpg=; b=lMdgSPLvTOADvzRLrZ83rKgB9d02tFTJD4tzfzZ9UKyAdzQU3fQyCSqcWJXbd4oSprT8R8Rh6F5GE3/r+36ODHKyGO38Ve3aZmeLUQtWIosSrofBV4cW14s7OVrKyK2u9lmWzARkcw1bQ/m9gxhO8Y6BF7SEhOJ5lGdnaWqww2c=
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=CFi9DEPwR+2p1o3AJD5sP4+ep2ncvr0ia7jld88444+iEPvq9TUnET08l4xfsAsQ0Vgq7G9hhTWdB35hzqu2YHPrHm1RZ709anqfoyIvW7ckHssAvGwL0o2OMTUROlsaL0D/B0HcwO2/zsIJMOdMx31FLbxIhFEgrKGTdCCceSY=
Received: by 10.35.49.11 with SMTP id b11mr12186464pyk.40.1208843048529; Mon, 21 Apr 2008 22:44:08 -0700 (PDT)
Received: from ?192.168.2.2? ( [67.181.217.27]) by mx.google.com with ESMTPS id p77sm6467143pyb.16.2008.04.21.22.44.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 21 Apr 2008 22:44:07 -0700 (PDT)
Message-ID: <480D7B24.2040506@gmail.com>
Date: Mon, 21 Apr 2008 22:44:04 -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 BidirectionalAttribute) to Experimental RFC
References: <47FFC306.7020100@gmail.com> <ftojjk$c81$1@ger.gmane.org><20080414073227.GA22354@nic.fr> <ftv472$sbe$1@ger.gmane.org> <20080414083720.GA30386@nic.fr> <ftv81f$9in$1@ger.gmane.org>
In-Reply-To: <ftv81f$9in$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

The dir="" is not really intended to specify that the direction is not 
known but that the direction has not been specified explicitly.  For 
instance, in an aggregate feed containing entries from multiple sources, 
the original entries may or may not have contained the bidi attribute. 
Because of the inheritance of direction from the feed, entries that do 
not have a dir="..." attribute will inherit the direction of the parent, 
which will change the context of the original entry and could 
potentially lead to the context being improperly or at least 
unexpectedly displayed relative to the original.

- James

Frank Ellermann wrote:
> Stephane Bortzmeyer wrote:
> 
>> as I said, otherwise, you could not express the fact that the
>> direction of the text in the <bar> element above is "Not Known".
>> Without dir="", you could not "cancel" the directionality of
>> <foo> in its nested elements.
> 
> Well, yes, but so far the Web with all its (X)HTML pages never 
> needed an "unknown direction" feature, why is this necessary
> in ATOM ?  And how would you implement an "unknown direction",
> toss a coin ?
> 
>  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