[OASIS Issue Tracker] (OSLCCCM-10) Are multiple global configuration providers supported, and how do they discover each other?

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

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

David Honey commented on OSLCCCM-10:
------------------------------------

This is related to https://issues.oasis-open.org/browse/OSLCCCM-9. A GCM OSLC service provider can specify a oslc:domain of oslc_config, but that is insufficient to differentiate an aggregating CM provider (such as GCM) from one that is non-agrregating (such as from a domain tool). Where a GCM provider supports constructing a hierarchy of GCs from different GCM providers, it can be treated as just another CM provider. Where a GCM provider does not support constructing a hierarchy of GCs from different GCM providers, it needs to either of both of the following:

1) prevent the user selecting another GCM provider for contributions. This means that an OSLC client must be able to determine whether a CM provider is a GC provider. We don't seem to have a standard means to achieve that.

2) prevent the user from adding a GC from another provider by checking the RDF of that GC indicates it is a GC (has oslc_config:accepts oslc_config:Configuration and oslc_config:acceptedBy oslc_config:Configuration). This is covered by the OSLC Configuration Management spec and already used in Rational GCM.

> Are multiple global configuration providers supported, and how do they discover each other?
> -------------------------------------------------------------------------------------------
>
>                 Key: OSLCCCM-10
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-10
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Configuration Management
>            Reporter: Nick Crossley
>




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