Hierarchy ID draft

[Al Brown <albertcbrown@us.ibm.com>]

Nikunj,

Thanks for coming up with the split draft[1] based on the wg call.

Section 2.1:
1.On a feed, it would be worthwhile to have the alternate representation (e.g., down or down-tree) as a link.
2. Down - this can be 0..1 rather than 1..1. Some entries may be leafs. It might be better to not specify cardinality in the basic ID
3.On an entry, I'd like to be able to specify up and up-tree.

Section 2.2 - I would prefer the hierarchy navigation ID to be only about navigation. This section describes containment behaviors to be inclusive of a node being in more than one location in the graph. Even though it is permissive, I am not sure this ID should say anything about the containment model.

Section 3
1. I would prefer a much simpler model rather than containing in link elements. It seems much more natural to represent down-tree as:
<atom:entry>
<atom:entry> </atom:entry>
...
</atom:entry>

or even

<atom:entry>
<ah:children>
<atom:entry> </atom:entry>
...
</ah:children>
</atom:entry>

One of the issues we have discussed on the wg, is what if the hierarchy does not want to be represented as a link? E.g., that portion of the tree does not have a URL at all? In this model, every node has to have an URI associated with it and that URI has to be calculated. How would I in the atom document format describe a tree that is self contained?

Thanks,
-Al
[1] http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atom-hierarchy.html

Al Brown
Emerging Standards and Industry Frameworks
CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home
Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home

Office 714 327 3453
Mobile 714 263 6441
Email albertcbrown@us.ibm.com
CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.