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] (CAMP-195) should type_definition resources be optional

Gilbert Pilz created CAMP-195:

             Summary: 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

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