OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-ccm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OSLCCCM-2) Disallow configurations as members of a component


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

Nick Crossley updated OSLCCCM-2:
--------------------------------

    Proposal: 
Add the text:
The members of an <code>oslc_config:Component</code> container MUST NOT be of type <code>oslc_config:Configuration</code>; sub-configurations are given in the oslc_config:contributions property.
Also clarify that there is no assigned meaning to a Component as a member of a Component.


  was:
Add the text:
The members of an <code>oslc_config:Component</code> container MUST NOT be of type <code>oslc_config:Configuration</code>; sub-configurations are given in the oslc_config:contributions property.



> Disallow configurations as members of a component
> -------------------------------------------------
>
>                 Key: OSLCCCM-2
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-2
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>            Priority: Minor
>
> In the dcterms:description of the resource shape for a Component, can we exclude sub-configurations from appearing in this member list of configuration items?



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]