[OASIS Issue Tracker] (OSLCCCM-1) Disallow nested components

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

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

Nick Crossley updated OSLCCCM-1:
--------------------------------

         Labels: ready-for-vote  (was: )
    Description: 
In the dcterms:description of the resource shape for Component, can we disallow or ignore nested components to simplify client processing?


  was:
In the dcterms:description of the resource shape for Component, can we disallow nested components to simplify client processing?


       Proposal: Make it clear that this spec assigns no meaning to a Component member of a Component, or to a Component being a selected version of a configuration - neither client nor server is required to do any recursive processing.  (was: Change the text to read:
Components themselves MUST NOT be nested - that is, the members of an <code>oslc_config:Component</code> container MUST NOT be of type <code>oslc_config:Component</code>;
)

> Disallow nested components
> --------------------------
>
>                 Key: OSLCCCM-1
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-1
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Priority: Minor
>              Labels: ready-for-vote
>
> In the dcterms:description of the resource shape for Component, can we disallow or ignore nested components to simplify client processing?



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