Actually, if there is enough support, there is a much better way out
as blogged earlier [1]. Of course, that is not currently included in
the hierarchy I-D [2], but that can change.
Atom syntax places no limits on the multiple occurrence of l...@rel
within a single entry or feed, except for a few relations defined in
RFC 4287. Also, I could technically use the term attribute previously
defined in the atom namespace to differentiate between the several
child feeds.
An example to illustrate my point:
<entry xmlns="..." xmlns:ah=".../">
<title>A folder entry</title>
...
<content src="..."/>
<link rel="self" href="/folder;metadata"/>
<link rel="down" type="application/atom+xml;type=feed"
title="Folder children collection"
href="/folder;contents/" term="contents" ah:count="0"/>
<link rel="down" type="application/atom+xml;type=feed"
title="Folder relationships collection"
href="/folder;relationships/" term ="relationships"
ah:count="0"/>
<link rel="related" type="application/atom+xml;type=feed"
title="Folder descendants feed"
href="/folder;descendants/" term ="descendants" ah:count="0"/>
<link rel="detail" type="application/atom+xml;type=feed"
title="Folder policy collection"
href="/folder;policies/" term ="policies" ah:count="0"/>
</entry>
Nikunj Mehta
http://o-micron.blogspot.com
[1]
http://o-micron.blogspot.com/2009/05/atom-multiple-links-with-same-rel-value.html
[2] http://www.ietf.org/internet-drafts/draft-divilly-atom-hierarchy-00.txt
On May 20, 2009, at 11:24 AM, Peter Keane wrote:
Hi Nikunj-
Very nice work. I have a couple of questions:
Can an entry contain more than one child feed (i.e. down link) of
different types? (I assume not per atom:l...@rel="down" (1..1)
cardinality constraint). In that case, would the entry have a child
feed that itself would contain parent entries, one for each feed of
varying type:
parent entry
-- child feed
-- -- parent entry
-- -- -- child feed type a
-- -- parent entry
-- -- -- child feed type b
Also, looks like IANA Atom Link registry already includes "up." This
ID is simply reusing that, correct?
--peter
On Wed, May 20, 2009 at 12:08 PM, Nikunj R. Mehta
<[email protected]> wrote:
Based on feedback received on this and the atom-protocol list as
well as
others interested in hierarchical relations in Atom, we have split
out the
hierarchical navigation and representation portions from
the draft-divilly-atompub-hierarchy-00. This was done with the
intention of
achieving consensus on the Atom syntax to be used for parent/child
like
navigation separately from how such resources are manipulated.
We look forward to the feedback of this community and will continue
to edit
the I-D to incorporate the feedback. Here are links to the I-D:
Text: http://www.ietf.org/internet-drafts/draft-divilly-atom-hierarchy-00.txt
HTML:
http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atom-hierarchy.html
Regards,
Nikunj
Begin forwarded message:
From: IETF I-D Submission Tool <[email protected]>
Date: May 20, 2009 9:54:15 AM PDT
To: [email protected]
Cc: [email protected]
Subject: New Version Notification for draft-divilly-atom-hierarchy-00
A new version of I-D, draft-divilly-atom-hierarchy-00.txt has been
successfuly submitted by Nikunj Mehta and posted to the IETF
repository.
Filename: draft-divilly-atom-hierarchy
Revision: 00
Title: Hierarchy Extensions for Atom
Creation_date: 2009-05-20
WG ID: Independent Submission
Number_of_pages: 10
Abstract:
This specification defines mechanisms for hierarchical navigation
among Atom feeds and entries.Editorial Note
To provide feedback on this Internet-Draft, join the atom-syntax
mailing list (http://www.imc.org/atom-syntax/) [1].
The IETF Secretariat.
Nikunj R Mehta | Consulting Member of Technical Staff | Phone: +1
650 506
0679 | Blog: http://o-micron.blogspot.com
Oracle Advanced Development Projects
500 Oracle Parkway #4OP662 | Redwood Shores, CA 94065
Oracle is committed to developing practices and products that help
protect
the environment
