[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCCM-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62589#comment-62589 ] 

James Amsden commented on OSLCCCM-22:
-------------------------------------

Ok, that makes sense. What do you see the client typically doing with this information about what configuration/component was used to resolve the concept URI in a request? Is this simply a means of reminding the user that configuration/component was used so they are able to continuously verify they are using the right configuration context for their work?

The typical use case would seem to be that a user creates a GC that includes the configuration contribution they need proactively. Then need to be very careful that they are including the configurations of components that properly reflect the work they are doing. Why would the client/user need to specifically verify this on each request? Wouldn't they rely on the CG to do the right thing based on the Configuration-Context they specified? 

The motivation for these questions is to limit the amount of information users are expected to process on any request.

> Provide a way for a client to discover the configuration used to resolve a request
> ----------------------------------------------------------------------------------
>
>                 Key: OSLCCCM-22
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-22
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Improvement
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>            Priority: Minor
>              Labels: work_required
>
> The spec allows a client to provide a configuration context using either a header or a query string, but there is no way for the client to discover if this configuration was actually used, or which contribution to a global configuration was used, to satisfy the request.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)