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

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

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


Subject: [OASIS Issue Tracker] Updated: (CAMP-156) does every component resource need to link back to an assembly resource?


     [ http://tools.oasis-open.org/issues/browse/CAMP-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilbert Pilz updated CAMP-156:
------------------------------

    Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/52016/camp-spec-v1.1-wd36-156.doc  (was: If we decide the answer to this question is 'no', we can make 'assembly' an optional attribute of the 'component' resource and document when and how it should be used.)

Changed 'component.assembly' to 'component.assemblies' and re-defined it as an array of Links[] to assembly resources. Replaced PlatformAssociations diagram to agree with this change.

> does every component resource need to link back to an assembly resource?
> ------------------------------------------------------------------------
>
>                 Key: CAMP-156
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-156
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Gilbert Pilz
>            Assignee: Gilbert Pilz
>            Priority: Minor
>
> This is more of a question than a definite issue. Right now (WD32) the 'component' resource requires a link back to its containing 'assembly' resource (in the 'assembly' attribute). This makes sense for the first-level components (i.e. the components that are directly referenced by 'assembly.components') but what about the second, third, etc. level components (i.e. the ones that are referenced by 'assembly.components'->'component.related_components'). Does it really make sense to have every member of the component tree reference back to the top-level 'assembly' resource? What about components that appear in the trees of more than one assembly? Which 'assembly' resource should they link back to?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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