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-176) in `xxx` allow `type` as a synonym for `xxx_type`


Alex Heneveld created CAMP-176:
----------------------------------

             Summary: in `xxx` allow `type` as a synonym for `xxx_type`
                 Key: CAMP-176
                 URL: https://issues.oasis-open.org/browse/CAMP-176
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Improvement
            Reporter: Alex Heneveld


Plans become much easier to read if we allow people to simply refer to a `type` in their artifact/service/requirement definitions.

Calling them `aritfact_type` and `service_type` and `requirement_type` is just long-winded and redundant in almost all cases.

I suggest accepting the longer form `xxx_type` for an `xxx` in case there is any ambiguity.




--
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]