Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jasnell@gmail.com designates
 64.233.184.226 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=FoIpAMCgylYMJznLHaGMPW8hGb2Fow67d76ILKNy90y0h0RdXTdfzuMnmmRqX+QJF/E3b4UXOvCS1AyxCOV+gSE3TmVPyly+mhiEcqcIrGQV5xv20EcP7VuC3Kejk+ddJNk3unVGJjnvotoC3Hm3POfOMz+NTxrJVLvF4QwRAIg=
Message-ID: <44A186F2.8090801@gmail.com>
Date: Tue, 27 Jun 2006 12:28:50 -0700
From: James M Snell <jasnell@gmail.com>
User-Agent: Thunderbird 1.5.0.4 (X11/20060516)
MIME-Version: 1.0
To: abdera-dev@incubator.apache.org
Subject: Re: XHTML Content
References: <68fba5c50606271205r6daccc11k386b3ab1fe594ac1@mail.gmail.com>
In-Reply-To: <68fba5c50606271205r6daccc11k386b3ab1fe594ac1@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


Robert Sayre wrote:
> James M. Snell wrote:
>> The spec also says that applications can use the div to aid in
>> displaying the content.
> 
> The spec says no such thing, and that's a bogus reading. It looks like
> the text should have been still more mealy and tortured, but the
> "markup" in question is the XHTML content... as in you can strip
> whatever you want or use only some of it.
> 

Section 4.1.3.3, Item #3

"The XHTML div element itself MUST NOT be considered part of the
content.  Atom Processors that display the content MAY use the markup to
aid in displaying it."

There is no definition of "the markup". Mileage, and interpretation may
vary.  Abdera's job is simply to help produce and read Atom, not
validate it or specify how it's used.

>> What I would prefer is that abdera simply
>> treat the div as content and let the application using abdera do the
>> right thing with it.
> 
> Um, no. There are several good reasons that div is not part of the
> content, but they all add up to preventing the "telescoping div"
> phenomenon.
> 

Um, yes.  There are several good reasons for Abdera to pass the
responsibility of doing the right thing on to applications using the
library.  Abdera does not display content, it merely parses and helps
produce feeds and entries.  It does not perform validation. It allows a
developer to work with the Atom data model.  A feed reader
implementation built on top of Abdera could reasonably be expected to do
the right thing with regards to the div.  There's no need for us to do so.

> If you need help understanding how this should work, see the Mozilla
> implementation:
> http://lxr.mozilla.org/mozilla/source/toolkit/components/feeds/src/FeedProcessor.js#1002
> 

No thanks.  The Mozilla implementation has its own problems.

> 
> have a nice day and don't break Atom,
> 

- James