On 05/03/2013 02:25 PM, Gabriel Hurley wrote: >> I prefer /capabilities, because this also fits well with important discoverability >> things in swift like max object size or max object metadata (ie everything >> defined in https://github.com/openstack/swift/blob/master/etc/swift.conf- >> sample#L15). > > That's a good argument in favor of "capabilities". I personally prefer the term "capabilities" as well because it uncouples the concept from the in-code "extensions" mechanism that some projects use. I don't think that a 1:1 mapping there is beneficial, for exactly the reason above and more. When we put the Glance v2 API proposal together, it had exactly the above, only we called it "server metadata" instead of capabilities... https://docs.google.com/document/d/19IapP5ziQp8ISuZIQh_CXVWx2um85T_PiT5hyNviRrE/edit#heading=h.l9zfgmat6fv2 -jay