We have a significant and growing number of properties in the specification. I don't believe that an oepration to get 
each property is a good idea, as many properties are optional and some might be aded by the container for its own 
specific needs.

The WSRF rendering has no problem with this, as it simply picks up standardized operations for those specs. The basic 
version could do exactly the same thing, but for just one operation without buying into the whole WSRF thing. For 
example, the base rendering could include the GetResourePropertyDocument operation (effectively the same as the WS-
Transfer get operation). Then the WSRF heads could add the rest on their own.

However, if referencing the WSRF spec is too politically charged, we could define our own version of the oepration, e.g.
 GetContainerProperties, which has exactly the same semantics as WS-Transfer.Get and WSRF.GetResourcePropertDocument.