Should the workgroup address partial configurations - configurations whose specification is incomplete, resulting in more than one candidate version of one or more resources?
Proposed resolution: the OSLC spec should define a simpler change set resource that contains zero or more links to CIs - with version-specific links or links with a configuration context, so the change set identifies the exact version of each resource. These links point to the version of the resource that is the result of the specified change. For discussion: do we also want to specify an optional link that points to the version of the resource before the specified change? If so, what is the difference in semantics between these two links and the provenance link prov:wasRevisionOf?
Closed Issues
Issue 1
How should the configuration management specification address structure, containment, hierarchy, etc., of configuration items? What does it mean to say a resource is in a configuration?
Resolution: the configuration management vocabulary shall not define terms for any such structure. The specification will allow a configuration resource to have multiple types, including a linked data platform container, a PLM item or view, or any other resource type that implies member resources. However, the workgroup strongly recommends that all future OSLC specifications use Linked Data Platform containers, aggregations, or other well-defined structures where possible, rather than inventing domain-specific containers and collections, and we suggest that future OSLC Core specifications make this same recommendation.
