It's not going to replace attributes in general.

But in certain cases (i.e. key value pairs) it makes sense.

Anything that could benefit from implicit operations (add,remove, etc)

would need to be addressable (/foo=bar).

Ike

On Jul 23, 2011, at 9:47 PM, Heiko W.Rupp wrote:

- using resources instead of attributes
- using lists/maps of attributes instead the heavily nested constructs we have now.