| If so, I'm not terribly fond of this approach. To date we have been mostly | dealing with how to handle labeling of the version of leaf nodes in a | heirarchy. However, the general case for configuration management is that | there is a heirarchy of versioned collections of versioned resources. | Ideally, what is needed to handle this is a naming mechanism like: | | http://foo.bar.com/top;version=rev_2.0/middle;version=14.2/leaf;version=5.5 | | Unfortunately, the URL specification at present does not allow parameters | to be included in each level of the heirarchy. Unfortunately, versioned containers is a pit. Nonetheless, embedding the /version=_version/ into the path is the only way to support them. The ;version= suffix won't cut it. Christopher