Luke Arno wrote:
I want a profile that would *allow* for hierarchy.
-1. "Allowing" for hierarchy in the core means that my client has to
support it. "Not preventing" means that some extension can come along
later and define it but that my client can still function without it.
Unless use cases can be presented that demonstrate a hard requirement
for nesting, I will continue to be -1 against any language going into
the core that explicitly allows for nested collections. I am strongly
+1 in favor of not putting any language into the draft that forbids
collections from being nested.
- James
