looking for atom advice (newbie atom developer)

Miles Fidelman <mfidelman@meetinghouse.net> Mon, 19 September 2011 15:52 UTC

Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@ietfa.amsl.com
Delivered-To: ietfarch-atompub-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46A0221F8C5B for <ietfarch-atompub-archive@ietfa.amsl.com>; Mon, 19 Sep 2011 08:52:09 -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 6pK5651nk0vd for <ietfarch-atompub-archive@ietfa.amsl.com>; Mon, 19 Sep 2011 08:52:08 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id EA34421F8C4D for <atompub-archive@ietf.org>; Mon, 19 Sep 2011 08:52:07 -0700 (PDT)
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p8JFkFQl080016 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Sep 2011 08:46:15 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p8JFkFNQ080015; Mon, 19 Sep 2011 08:46:15 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p8JFkEpH080004 for <atom-syntax@imc.org>; Mon, 19 Sep 2011 08:46:15 -0700 (MST) (envelope-from mfidelman@meetinghouse.net)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 2B956CC1AB for <atom-syntax@imc.org>; Mon, 19 Sep 2011 11:46:14 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CzCgpjvmov25 for <atom-syntax@imc.org>; Mon, 19 Sep 2011 11:46:11 -0400 (EDT)
Received: from new-host-3.home (pool-173-76-134-212.bstnma.fios.verizon.net [173.76.134.212]) by server1.neighborhoods.net (Postfix) with ESMTPSA id ECC63CC17F for <atom-syntax@imc.org>; Mon, 19 Sep 2011 11:46:10 -0400 (EDT)
Message-ID: <4E7763C2.3050801@meetinghouse.net>
Date: Mon, 19 Sep 2011 11:46:10 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.2) Gecko/20110902 Firefox/6.0.2 SeaMonkey/2.3.3
MIME-Version: 1.0
To: atom-syntax@imc.org
Subject: looking for atom advice (newbie atom developer)
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Hello Folks,

Please excuse me if this is the wrong list for these questions, but 
there don't seem to be very many places where atom is actively discussed 
(if anyone can point me at a better community for developers working 
with atom, please let me know).

We're considering using Atom in a somewhat non-standard way - as a 
vehicle for transporting HTML content (think web pages, single-page 
JavaScript applications).  It seems like Atom is perfect for this, but 
the specifications are a bit vague in several areas, and implementations 
even more so.

RE. SPECS:

The spec. for content elements, of type HTML (RFC4287, par. 3.1.1.2.), 
says "If the value of "type" is "html", the content of the Text 
construct  .... SHOULD be suitable for handling as HTML [HTML 
<http://tools.ietf.org/html/rfc4287#ref-HTML>] ... (and) 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."

This implies that the notional use of an HTML content element is for a 
snippet of HTML, but does not seem to preclude embedding an entire web 
page, including JavaScript, within an HTML content element.

Questions:

1. Is this a correct interpretation?

2. If so, does anybody know of anybody who's doing this kind of thing?

3. Can anybody suggest any tools, libraries for generating Atom with 
complicated content elements, posting it via Atompub, processing posts 
on a server, and then parsing feeds on a client?  It seems like all of 
the tools I've been able to find view Atom as nothing more than a 
replacement for RSS as a way to post and read blog feeds.

4. Any thoughts or pointers vis-a-vis how common browsers handle Atom 
feeds.  It's already clear that they handle/render feeds differently 
when they're accessed via HTTP, than when the same XML is read from a 
file.  It sure would be nice to find some material that would help me 
understand what's going on.

Thanks very much for any assistance you can offer.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In<fnord>  practice, there is.   .... Yogi Berra