[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New Version Notification for draft-divilly-atompub-hierarchy-00
On Tue, May 5, 2009 at 11:43 AM, Nikunj Mehta <nikunj.mehta@xxxxxxxxxx> wrote:
> We would like to solicit the group's feedback on this I-D. There is already
> some interest both internally at Oracle and from other parties in advancing
> this I-D along standards track.
> Regards,
> Nikunj
> Blog: http://o-micron.blogspot.com
> Begin forwarded message:
>
> From: IETF I-D Submission Tool <idsubmission@xxxxxxxx>
> Date: May 5, 2009 9:39:54 AM PDT
> To: nikunj.mehta@xxxxxxxxxx
> Cc: colm.divilly@xxxxxxxxxx
> Subject: New Version Notification for draft-divilly-atompub-hierarchy-00
>
> A new version of I-D, draft-divilly-atompub-hierarchy-00.txt has been
> successfuly submitted by Nikunj Mehta and posted to the IETF repository.
>
Hi Nikunj -
As I've said, i like the proposal very much. I do find the spec
somewhat hard to follow both due to some of the naming decisions (see
http://markmail.org/message/gsyuxqa22mpni3uq) and also because I am
not entirely certain of the scope of use cases being addressed. Have
you seen Tim Bray's "metacollections" post:
http://www.tbray.org/ongoing/When/200x/2008/07/07/Atom ? Would you
say this ID addresses this use (basically, a mechanism to created new
collections on an AtomPub server)?
Also, if I read it correctly, we are talking about hierarchy in which
a "child" is completely dependent upon it's parent (i.e., when the
parent is deleted, the child will be deleted as well)?
One use case I have is for organizing a catalog of fine art images.
There will be a collection of Artists, each artist represented by an
entry. Each entry will have a child feed of that artist's work, each
work represented as an entry in that child feed. A "work" entry will
also exist in a global Works feed and in the case of, say, an
anonymous work, will have no artist "master" entry. So obviously, a
work record is not dependent on it's parent. I assume this ID does
NOT cover that use case (is that correct)?
I am particularly interested just now since I am beginning work on a
fairly generic AtomPub server built on Google's AppEngine. I need a
good standard way for a logged in user to create their own collection
that they can then begin posting new entries and media items to. I am
assuming that's a core use case for this ID (much what Tim Bray was
talking about).
thanks-
Peter Keane
> Filename: draft-divilly-atompub-hierarchy
> Revision: 00
> Title: Hierarchy Extensions to Atom Feeds
> Creation_date: 2009-05-05
> WG ID: Independent Submission
> Number_of_pages: 18
>
> Abstract:
> This specification defines a mechanism to create and remove AtomPub
> collections using the AtomPub protocol as well as to express
> hierarchies of feeds within the Atom Syndication Format.Editorial Note
>
> To provide feedback on this Internet-Draft, join the atom-protocol
> mailing list (http://www.imc.org/atom-protocol/) [1].
>
>
>
> The IETF Secretariat.
>
>