[OASIS Issue Tracker] (CAMP-195) should type_definition resources be optional

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

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

Gilbert Pilz updated CAMP-195:
------------------------------

    Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/58121/camp-spec-v1.2-wd09-issue-195-v1.doc

Added link to concrete proposal.

> should type_definition resources be optional
> --------------------------------------------
>
>                 Key: CAMP-195
>                 URL: https://issues.oasis-open.org/browse/CAMP-195
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>    Affects Versions: 1.2
>         Environment: WD04
>            Reporter: Gilbert Pilz
>            Assignee: Anish Karmarkar
>            Priority: Minor
>
> As of WD04 the specification treats the existence of type_definition resources and the top-level type_definition resource collection as optional. If your implementation of CAMP does not add any new resources or extend any of the CAMP-defined resources, a Provider is not required to implement any type_definition resources or the top-level type_definition resource collection. Now that every resource references the type_definition resource that defines its structure, we should probably revisit the idea that type_definition resources are optional.



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