We discussed whether CM actions such as check out should be covered in phase 1, or whether users performed these actions in the underlying tool, perhaps with a delegated UI picker to create links between configuration items or configurations and other resources such as change requests.
We discussed the need for versioning providers to support two types of resource URIs: absolute and composite (perhaps there is a better term?). An absolute URI always resolves to the same version of a resource. A composite is composed of a concept URI plus some context that the underlying versioning provider resolves to a particular version of that resource. This resolution may change over time. Examples of context might include effectivity for PLM tools, streams for SCM tools and so on.
