[OASIS Issue Tracker] (OSLCCCM-21) Provide a way for a client to discover the default configuration for a given configuration provider

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

     [ https://issues.oasis-open.org/browse/OSLCCCM-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Crossley updated OSLCCCM-21:
---------------------------------

    Proposal: 
Provide a link in the service document that references a ConfigurationSettings resource, which has a property identifying the default configuration. A GET on this resource would return this property (amongst any others). A missing property, or a property with an rdf:nil value, implies there is no default configuration, so requests with no context will fail.

A PUT on this resource MAY be supported. Servers MAY provide other ways for users to set the default configuration.

  was:Provide a link in the service document that references a ConfigurationSettings resource, which has a property identifying the default configuration. A GET on this resource would return this property (amongst any others). A PUT on this resource MAY be supported. A missing property, or a property with an rdf:nil value, implies there is no default configuration, so requests with no context will fail.


> Provide a way for a client to discover the default configuration for a given configuration provider
> ---------------------------------------------------------------------------------------------------
>
>                 Key: OSLCCCM-21
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-21
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Improvement
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Priority: Minor
>
> The spec allows a server to provide a default configuration context, but no way for the client to discover what this default is. It would be useful for the client to be able to do so.



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