[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`
[ https://issues.oasis-open.org/browse/CAMP-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59335#comment-59335 ] Gilbert Pilz edited comment on CAMP-176 at 4/2/15 4:43 PM: ----------------------------------------------------------- Motion to resolve this by adopting the proposal at https://www.oasis-open.org/apps/org/workgroup/camp/download.php/55251/camp-spec-v1.1-wd49-issue-176-v1.doc was passed during the meeting of 2015-04-01. was (Author: gilbert.pilz): Motion to resolve this by adopting the proposal at https://www.oasis-open.org/apps/org/workgroup/camp/download.php/55251/camp-spec-v1.1-wd49-issue-176-v1.doc was passed during the meeting of 2015-04-01. The Working Draft incorporating this proposal is at: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/55387/camp-spec-vx.x-wd50.doc > 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 > Components: Spec > Reporter: Alex Heneveld > Assignee: Gilbert Pilz > > 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]