Nikunj R. Mehta 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
...
Ni Nikunj,
with respect to
<http://tools.ietf.org/html/draft-divilly-atom-hierarchy-00#section-3>,
"Inline Representation of Hierarchical Resources"...
It seems to be that using atom:link as a container elements stretches
its semantics of "reference from an entry or feed to a Web resource" too
much.
As Al pointed out on the CMIS mailing list
(<http://lists.oasis-open.org/archives/cmis/200905/msg00186.html>), it
may be better to use a container element inside atom:entry.
So, the example in
<http://tools.ietf.org/html/draft-divilly-atom-hierarchy-00#section-3.2.3>:
<atom:entry>
<atom:link rel="down"
href="/finance/feeds/default/portfolios/1/positions">
<atom:feed>
<atom:link rel="self"
href="/finance/feeds/default/portfolios/1/positions"/>
...
</atom:feed>
</atom:link>
...
</atom:entry>
would become
<atom:entry>
<atom:link rel="down"
href="/finance/feeds/default/portfolios/1/positions" />
<ah:children>
<atom:feed>
<atom:link rel="self"
href="/finance/feeds/default/portfolios/1/positions"/>
...
</atom:feed>
</ah:children>
...
</atom:entry>
BR, Julian
