From owner-atom-syntax@mail.imc.org  Wed Oct  1 06:53:27 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04B643A6A67
	for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  1 Oct 2008 06:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_47=0.6]
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 mFmM+n7P5Q1I
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Wed,  1 Oct 2008 06:53:22 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 2DC5C3A6768
	for <atompub-archive@ietf.org>; Wed,  1 Oct 2008 06:53:21 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m91DjPaF089462
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 1 Oct 2008 06:45:25 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m91DjP7r089461;
	Wed, 1 Oct 2008 06:45:25 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m91DjOxU089452
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <atom-syntax@imc.org>; Wed, 1 Oct 2008 06:45:25 -0700 (MST)
	(envelope-from brian@briansmith.org)
Received: from T60 (unknown [70.136.54.236])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by smtp.mxes.net (Postfix) with ESMTP id 60FCFD0B92;
	Wed,  1 Oct 2008 09:45:23 -0400 (EDT)
From: "Brian Smith" <brian@briansmith.org>
To: "'Brian Smith'" <brian@briansmith.org>, <atom-syntax@imc.org>
References: <AC05A21D6BB8470E9FBC1CE72ADED9AE@T60>
Subject: Conflict between the AtomPub multipart/related and composite content proposals
Date: Wed, 1 Oct 2008 08:45:26 -0500
Message-ID: <EEEA4BB68777453C8E4B994DA3B08B1A@T60>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <AC05A21D6BB8470E9FBC1CE72ADED9AE@T60>
Thread-Index: AckdAwK/dkdCYaCvQa2WO/b0tIaJiAGx2gnw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
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>


Brian Smith wrote:
> My proposal is to create a new standards-track RFC that
> updates RFC 4287. The RFC would say only this
> (plus the standard RFC boilerplate text):
>
> ...
>
>    1. All MIME types are allowed in atom:content
> 
>       The restriction on atom:content's type
>       attribute "but MUST NOT be a composite type"
>       from section 4.1.3 in RFC 4287 is removed.
>       There are now no restrictions on the type of
>       content allowed in atom:content.
> 
>       The rules for processing atom:content remain
>       exactly as specified in Section 4.1.3.3
>       of [RFC4287]. In particular, when the 
>       atom:content element contains content with
>       a composite MIME type, that content must be
>       encoded in Base64 as specified in step #6 of
>       that section.

I got two positive responses and nobody objected. I was hoping for more
feedback, but I guess I will press on with this.

One issue that I did not mention in my previous message is that the current
multipart/alternate proposal doesn't compose well with this proposal. The
multipart/alternate proposal uses the Content-Type of the POST request to
decide when to unpack the request. As was mentioned in the earlier
discussion of the multipart/alternate draft, this conflicts with any other
use for posting multipart/related content to a collection. For example, I
have applications that post multipart/alternate content to collections so
that the multi-part message can be stored as-is in the collection as a media
resource. It would be better for the multipart proposal(s) to avoid
overloading the Content-Type header for its purposes. A new request header
or a link to a new resource that does the unpacking could be used instead.

Regards,
Brian




From owner-atom-syntax@mail.imc.org  Mon Oct  6 20:24:33 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A93213A6B4A
	for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  6 Oct 2008 20:24:33 -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 ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ePMNtplBYWws
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Mon,  6 Oct 2008 20:24:33 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 724523A6B4B
	for <atompub-archive@ietf.org>; Mon,  6 Oct 2008 20:24:32 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m973FNKX024024
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 6 Oct 2008 20:15:23 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m973FNWj024023;
	Mon, 6 Oct 2008 20:15:23 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from asmtpout022.mac.com (asmtpout022.mac.com [17.148.16.97])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m973FCCG024011
	for <atom-syntax@imc.org>; Mon, 6 Oct 2008 20:15:23 -0700 (MST)
	(envelope-from andrewdasilva@mac.com)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Received: from [192.168.1.145]
 (poste34-61.residences.ulaval.ca [132.203.61.34]) by asmtp022.mac.com
 (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug  7 2008; 32bit))
 with ESMTPA id <0K8C00IK4MDBSR40@asmtp022.mac.com> for atom-syntax@imc.org;
 Mon, 06 Oct 2008 20:15:12 -0700 (PDT)
Message-id: <1C1D116F-9BB2-4B4D-9C21-2965324C0848@mac.com>
From: Andrew da Silva <andrewdasilva@mac.com>
To: atom-syntax@imc.org
Subject: Exporting a blog using Atom
Date: Mon, 06 Oct 2008 23:15:11 -0400
X-Mailer: Apple Mail (2.929.2)
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>


Hi guys and gals,

Would you recommend using Atom to export other things than entries,  
comments or logs?

I was hoping to use Atom to export blog options, users/groups,  
permissions, tags, etc...

Of course, I want the document to be valid Atom.

While talking with Geoffrey Sneddon, he suggested using several Atom  
documents, makes sense.

Here's an example of a table structure we use:

name - string
type - integer
value - string

The goal is to be able to fully export a blog either to migrate,  
upgrade or backup...

Thanks!

Andrew da Silva



From owner-atom-syntax@mail.imc.org  Thu Oct  9 10:36:36 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD1CA3A67DD
	for <ietfarch-atompub-archive@core3.amsl.com>; Thu,  9 Oct 2008 10:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.355
X-Spam-Level: 
X-Spam-Status: No, score=-2.355 tagged_above=-999 required=5
	tests=[AWL=-0.244, BAYES_05=-1.11, RCVD_IN_DNSWL_LOW=-1]
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 ASEP68cqh1SV
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Thu,  9 Oct 2008 10:36:35 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id E66E33A686D
	for <atompub-archive@ietf.org>; Thu,  9 Oct 2008 10:36:34 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m99HSdje081184
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 9 Oct 2008 10:28:39 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m99HSdn3081182;
	Thu, 9 Oct 2008 10:28:39 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m99HSRFw081156
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <atom-syntax@imc.org>; Thu, 9 Oct 2008 10:28:38 -0700 (MST)
	(envelope-from brian@briansmith.org)
Received: from T60 (unknown [70.252.164.83])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by smtp.mxes.net (Postfix) with ESMTP id 206C623E3F3;
	Thu,  9 Oct 2008 13:28:26 -0400 (EDT)
From: "Brian Smith" <brian@briansmith.org>
To: "'Andrew da Silva'" <andrewdasilva@mac.com>, <atom-syntax@imc.org>
References: <1C1D116F-9BB2-4B4D-9C21-2965324C0848@mac.com>
Subject: RE: Exporting a blog using Atom
Date: Thu, 9 Oct 2008 12:28:26 -0500
Message-ID: <89756D7270A846A3B78FFAE00381E8C7@T60>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1C1D116F-9BB2-4B4D-9C21-2965324C0848@mac.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AckoK2IFNMg4U5qKTum49wrnq0NYYgCB7t+Q
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>


Andrew da Silva wrote:
> Would you recommend using Atom to export other things than 
> entries, comments or logs?
> 
> I was hoping to use Atom to export blog options, 
> users/groups, permissions, tags, etc...

I am building weblogging software that stores everything in AtomPub
collections--comments, entries, settings, pictures, attachments, templates,
etc. So, it is definitely possible for backup/restore purposes for a given
software package. For import/export between different software packages,
blogging packages *should* (IMO) be able to import/export entries and
comments as Atom feeds but many don't do a good job doing it. Besides
entries and comments, Atom is less useful because there are not standards
for encoding settings, and many settings applicable for package A (e.g.
WordPress) are not applicable to package B (e.g. Moveable Type). 

Regards,
Brian



From owner-atom-syntax@mail.imc.org  Thu Oct  9 13:59:04 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9A0A3A68CD
	for <ietfarch-atompub-archive@core3.amsl.com>; Thu,  9 Oct 2008 13:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6,
	RCVD_IN_DNSWL_MED=-4]
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 0SdgGqEPVJGw
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Thu,  9 Oct 2008 13:59:03 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 3E7353A682A
	for <atompub-archive@ietf.org>; Thu,  9 Oct 2008 13:59:02 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m99KoJjH008041
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 9 Oct 2008 13:50:19 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m99KoJOt008040;
	Thu, 9 Oct 2008 13:50:19 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m99Ko8C3008025
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <atom-syntax@imc.org>; Thu, 9 Oct 2008 13:50:19 -0700 (MST)
	(envelope-from brunet@us.ibm.com)
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227])
	by e38.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id m99Knaev023167
	for <atom-syntax@imc.org>; Thu, 9 Oct 2008 14:49:36 -0600
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id m99Ko3tw153086
	for <atom-syntax@imc.org>; Thu, 9 Oct 2008 14:50:04 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m99Ko3Qg010498
	for <atom-syntax@imc.org>; Thu, 9 Oct 2008 14:50:03 -0600
Received: from d03nm116.boulder.ibm.com (d03nm116.boulder.ibm.com [9.17.195.142])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m99Ko2JC010479
	for <atom-syntax@imc.org>; Thu, 9 Oct 2008 14:50:02 -0600
To: atom-syntax@imc.org
MIME-Version: 1.0
Subject: Fw: link rel="search"
X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006
From: Pete Brunet <brunet@us.ibm.com>
Message-ID: <OFFCC97BBD.062A0649-ON862574DD.007262F0-862574DD.007272E9@us.ibm.com>
Date: Thu, 9 Oct 2008 15:50:01 -0500
X-MIMETrack: Serialize by Router on D03NM116/03/M/IBM(Build V85_M2_08202008HFIGS1|August
 20, 2008) at 10/09/2008 14:50:02,
	Serialize complete at 10/09/2008 14:50:02
Content-Type: multipart/alternative; boundary="=_alternative 00727279862574DD_="
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>


This is a multipart message in MIME format.
--=_alternative 00727279862574DD_=
Content-Type: text/plain; charset="US-ASCII"

I didn't see a response to this question...

----- Forwarded by Pete Brunet/Austin/IBM on 10/09/2008 03:49 PM -----

Pete Brunet/Austin/IBM@IBMUS 
Sent by: owner-atom-syntax@mail.imc.org
07/10/2008 04:05 PM

To
atom-syntax@imc.org
cc

Subject
link rel="search"







I see OpenSearch uses a link rel value of "search", but I don't see 
"search" in the RFC4287 spec 

7.1 Registry of Link Relations 
This registry is maintained by IANA and initially contains five values: 
"alternate", "related", "self", "enclosure", and "via". New assignments 
are subject to IESG Approval 

What is the status of the "search" rel value? 

Example: 
   <link rel="search" 
         href="http://example.com/opensearchdescription.xml" 
         type="application/opensearchdescription+xml" 
         title="Content Search" /> 

Pete Brunet
                                                                         
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G
--=_alternative 00727279862574DD_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 color=#2f2f2f face="sans-serif">I didn't see a response
to this question...</font><font size=1 color=#2f2f2f face="Arial"><br>
</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Pete
Brunet/Austin/IBM on 10/09/2008 03:49 PM -----</font>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Pete Brunet/Austin/IBM@IBMUS</b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-atom-syntax@mail.imc.org</font>
<p><font size=1 face="sans-serif">07/10/2008 04:05 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">atom-syntax@imc.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">link rel=&quot;search&quot;</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
I see OpenSearch uses a link rel value of &quot;search&quot;, but I don't
see &quot;search&quot; in the RFC4287 spec</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
7.1 Registry of Link Relations</font><font size=3> </font><font size=2 face="sans-serif"><br>
This registry is maintained by IANA and initially contains five values:
&quot;alternate&quot;, &quot;related&quot;, &quot;self&quot;, &quot;enclosure&quot;,
and &quot;via&quot;. New assignments are subject to IESG Approval</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
What is the status of the &quot;search&quot; rel value?</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
Example:</font><font size=3> </font><font size=2 face="sans-serif"><br>
 &nbsp; &lt;link rel=&quot;search&quot;</font><font size=3> </font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp; href=&quot;http://example.com/opensearchdescription.xml&quot;
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; type=&quot;application/opensearchdescription+xml&quot;
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; title=&quot;Content Search&quot; /&gt;</font><font size=3>
</font><font size=2 face="sans-serif"><br>
</font><font size=1 color=#0060a0 face="Arial"><b><br>
Pete Brunet</b></font><font size=3 color=#0060a0><strike><br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; </strike></font><font size=1 color=#2f2f2f face="Arial"><br>
IBM Accessibility Architecture and Development<br>
11501 Burnet Road, MS 9022E004, Austin, TX 78758<br>
Voice: (512) 838-4594, Cell: (512) 689-4155<br>
Ionosphere: WS4G</font>
--=_alternative 00727279862574DD_=--



From owner-atom-syntax@mail.imc.org  Thu Oct  9 14:20:43 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 569463A692B
	for <ietfarch-atompub-archive@core3.amsl.com>; Thu,  9 Oct 2008 14:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,
	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 8CQoshA9CVbp
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Thu,  9 Oct 2008 14:20:42 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id EC28A3A688F
	for <atompub-archive@ietf.org>; Thu,  9 Oct 2008 14:20:41 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m99LAB6v009591
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 9 Oct 2008 14:10:11 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m99LABBv009590;
	Thu, 9 Oct 2008 14:10:11 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by balder-227.proper.com (8.14.2/8.14.2) with SMTP id m99L9xC9009556
	for <atom-syntax@imc.org>; Thu, 9 Oct 2008 14:10:09 -0700 (MST)
	(envelope-from pagaltzis@gmx.de)
Received: (qmail invoked by alias); 09 Oct 2008 21:09:57 -0000
Received: from static-87-79-236-202.netcologne.de (EHLO klangraum) [87.79.236.202]
  by mail.gmx.net (mp038) with SMTP; 09 Oct 2008 23:09:57 +0200
X-Authenticated: #163624
X-Provags-ID: V01U2FsdGVkX187XakDCL07DfW4kXjudLMoT+9Agwi+R1bjLQykEY
	pe3SBVyeyAvg4Y
Date: Thu, 9 Oct 2008 23:09:56 +0200
From: Aristotle Pagaltzis <pagaltzis@gmx.de>
To: atom-syntax@imc.org
Subject: Re: Exporting a blog using Atom
Message-ID: <20081009210956.GF14834@klangraum.plasmasturm.org>
Mail-Followup-To: atom-syntax@imc.org
References: <1C1D116F-9BB2-4B4D-9C21-2965324C0848@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1C1D116F-9BB2-4B4D-9C21-2965324C0848@mac.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.67
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>


* Andrew da Silva <andrewdasilva@mac.com> [2008-10-07 05:25]:
> Would you recommend using Atom to export other things than
> entries, comments or logs?

Depends on how far you want to go. I see no reason to do it;
neither do I see any reason not to. The only good argument in
favour that I can think of is that you could export the entire
weblog to a single file, but then you also have images and other
binary files, and then it makes more sense to export as a zip
file, at which point you can just as well put the configuration
in a separate file of its own within the zip archive.

> Here's an example of a table structure we use:
>
> name - string
> type - integer
> value - string
>
> The goal is to be able to fully export a blog either to
> migrate, upgrade or backup...

If I were to keep the settings inside Atom, Iâ€™d probably make a
special Entry to contain the configuration, and would use XOXO as
the basis for the format of its content. I think. I dunno, tho.

You could also have the configuration in an extension element
thatâ€™s part of the feed metadata. That would make sure that
trying to import the feed into a *different* weblogging system
wonâ€™t create a spurious posting with computer gibberish in it.

Then again maybe you *want* it to be inspectable.

There are a million ways to approach this, and each of them is
better at different things. It really depends on your goals.

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>



From owner-atom-syntax@mail.imc.org  Thu Oct  9 15:04:44 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C14FD3A6A48
	for <ietfarch-atompub-archive@core3.amsl.com>; Thu,  9 Oct 2008 15:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.061
X-Spam-Level: 
X-Spam-Status: No, score=-1.061 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001,
	J_CHICKENPOX_21=0.6, SARE_MILLIONSOF=0.315]
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 E9B1LpqeKpen
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Thu,  9 Oct 2008 15:04:43 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 6EFDC3A67D0
	for <atompub-archive@ietf.org>; Thu,  9 Oct 2008 15:04:42 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m99LvYI5013303
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 9 Oct 2008 14:57:34 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m99LvYl9013302;
	Thu, 9 Oct 2008 14:57:34 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.181])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m99LvNG6013283
	for <atom-syntax@imc.org>; Thu, 9 Oct 2008 14:57:33 -0700 (MST)
	(envelope-from dewitt@unto.net)
Received: by el-out-1112.google.com with SMTP id v27so92291ele.13
        for <atom-syntax@imc.org>; Thu, 09 Oct 2008 14:57:23 -0700 (PDT)
Received: by 10.151.42.6 with SMTP id u6mr891965ybj.39.1223589442875;
        Thu, 09 Oct 2008 14:57:22 -0700 (PDT)
Received: by 10.65.95.6 with HTTP; Thu, 9 Oct 2008 14:57:22 -0700 (PDT)
Message-ID: <77facc500810091457k12cce624w945cd57302c2acb2@mail.gmail.com>
Date: Thu, 9 Oct 2008 14:57:22 -0700
From: "DeWitt Clinton" <dewitt@unto.net>
To: "Pete Brunet" <brunet@us.ibm.com>
Subject: Re: Fw: link rel="search"
Cc: atom-syntax@imc.org
In-Reply-To: <OFFCC97BBD.062A0649-ON862574DD.007262F0-862574DD.007272E9@us.ibm.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_59706_28087573.1223589442854"
References: <OFFCC97BBD.062A0649-ON862574DD.007262F0-862574DD.007272E9@us.ibm.com>
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>


------=_Part_59706_28087573.1223589442854
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Frank Ellermann has a work-in-progress draft for the registration of
rel="search".  It hasn't been submitted yet, so nothing has been registered,
of course.

  http://www.ietf.org/internet-drafts/draft-ellermann-opensearch-01.txt

That said, there are on the order of millions of pages and/or atom feeds
with rel="search" on the web, and that link relation is included in the
HTML5 draft [1], so I'd be surprised if that registration were to be
rejected.

[1] http://www.w3.org/html/wg/html5/#link-type-search

-DeWitt

On Thu, Oct 9, 2008 at 1:50 PM, Pete Brunet <brunet@us.ibm.com> wrote:

>
> I didn't see a response to this question...
>
> ----- Forwarded by Pete Brunet/Austin/IBM on 10/09/2008 03:49 PM -----
>  *Pete Brunet/Austin/IBM@IBMUS*
> Sent by: owner-atom-syntax@mail.imc.org
>
> 07/10/2008 04:05 PM
>   To
> atom-syntax@imc.org  cc
>   Subject
> link rel="search"
>
>
>
>
>
> I see OpenSearch uses a link rel value of "search", but I don't see
> "search" in the RFC4287 spec
>
> 7.1 Registry of Link Relations
> This registry is maintained by IANA and initially contains five values:
> "alternate", "related", "self", "enclosure", and "via". New assignments are
> subject to IESG Approval
>
> What is the status of the "search" rel value?
>
> Example:
>   <link rel="search"
>         href="http://example.com/opensearchdescription.xml"
>         type="application/opensearchdescription+xml"
>         title="Content Search" />
> *
> Pete Brunet*
>
> IBM Accessibility Architecture and Development
> 11501 Burnet Road, MS 9022E004, Austin, TX 78758
> Voice: (512) 838-4594, Cell: (512) 689-4155
> Ionosphere: WS4G

------=_Part_59706_28087573.1223589442854
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Frank Ellermann has a work-in-progress draft for the registration of rel=&quot;search&quot;.&nbsp; It hasn&#39;t been submitted yet, so nothing has been registered, of course.<br><br>&nbsp; <a href="http://www.ietf.org/internet-drafts/draft-ellermann-opensearch-01.txt">http://www.ietf.org/internet-drafts/draft-ellermann-opensearch-01.txt</a><br>
<br>That said, there are on the order of millions of pages and/or atom feeds with rel=&quot;search&quot; on the web, and that link relation is included in the HTML5 draft [1], so I&#39;d be surprised if that registration were to be rejected.<br>
<br>[1] <a href="http://www.w3.org/html/wg/html5/#link-type-search">http://www.w3.org/html/wg/html5/#link-type-search</a><br><br>-DeWitt<br><br><div class="gmail_quote">On Thu, Oct 9, 2008 at 1:50 PM, Pete Brunet <span dir="ltr">&lt;<a href="mailto:brunet@us.ibm.com">brunet@us.ibm.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font color="#2f2f2f" face="sans-serif" size="2">I didn&#39;t see a response
to this question...</font><font color="#2f2f2f" face="Arial" size="1"><br>
</font>
<br><font color="#800080" face="sans-serif" size="1">----- Forwarded by Pete
Brunet/Austin/IBM on 10/09/2008 03:49 PM -----</font>
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="40%"><font face="sans-serif" size="1"><b>Pete Brunet/Austin/IBM@IBMUS</b>
</font>
<br><font face="sans-serif" size="1">Sent by: <a href="mailto:owner-atom-syntax@mail.imc.org" target="_blank">owner-atom-syntax@mail.imc.org</a></font>
<p><font face="sans-serif" size="1">07/10/2008 04:05 PM</font>
</p></td><td width="59%">
<table width="100%">
<tbody><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">To</font></div>
</td><td><font face="sans-serif" size="1"><a href="mailto:atom-syntax@imc.org" target="_blank">atom-syntax@imc.org</a></font>
</td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">cc</font></div>
</td><td>
</td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">Subject</font></div>
</td><td><font face="sans-serif" size="1">link rel=&quot;search&quot;</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign="top">
<td>
</td><td></td></tr></tbody></table>
<br></td></tr></tbody></table>
<br>
<br>
<br><font face="sans-serif" size="2"><br>
I see OpenSearch uses a link rel value of &quot;search&quot;, but I don&#39;t
see &quot;search&quot; in the RFC4287 spec</font><font size="3"> <br>
</font><font face="sans-serif" size="2"><br>
7.1 Registry of Link Relations</font><font size="3"> </font><font face="sans-serif" size="2"><br>
This registry is maintained by IANA and initially contains five values:
&quot;alternate&quot;, &quot;related&quot;, &quot;self&quot;, &quot;enclosure&quot;,
and &quot;via&quot;. New assignments are subject to IESG Approval</font><font size="3">
<br>
</font><font face="sans-serif" size="2"><br>
What is the status of the &quot;search&quot; rel value?</font><font size="3">
<br>
</font><font face="sans-serif" size="2"><br>
Example:</font><font size="3"> </font><font face="sans-serif" size="2"><br>
 &nbsp; &lt;link rel=&quot;search&quot;</font><font size="3"> </font><font face="sans-serif" size="2"><br>
 &nbsp; &nbsp; &nbsp; &nbsp; href=&quot;<a href="http://example.com/opensearchdescription.xml" target="_blank">http://example.com/opensearchdescription.xml</a>&quot;
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; type=&quot;application/opensearchdescription+xml&quot;
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; title=&quot;Content Search&quot; /&gt;</font><font size="3">
</font><font face="sans-serif" size="2"><br>
</font><font color="#0060a0" face="Arial" size="1"><b><br>
Pete Brunet</b></font><font color="#0060a0" size="3"><strike><br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; </strike></font><font color="#2f2f2f" face="Arial" size="1"><br>
IBM Accessibility Architecture and Development<br>
11501 Burnet Road, MS 9022E004, Austin, TX 78758<br>
Voice: (512) 838-4594, Cell: (512) 689-4155<br>
Ionosphere: WS4G</font></blockquote></div><br></div>

------=_Part_59706_28087573.1223589442854--



From owner-atom-syntax@mail.imc.org  Sun Oct 12 18:54:27 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF69D3A6B4A
	for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 12 Oct 2008 18:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_45=0.6]
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 qeUwa1UexO1s
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Sun, 12 Oct 2008 18:54:27 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 6D3473A69A6
	for <atompub-archive@ietf.org>; Sun, 12 Oct 2008 18:54:26 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9D1k3a8048309
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 12 Oct 2008 18:46:03 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m9D1k3II048308;
	Sun, 12 Oct 2008 18:46:03 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9D1jqad048299
	for <atom-syntax@imc.org>; Sun, 12 Oct 2008 18:46:02 -0700 (MST)
	(envelope-from pjkeane@gmail.com)
Received: by wf-out-1314.google.com with SMTP id 25so1454450wfc.28
        for <atom-syntax@imc.org>; Sun, 12 Oct 2008 18:45:51 -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:sender
         :to:subject:mime-version:content-type:content-transfer-encoding
         :content-disposition:x-google-sender-auth;
        bh=1uGM6NsBQVu/+tk9hX/I3PmJw/RikZVxbwx9VPxmS60=;
        b=nsjksMIAZbBs8ZuoNoJQ4Tv8p61C+zgFN4hp3VnUrc1q3N2hlOUxL7pGhi8Bxns92s
         i1zpzvasDzhWsQY8kqjnkjDj26A6hn+Qciq/OBZ7JxVKRIZUqkDd6hl65LH+Oz0VelEN
         S/dy4AUtDg7yjzJwRMCQp0mNkxst85PCkIfMs=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition:x-google-sender-auth;
        b=QANbX205HSD6eYHe02y1BjKjUXoYwUYrDM3onBSyMythUFYr6N13KPNz81IkvBRJPB
         CEJpuXGFqGU8aMwUuujcH6YSbK52t9Sj2RUISDVbWOSsajchGXw0kOhgV5RNJXPWepUF
         S4tCW/aqv215ip06RzY0YTdSAfpXKDGSCaM+I=
Received: by 10.142.165.14 with SMTP id n14mr2287718wfe.51.1223862351716;
        Sun, 12 Oct 2008 18:45:51 -0700 (PDT)
Received: by 10.142.142.1 with HTTP; Sun, 12 Oct 2008 18:45:51 -0700 (PDT)
Message-ID: <8158ad750810121845y7a84b7f6xe7f86f68a2894d40@mail.gmail.com>
Date: Sun, 12 Oct 2008 20:45:51 -0500
From: "Peter Keane" <pkeane@mail.utexas.edu>
To: atom-syntax@imc.org
Subject: thoughts/opinions about Yahoo's SearchMonkey?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: 22c44b5671b84bd6
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>


Does anyone here in the Atom world have thoughts or opinions about
Yahoo's SearchMonkey and related specs, esp. DataRSS [1]?
SearchMonkey is obviously aimed at improving search for producers and
consumers, but the approach to adding metadata to resources has wide
applicability.  Not that it's the be-all and end-all, but rather
another interesting point of triangulation on the problem(s) that we
are all trying to address.

I keep seeing DataRSS as a more generic MediaRSS (also from Yahoo),
although I am not sure that's an accurate take.  It also looks like a
way to use RDF (by way of RDFa mechanisms) with an Atom feed.  I also
see it as a pretty clean and easily understandable way to add
arbitrary metadata to a link (something which I feel like we need, and
which has been discussed here many times before).

Essentially, you create an "adjunct" extension that live in an
atom:entry. It's repeatable, in that multiple parties can make an
assertion about a particular resource.  By the way, the docs talk
about DataRSS as a "specification for conveying structured data for
URLs," which in the context of SearchMonkey mean that when a
particular URL is turned up in a search result, this adjunct is ready
in the wings to provide the metadata for a nicely presented Google
OneBox style summary.  Within the adjunct, you can have "meta"
elements (key-value pairs describing the adjunct) and/or "items"
(think atom:link) which in turn can have meta elements.
Interestingly, items can contain other items, which makes for a
powerful, if potentially unwieldy structure.

Perhaps to deal with some of that potential explosion of complexity
and non-standard approaches, they offer both a recommended set of
vocabularies to use with DataRSS [2] and a set of sample DataRSS for
various common content types [3].

--peter keane

[1] http://developer.yahoo.com/searchmonkey/smguide/understand_datarss.html
[2] http://developer.yahoo.com/searchmonkey/smguide/profile_vocab.html
[3] http://developer.yahoo.com/searchmonkey/smguide/datarss-examples.html



From owner-atom-syntax@mail.imc.org  Mon Oct 13 21:32:52 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3F413A67E7
	for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 13 Oct 2008 21:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.077
X-Spam-Level: 
X-Spam-Status: No, score=-1.077 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622,
	J_CHICKENPOX_44=0.6, J_CHICKENPOX_45=0.6]
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 8HYWJvpsdB5I
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Mon, 13 Oct 2008 21:32:52 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 98D6A3A6863
	for <atompub-archive@ietf.org>; Mon, 13 Oct 2008 21:32:51 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9E4MPjB041690
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 13 Oct 2008 21:22:25 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m9E4MP8F041689;
	Mon, 13 Oct 2008 21:22:25 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9E4MEn6041667
	for <atom-syntax@imc.org>; Mon, 13 Oct 2008 21:22:25 -0700 (MST)
	(envelope-from pjkeane@gmail.com)
Received: by gxk12 with SMTP id 12so4536964gxk.10
        for <atom-syntax@imc.org>; Mon, 13 Oct 2008 21:22:14 -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:sender
         :to:subject:mime-version:content-type:content-transfer-encoding
         :content-disposition:x-google-sender-auth;
        bh=QZ5aso48aCb6WhePSXCd2EjqrThakM6uqOYfhZBir7U=;
        b=U6g3iQD4j8IIIWgureQeEYTHEt4U742H4nMHvzCSk2VY5c0DCKK5QknKt7hxocLdLd
         wAXk5QuinVL9juu3Qy0XID3l7Cd02B8B9cfXU/JmVHalgCyjzrgybfyJbVBSRuIj0gQn
         wJfgk0X0zA7AEzAhyIqvpiwyRIeqyqLYy+r2U=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition:x-google-sender-auth;
        b=xTW4kSOPY0P644jphx+e6TAvbUcuaepk+ZCE9NOTdW1samJ7rBW27yvj4gr5X/EZ5O
         JMnzsw+CC+0B3KHA9HKqxLu6vV5BiuKNSj4noRqNlyefnn6T9PKLW4+8KDQoJQItMXFx
         0hDHDCsGlYGkgSAtmDm6HeKQ+RsnDg5KW5j38=
Received: by 10.142.44.13 with SMTP id r13mr2626328wfr.230.1223958133863;
        Mon, 13 Oct 2008 21:22:13 -0700 (PDT)
Received: by 10.142.142.1 with HTTP; Mon, 13 Oct 2008 21:22:13 -0700 (PDT)
Message-ID: <8158ad750810132122t50e79b76u86b6146beb0c2e16@mail.gmail.com>
Date: Mon, 13 Oct 2008 23:22:13 -0500
From: "Peter Keane" <pkeane@mail.utexas.edu>
To: "atom-syntax Syntax" <atom-syntax@imc.org>
Subject: Atom simple metadata extension
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: 6c79f989dacd7180
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>


In looking over Yahoo's DataRSS spec (part of SearchMonkey), and after
thinking about Bill DeHora's recent blog posts about JSON and Atom, I
am reminded again how useful it might be to have a simple mechanism to
add arbitrary metadata to an atom:feed, atom:entry, or atom:link.  I
realize this has been addressed in various ways before (esp. James
Snell's link extensions proposal), but deconstructing/simplifying
DataRSS just a bit, we could arrive at a metadata extension:

<x:meta property="[property name -- maybe a CURIE?]">value of the
property</x:meta>

This element would make an assertion about it's containing element,
any of: feed, entry or link.  The property value is always a simple
string.  The property attribute should , I suppose, be a CURIE, but
I'd guess it could be a simple string as well.  In DataRSS they have
an optional "datatype" attribute, that holds a CURIE -- potentially
useful, although I'd probably not use that.

DataRSS uses a containing "adjunct" element, but I'd be happy to leave
that out and assume that metadata assertions are being made by the
creator of the atom feed or entry.  The "item" element in DataRSS is
(as far as I can tell) a surrogate for atom:link, so we don't need
that. The other element DataRSS uses is "type," which this proposal
doesn't address since there are other possible ways to do that in atom
(or not do at all).

It's apparent in the DataRSS docs that they realize the complexity
comes not in the syntax, but in encouraging standard vocabularies and
standard constructs for similar content types.  As people standardize,
more interop results.  In the mean time, Atom can be all that much
more useful for simple applications that just need a bit more metadata
for a specific use case.

I'd be curious to hear thoughts/opinions on this.

--peter keane



From owner-atom-syntax@mail.imc.org  Mon Oct 13 22:11:03 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BB383A6AC8
	for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 13 Oct 2008 22:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5
	tests=[AWL=-3.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 HExXh-1b7bIo
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Mon, 13 Oct 2008 22:11:02 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id C305E3A63CB
	for <atompub-archive@ietf.org>; Mon, 13 Oct 2008 22:11:01 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9E54oSf046003
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 13 Oct 2008 22:04:51 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m9E54oYI046001;
	Mon, 13 Oct 2008 22:04:50 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9E54dGA045984
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <atom-syntax@imc.org>; Mon, 13 Oct 2008 22:04:50 -0700 (MST)
	(envelope-from brian@briansmith.org)
Received: from T60 (unknown [70.255.104.59])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by smtp.mxes.net (Postfix) with ESMTP id E96FC23E3E1;
	Tue, 14 Oct 2008 01:04:38 -0400 (EDT)
From: "Brian Smith" <brian@briansmith.org>
To: "'Peter Keane'" <pkeane@mail.utexas.edu>,
        "'atom-syntax Syntax'" <atom-syntax@imc.org>
References: <8158ad750810132122t50e79b76u86b6146beb0c2e16@mail.gmail.com>
Subject: RE: Atom simple metadata extension
Date: Tue, 14 Oct 2008 00:04:34 -0500
Message-ID: <45BF919842774B9F9AF470B7848CE541@T60>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <8158ad750810132122t50e79b76u86b6146beb0c2e16@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AckttNGPw8D9d7Z/QZuWnu+2tUfxYAABF5PA
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>


> <x:meta property="[property name -- maybe a CURIE?]">value of the
> property</x:meta>
> 
> This element would make an assertion about it's containing element,
> any of: feed, entry or link.  The property value is always a simple
> string.  The property attribute should , I suppose, be a CURIE, but
> I'd guess it could be a simple string as well.

That is exactly what a simple extension element does. RFC 4287, Section
6.4.1: "The element can be interpreted as a simple property (or name/value
pair) of the parent element that encloses it."

<ns:property-name>value of the property</ns:property-name>

- Brian



From owner-atom-syntax@mail.imc.org  Tue Oct 14 04:59:43 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 11DE03A67EE
	for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 14 Oct 2008 04:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level: 
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5
	tests=[AWL=-0.525, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622,
	J_CHICKENPOX_44=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_46=0.6]
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 rylFlU3WdiNj
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Tue, 14 Oct 2008 04:59:37 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 2FBBB3A67EA
	for <atompub-archive@ietf.org>; Tue, 14 Oct 2008 04:59:36 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9EBpfjH085449
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 14 Oct 2008 04:51:41 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m9EBpfcO085448;
	Tue, 14 Oct 2008 04:51:41 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9EBpTo1085407
	for <atom-syntax@imc.org>; Tue, 14 Oct 2008 04:51:40 -0700 (MST)
	(envelope-from pjkeane@gmail.com)
Received: by wf-out-1314.google.com with SMTP id 25so2054474wfc.28
        for <atom-syntax@imc.org>; Tue, 14 Oct 2008 04:51:29 -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:sender
         :to:subject:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references
         :x-google-sender-auth;
        bh=G6XIAK/MyB3pxnq2iGlWFBJuhh3/HKAX2W/S2sSEYsY=;
        b=dmZvy/S8fskGEHnqTOxTH4YlPyNc8RNGIijhGNQKMDGsrEUHIH1sbCePea4nii2qcU
         jrmQ9W8ewj0hQG6/80YUx9ow1DgCgWGUfiX/ZEptnez8U6/k5DYehMvwl691iJgG6/nf
         1tk2V8Q2GHmcrllaRZgVGEQrMFuxy6KZwt/oA=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=qLDWFSliO3kX2ausNbnQKavBkXUGRBBwO0GT/8V4QID809nD230nz7z6DEhfflO4nV
         eoeEHsssMNpreIZSVXhjO2EzbnZAd8CWyMrWbQ22XasiLCKLWdY6OwQ0fF67V3V5RPeC
         xhmrEt9uTG3I8VFtSAYCvNWVRIkukutjZERnk=
Received: by 10.142.43.19 with SMTP id q19mr3339839wfq.54.1223985089038;
        Tue, 14 Oct 2008 04:51:29 -0700 (PDT)
Received: by 10.142.142.1 with HTTP; Tue, 14 Oct 2008 04:51:29 -0700 (PDT)
Message-ID: <8158ad750810140451r48f1319euedfeb6c4f3632f97@mail.gmail.com>
Date: Tue, 14 Oct 2008 06:51:29 -0500
From: "Peter Keane" <pkeane@mail.utexas.edu>
To: "atom-syntax Syntax" <atom-syntax@imc.org>
Subject: Re: Atom simple metadata extension
In-Reply-To: <8158ad750810140449u987ed0co6d50700f3ce8f698@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <8158ad750810132122t50e79b76u86b6146beb0c2e16@mail.gmail.com>
	 <45BF919842774B9F9AF470B7848CE541@T60>
	 <8158ad750810140449u987ed0co6d50700f3ce8f698@mail.gmail.com>
X-Google-Sender-Auth: 34d228c8b4b1c662
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>


 On Tue, Oct 14, 2008 at 12:04 AM, Brian Smith <brian@briansmith.org> wrote:
>> <x:meta property="[property name -- maybe a CURIE?]">value of the
>> property</x:meta>
>>
>> This element would make an assertion about it's containing element,
>> any of: feed, entry or link.  The property value is always a simple
>> string.  The property attribute should , I suppose, be a CURIE, but
>> I'd guess it could be a simple string as well.
>
> That is exactly what a simple extension element does. RFC 4287, Section
> 6.4.1: "The element can be interpreted as a simple property (or name/value
> pair) of the parent element that encloses it."

 In 6.4 it states "Child elements of atom:entry, atom:feed,
 atom:source, and Person constructs are considered Metadata elements
 and are described below."  Would it be an acceptable practice to do
 the same w/ an atom:link?  e.g.,

  <atom:link rel="related" href="http://example.com/etc">
        <ns:property-name>value of property</ns:property-name>
 </link>

--peter

>
> <ns:property-name>value of the property</ns:property-name>
>
> - Brian
>



From owner-atom-syntax@mail.imc.org  Fri Oct 31 03:57:56 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CD853A682A
	for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 31 Oct 2008 03:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 Ur2aOGouJfVF
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Fri, 31 Oct 2008 03:57:55 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id E3A3E3A6835
	for <atompub-archive@ietf.org>; Fri, 31 Oct 2008 03:57:51 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9VAmCnc092368
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 03:48:12 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m9VAmCnX092367;
	Fri, 31 Oct 2008 03:48:12 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9VAlxxU092328
	(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO)
	for <atom-syntax@imc.org>; Fri, 31 Oct 2008 03:48:11 -0700 (MST)
	(envelope-from ga-atom-syntax@gmane.org)
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1KvrXm-0001GA-Ks
	for atom-syntax@imc.org; Fri, 31 Oct 2008 10:47:54 +0000
Received: from 81-67-87-178.rev.numericable.fr ([81.67.87.178])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <atom-syntax@imc.org>; Fri, 31 Oct 2008 10:47:54 +0000
Received: from jerome.louvel by 81-67-87-178.rev.numericable.fr with local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <atom-syntax@imc.org>; Fri, 31 Oct 2008 10:47:54 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: atom-syntax@imc.org
From:  Jerome Louvel <jerome.louvel@noelios.com>
Subject:  [ANN] Restlet 1.1 released with better Atom syntax support
Date:  Fri, 31 Oct 2008 11:47:45 +0100
Lines: 16
Message-ID: <geenof$qou$1@ger.gmane.org>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  8bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: 81-67-87-178.rev.numericable.fr
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
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>


Hi all,

We've just released Restlet 1.1.0 with better Atom support. See full 
announce here:
http://blog.noelios.com/2008/10/28/restlet-110-released/

We are now compatible with Atom syntax format 1.0 and can now handle 
both parsing and generation of Atom feeds. See our Atom extension:
http://www.restlet.org/documentation/1.1/ext/index.html?org/restlet/ext/atom/package-summary.html 


Best regards,
Jérôme Louvel
-- 
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com



From owner-atom-syntax@mail.imc.org  Fri Oct 31 04:45:51 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 782F23A6B74
	for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 31 Oct 2008 04:45:51 -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 ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OKTvzsn0x7Uh
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Fri, 31 Oct 2008 04:45:50 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id B0E4F3A6AFD
	for <atompub-archive@ietf.org>; Fri, 31 Oct 2008 04:45:48 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9VBcWbd001350
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 04:38:32 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m9VBcWjp001347;
	Fri, 31 Oct 2008 04:38:32 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from yx-out-1718.google.com (yx-out-1718.google.com [74.125.44.152])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9VBcJsp001302;
	Fri, 31 Oct 2008 04:38:30 -0700 (MST)
	(envelope-from t.broyer@gmail.com)
Received: by yx-out-1718.google.com with SMTP id 36so488749yxh.4
        for <multiple recipients>; Fri, 31 Oct 2008 04:38:19 -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:to
         :subject:cc:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references;
        bh=4hP1EpWfut4ZC+HINoHV8HIlVnDeMRimPyyZSBkR2xk=;
        b=QA3rxeb2HoCe8U2H24Wq1LhyZIpWsma9dNkwMKhi/pd79/z4L+RaN/BtD7YmvZ9kbM
         po6Z+MSmrlhmuD4aYylz2LR56SkOSGha37xXVXC9jdgfzIt/S06gDNRkWQ2fTiOHyvAN
         eYYQizrivGpI63ixnWLk4zzgqFgMhy7epLaxQ=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=JTSQ5kIxrdn/z0KbRzpjiwzDPFXokwNyWkbfuswzJm9TJIQjdNFWtnIGqHQOVkDRSa
         CXxKvZjZyXpJY7MCEhBx31GV8Gp9vCvNWXWkz0CqDmQE9baEM/F7QroPWd7V4Tj4qqtd
         Tfym5dk5Ny1WUO2INkpG5zPMfg0o+Ek9B1GAI=
Received: by 10.64.196.9 with SMTP id t9mr12992663qbf.66.1225453098951;
        Fri, 31 Oct 2008 04:38:18 -0700 (PDT)
Received: by 10.65.231.1 with HTTP; Fri, 31 Oct 2008 04:38:18 -0700 (PDT)
Message-ID: <a9699fd20810310438o1a2e9aa2r608a11add60c8879@mail.gmail.com>
Date: Fri, 31 Oct 2008 12:38:18 +0100
From: "Thomas Broyer" <t.broyer@gmail.com>
To: "Jerome Louvel" <jerome.louvel@noelios.com>
Subject: Re: [ANN] Restlet 1.1 released with better Atom syntax support
Cc: atom-syntax@imc.org, "Atom-Protocol Protocol" <atom-protocol@imc.org>
In-Reply-To: <geenof$qou$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <geenof$qou$1@ger.gmane.org>
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>


On Fri, Oct 31, 2008 at 11:47 AM, Jerome Louvel wrote:
>
> We've just released Restlet 1.1.0 with better Atom support. See full
> announce here:
> http://blog.noelios.com/2008/10/28/restlet-110-released/
>
> We are now compatible with Atom syntax format 1.0 and can now handle both
> parsing and generation of Atom feeds.

Any reason you're not using Abdera? It looks much more flexible (i.e.
support for extension elements)

-- 
Thomas Broyer



From owner-atom-syntax@mail.imc.org  Fri Oct 31 06:53:24 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 87DF13A6BCB
	for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 31 Oct 2008 06:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5
	tests=[AWL=-0.757, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311]
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 2DVfYHmLXCoL
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Fri, 31 Oct 2008 06:53:23 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 179C03A6BFF
	for <atompub-archive@ietf.org>; Fri, 31 Oct 2008 06:53:22 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9VDjAr2024397
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 06:45:10 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m9VDjAVG024395;
	Fri, 31 Oct 2008 06:45:10 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from alaska.noelios.com (ns22644.ovh.net [91.121.6.62])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9VDiv5l024346
	(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 06:45:09 -0700 (MST)
	(envelope-from jerome.louvel@noelios.com)
Received: from 81-67-87-178.rev.numericable.fr ([81.67.87.178] helo=colorado)
	by alaska.noelios.com with esmtpsa (TLS-1.0:RSA_ARCFOUR_MD5:16)
	(Exim 4.63)
	(envelope-from <jerome.louvel@noelios.com>)
	id 1KvuIx-0003hb-Pp; Fri, 31 Oct 2008 14:44:57 +0100
From: "Jerome Louvel" <jerome.louvel@noelios.com>
To: "'Thomas Broyer'" <t.broyer@gmail.com>
Cc: <atom-syntax@imc.org>, "'Atom-Protocol Protocol'" <atom-protocol@imc.org>
References: <geenof$qou$1@ger.gmane.org> <a9699fd20810310438o1a2e9aa2r608a11add60c8879@mail.gmail.com>
Date: Fri, 31 Oct 2008 14:44:44 +0100
Message-ID: <E1963019B4EA47259DAF17868E015626@colorado>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <a9699fd20810310438o1a2e9aa2r608a11add60c8879@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: Ack7TTCPGE1nRXilS/+b7tG79Uch5wAEPLvw
X-SA-Exim-Connect-IP: 81.67.87.178
X-SA-Exim-Mail-From: jerome.louvel@noelios.com
X-Spam-Relay: 
Subject: RE: [ANN] Restlet 1.1 released with better Atom syntax support
X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000)
X-SA-Exim-Scanned: Yes (on alaska.noelios.com)
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>



Hi Thomas,

We started our Atom extension during Restlet 1.0 development and I'm not =
sure Abdera existed at that time. Our goal is also much more modest on =
this front than Abdera. Finally, the ability to leverage the Restlet API =
makes the extension very light in term of code size.

However, once Abdera reaches 1.0, we could be interested to consider =
adding an extension for it to Restlet. But maybe it would make more =
sense for Abdera to leverage the Restlet API internally or to provide =
support for it?=20

Best regards,
J=C3=A9r=C3=B4me Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


-----Message d'origine-----
De : Thomas Broyer [mailto:t.broyer@gmail.com]=20
Envoy=C3=A9 : vendredi 31 octobre 2008 12:38
=C3=80 : Jerome Louvel
Cc : atom-syntax@imc.org; Atom-Protocol Protocol
Objet : Re: [ANN] Restlet 1.1 released with better Atom syntax support

On Fri, Oct 31, 2008 at 11:47 AM, Jerome Louvel wrote:
>
> We've just released Restlet 1.1.0 with better Atom support. See full
> announce here:
> http://blog.noelios.com/2008/10/28/restlet-110-released/
>
> We are now compatible with Atom syntax format 1.0 and can now handle =
both
> parsing and generation of Atom feeds.

Any reason you're not using Abdera? It looks much more flexible (i.e.
support for extension elements)

--=20
Thomas Broyer



From owner-atom-syntax@mail.imc.org  Fri Oct 31 15:18:21 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8ECB13A6AAB
	for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 31 Oct 2008 15:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
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 BV4-tWYKnr85
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Fri, 31 Oct 2008 15:18:20 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 445A03A6839
	for <atompub-archive@ietf.org>; Fri, 31 Oct 2008 15:18:19 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9VMAqc6027359
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 15:10:53 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id m9VMAqrx027356;
	Fri, 31 Oct 2008 15:10:52 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from rgminet01.oracle.com (rgminet01.oracle.com [148.87.113.118])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m9VMAf96027282
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 15:10:51 -0700 (MST)
	(envelope-from nikunj.mehta@oracle.com)
Received: from agmgw2.us.oracle.com (agmgw2.us.oracle.com [152.68.180.213])
	by rgminet01.oracle.com (Switch-3.2.4/Switch-3.2.4) with ESMTP id m9VMAd4a008510;
	Fri, 31 Oct 2008 16:10:39 -0600
Received: from acsmt705.oracle.com (acsmt705.oracle.com [141.146.40.83])
	by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m9VMAcMC030551;
	Fri, 31 Oct 2008 16:10:39 -0600
Received: from [144.25.174.33] (/144.25.174.33)
	by default (Oracle Beehive Gateway v4.0)
	with ESMTP ; Fri, 31 Oct 2008 22:10:38 +0000
Message-ID: <490B826D.6070907@oracle.com>
Date: Fri, 31 Oct 2008 15:10:53 -0700
From: Nikunj Mehta <nikunj.mehta@oracle.com>
Organization: Oracle
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: atom-protocol Protocol <atom-protocol@imc.org>,
        Atom-Syntax <atom-syntax@imc.org>,
        Colm Divilly <colm.divilly@oracle.com>
Subject: draft-divilly-atompub-hierarchy-00
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
X-Whitelist: TRUE
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>


Fellow Atom and AtomPub'bers,

We'd like to discuss the draft below that introduces extensions for Atom 
and AtomPub to deal with hierarchies of feeds and the programmatic 
creation and removal of AtomPub Collections.

This draft defines a mechanism for identifying hierarchical 
master-detail relations among data feeds so that consumer applications 
can perform standard AtomPub operations on them. A hierarchical 
master-detail relation of an Entry to a Feed implies the detail Feed is 
created when the master Entry is created and the Feed is removed when 
the Entry is removed. The Entry is called the "master entry" and the 
Feed is called "detail feed". This relationship allows a client to use 
AtomPub to create a new Collection by posting an Entry to an existing 
Collection.

Comments?

Colm Divilly & Nikunj Mehta

==============================================================

    Title        : Hierarchy Extensions to Atom Feeds
    Author(s)    : C. Divlly and N. Mehta
    Filename    : draft-divilly-atompub-hierarchy-00.txt
    Pages        : 18

This I-D is available at the following URL:
    
http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atompub-hierarchy-00.html 

    
http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atompub-hierarchy-00.txt 



From owner-atom-syntax@mail.imc.org  Fri Oct 31 21:45:58 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE0FD3A69B3
	for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 31 Oct 2008 21:45:58 -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 ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FmINwsueXIfL
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Fri, 31 Oct 2008 21:45:58 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 6BA113A67A1
	for <atompub-archive@ietf.org>; Fri, 31 Oct 2008 21:45:57 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mA14cRLc007057
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 21:38:27 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id mA14cRdR007056;
	Fri, 31 Oct 2008 21:38:27 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mA14cGmX007011
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 21:38:27 -0700 (MST)
	(envelope-from brian@briansmith.org)
Received: from T60 (unknown [70.254.207.136])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by smtp.mxes.net (Postfix) with ESMTP id A24EAD059F;
	Sat,  1 Nov 2008 00:38:10 -0400 (EDT)
From: "Brian Smith" <brian@briansmith.org>
To: <nikunj.mehta@oracle.com>, <atom-protocol@imc.org>, <atom-syntax@imc.org>,
        <colm.divilly@oracle.com>
References: <490B826D.6070907@oracle.com>
In-Reply-To: <490B826D.6070907@oracle.com>
Subject: RE: draft-divilly-atompub-hierarchy-00
Date: Fri, 31 Oct 2008 23:37:47 -0500
Message-ID: <000001c93bdb$a744f280$f5ced780$@org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ack7pdNzR0jfp0HhSlmUoL8TNnuafgAK9WpQ
Content-Language: en-us
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>


Nikunj Mehta wrote:
> We'd like to discuss the draft below that introduces extensions for
> Atom and AtomPub to deal with hierarchies of feeds and the
> programmatic creation and removal of AtomPub Collections.
> 
> Comments?

What do you think about the search-based mechanism that I suggested in the
most recent "Hierarchical Collections" thread? It can be seen as a
simplified, specialized version of CMIS's query mechanism (in fact, I think
it can be implemented in terms of CMIS queries). I will repeat the
description of the mechanism below using your terminology:

* Link relation "master": When an entry A links to another entry B with the
"master" link relation, entry A is considered to exist only while entry B
exists. To add a detail entry to B, post an entry containing a "master" link
referencing B to the same collection that B is in.

* URI template "details" with one parameters "entry". The "details" URI
template describes a set of feeds. Each feed holds all the entries from the
collection that link to the given entry using the "master" link relation.
    Example:
       http://example.org/collection/with-link/rel=part-of&href={entry}

* A means of associating a named URI template with a feed. Somebody
suggested a <link-template> extension for this, and I will use that:
    <feed ...>
       <link-template rel='details'
template='./with-link/rel=part-of&href={entry}'/>
       ...
    </feed>

Given this, you can implement all the functionality from your draft, as far
as I can tell.
 
If you add a third parameter "depth", you can search the containment
hierarchy transitively in a very small number of requests, with duplicates
automatically filtered out. It seems like the master-detail mechanism you
describe requires a very large number of requests to find the transitive
closure.

Plus, the URI template query mechanism easily generalizes to other relations
besides master-detail.

Regards,
Brian




From owner-atom-syntax@mail.imc.org  Fri Oct 31 22:43:04 2008
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@core3.amsl.com
Delivered-To: ietfarch-atompub-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8908C3A684E
	for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 31 Oct 2008 22:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.177
X-Spam-Level: 
X-Spam-Status: No, score=-0.177 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_37=0.6,
	J_CHICKENPOX_48=0.6, J_CHICKENPOX_74=0.6]
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 NmpEFnqP0ukt
	for <ietfarch-atompub-archive@core3.amsl.com>;
	Fri, 31 Oct 2008 22:43:03 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
	by core3.amsl.com (Postfix) with ESMTP id 1E3A83A6AA1
	for <atompub-archive@ietf.org>; Fri, 31 Oct 2008 22:43:02 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mA15abpg016969
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 22:36:37 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.14.2/8.13.5/Submit) id mA15abEo016967;
	Fri, 31 Oct 2008 22:36:37 -0700 (MST)
	(envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170])
	by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mA15aPx5016916;
	Fri, 31 Oct 2008 22:36:36 -0700 (MST)
	(envelope-from pjkeane@gmail.com)
Received: by wf-out-1314.google.com with SMTP id 25so1683826wfc.28
        for <multiple recipients>; Fri, 31 Oct 2008 22:36:25 -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:sender
         :to:subject:cc:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references
         :x-google-sender-auth;
        bh=UzgV5LU40U73F2W8Tj1XaJC+rzIwOTk05jnAtt77Bvk=;
        b=JcwxAXUOVxiKQAa7H9OvekWDd+pf18Guwtvu41mLQkCkHdqFTdNZzOfplVjC7a2N3r
         89TxmMeaGzg3M1rpntuiPRFp7CDuEZ6WlU+PykvJDaHBw+FIAfKt6cGya1t+KaVO6q6m
         KarW4xhnNJ1VxF1KHfiOLOEX6P7AM6r9HltSU=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=BUOHypkVRb5hEQ9fq+RHyaMc2ZB+pXD2F1BcOe77jEvRpuOOtlQTI4OW7e/MpkFXVN
         vNoDfDC8LOrbUbiasOJME0xZvs3PwOVfJR/nS0jFyRk9poUoSTwZFWGR225SO6QsJd63
         YqYvw/xy9pRJPg60yXedoNcS9D76MBgDmbfKk=
Received: by 10.142.255.14 with SMTP id c14mr5832004wfi.296.1225517785125;
        Fri, 31 Oct 2008 22:36:25 -0700 (PDT)
Received: by 10.142.142.1 with HTTP; Fri, 31 Oct 2008 22:36:25 -0700 (PDT)
Message-ID: <8158ad750810312236y3651b735u6d2c6d5beaf0504b@mail.gmail.com>
Date: Sat, 1 Nov 2008 00:36:25 -0500
From: "Peter Keane" <pkeane@mail.utexas.edu>
To: "Nikunj Mehta" <nikunj.mehta@oracle.com>
Subject: Re: draft-divilly-atompub-hierarchy-00
Cc: "atom-protocol Protocol" <atom-protocol@imc.org>,
        Atom-Syntax <atom-syntax@imc.org>,
        "Colm Divilly" <colm.divilly@oracle.com>
In-Reply-To: <490B826D.6070907@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <490B826D.6070907@oracle.com>
X-Google-Sender-Auth: 0b3fe72bf4c2b217
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>


I'm glad to see hierarchies in an I-D.  I have a few questions:

1. 3.1 states: "The kind of child Feed's metadata identifies the kind
of new Entries that it can accept."  I am not entirely clear what that
means -- is there a mechanism for determining the "kind" of metadata?
Seems like a job for atom:category, and a did see that an example in
7.3 included an atom:category w/ scheme
"http://finance.example.com/cat/kind" is that, in this case, the
"kind" to which the sentence in 3.1 is referring?

2. 3.1 states: "A master Feed MAY itself be a child of another master
feed."  is that child-master also considered a "detail feed" of it's
parent?  So would that feed be both a detail feed *and* and master
feed? and the entry that defines it both a "master entry" and a
"detail entry?"

3. Can a master entry have more than one detail feed? If so, how does
a client distinguish them?  (perhaps an atom:category child of the
atom:link@rel=detail for each?)

I have a sense that this I-D is aimed primarily at creating a
mechanism for managing feeds with feeds, using atompub, and perhaps
less about creating a generic mechanism for describing sub-feeds in
atom.  Here the master entry is really a convenient atompub capable
(since atompub focuses on entries, not feeds) "wrapper" for a feed w/
in a feed.  Is that an accurate characterization?   A more generic
mechanism for hierarchy in Atom might address multiple sub-feeds for
an atom entry and would likely not require that a feed be labelled a
"master" feed before the fact (i.e., any feed could have entries that
contained other feeds or not, and need not declare that
functionality/purpose up front).  I'm not suggesting this is good or
bad, just want to get a clear understanding of the purpose.

The implementation I work on has need for this exact sort of thing.  I
have addressed it a fairly generic way of allowing an entry to have an
atom:link@rel=service which points to an app:service document that
describes the sub-feeds that this entry has available for posting to
(typically, there is more than one).

--peter keane


On Fri, Oct 31, 2008 at 5:10 PM, Nikunj Mehta <nikunj.mehta@oracle.com> wrote:
>
> Fellow Atom and AtomPub'bers,
>
> We'd like to discuss the draft below that introduces extensions for Atom and
> AtomPub to deal with hierarchies of feeds and the programmatic creation and
> removal of AtomPub Collections.
>
> This draft defines a mechanism for identifying hierarchical master-detail
> relations among data feeds so that consumer applications can perform
> standard AtomPub operations on them. A hierarchical master-detail relation
> of an Entry to a Feed implies the detail Feed is created when the master
> Entry is created and the Feed is removed when the Entry is removed. The
> Entry is called the "master entry" and the Feed is called "detail feed".
> This relationship allows a client to use AtomPub to create a new Collection
> by posting an Entry to an existing Collection.
>
> Comments?
>
> Colm Divilly & Nikunj Mehta
>
> ==============================================================
>
>   Title        : Hierarchy Extensions to Atom Feeds
>   Author(s)    : C. Divlly and N. Mehta
>   Filename    : draft-divilly-atompub-hierarchy-00.txt
>   Pages        : 18
>
> This I-D is available at the following URL:
>
> http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atompub-hierarchy-00.html
>
> http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atompub-hierarchy-00.txt
>



