Return-Path: 
 <abdera-dev-return-289-apmail-incubator-abdera-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-abdera-dev-archive@locus.apache.org
Received: (qmail 50033 invoked from network); 27 Jun 2006 21:43:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 27 Jun 2006 21:43:32 -0000
Received: (qmail 27755 invoked by uid 500); 27 Jun 2006 21:43:31 -0000
Delivered-To: apmail-incubator-abdera-dev-archive@incubator.apache.org
Received: (qmail 27722 invoked by uid 500); 27 Jun 2006 21:43:31 -0000
Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:abdera-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:abdera-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:abdera-dev@incubator.apache.org>
List-Id: <abdera-dev.incubator.apache.org>
Reply-To: abdera-dev@incubator.apache.org
Delivered-To: mailing list abdera-dev@incubator.apache.org
Received: (qmail 27713 invoked by uid 99); 27 Jun 2006 21:43:31 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2006 14:43:31 -0700
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=DNS_FROM_RFC_ABUSE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of stephen.duncan@gmail.com
 designates 66.249.92.168 as permitted sender)
Received: from [66.249.92.168] (HELO ug-out-1314.google.com) (66.249.92.168)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2006 14:43:30 -0700
Received: by ug-out-1314.google.com with SMTP id q2so2215244uge
        for <abdera-dev@incubator.apache.org>;
 Tue, 27 Jun 2006 14:43:09 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Ke7MYdDVKDxcb7hvPsFgMezD7gaXqiwwhkahwzx74f7/LhAfGX+Derl1xGKGDDmfE7+6eMLo3FaBZ2RNfz9AYxAQE6UYbbbsOeGFoK8AP4WQwT668lImiVW7Enx1tvMQYyt14+FEtdvv4k1d8T8O2i1wDEXyWx6pP47uhgmu7ZA=
Received: by 10.78.177.3 with SMTP id z3mr14545hue;
        Tue, 27 Jun 2006 14:43:09 -0700 (PDT)
Received: by 10.78.53.20 with HTTP; Tue, 27 Jun 2006 14:43:09 -0700 (PDT)
Message-ID: <b20ce4ed0606271443t4650e05fmb578e68015117dd7@mail.gmail.com>
Date: Tue, 27 Jun 2006 17:43:09 -0400
From: "Stephen Duncan" <stephen.duncan@gmail.com>
To: abdera-dev@incubator.apache.org
Subject: Re: XHTML Content
In-Reply-To: <44A186F2.8090801@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <68fba5c50606271205r6daccc11k386b3ab1fe594ac1@mail.gmail.com>
	 <44A186F2.8090801@gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 6/27/06, James M Snell <jasnell@gmail.com> wrote:
>
>
> 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.

Reading the spec as a whole, it's clearly meant to mimic Section 3.1.1.2:

"HTML markup within SHOULD be such that it could
   validly appear directly within an HTML <DIV> element, after
   unescaping.  Atom Processors that display such content MAY use that
   markup to aid in its display."

meaning that if it helps, you can surround the content with a div (I
don't think Robert is correct in it referring to the content).  The
purpose of NOT considering the DIV as part of the content in the XHTML
case is to make it such at that it is possible to have equal HTML &
XHTML content where escaping is the only difference.

I do think it's Abdera's job to take into account details like this
from the spec.  If it's just going to be a simple wrapper for the
straight XML, I could just make an XSD for Atom and use XMLBeans.   I
think providing the wrapping DIV rather than forcing it to be part of
the string makes it easier for people to produce Atom, and regarding
retreiving the content, I think "MUST NOT be considered part of the
content" is a clear enough guide that it's the right things to give
back to people wanting to read Atom.

-- 
Stephen Duncan Jr
www.stephenduncanjr.com