In the past the way to get an item's children was to iterate on the item ("for child in item:"), but now that ItemCollection? overrides _ _ iter _ _ ( ), that changes the behavior. Iterating on an ItemCollection? returns results rather than children. I guess the way to get child items is to always call item.iterChildren( )
Opinions from others:
we want to reduce the usage of parent/child repo relationship
iterating on an item to get its children is awkward
Shared items: same UUID or not?
Seems convenient to use the same UUIDs (not sure it's possible with the current APIs though)
Do we need this?
Does it get implemented in the data model (modeled as a single item, same UUID) or in the content model (modeled as separate items, different UUIDs)?