Regular CAMP TC Call (Conference Call) | |
Name | Regular CAMP TC Call (Conference Call) |
Time | Wednesday, 27 February 2013, 10:00am to 11:30am PST
(Wednesday, 27 February 2013, 06:00pm to 07:30pm UTC) |
Description | Dial-in:
+1 866-682-4770 Other numbers: https://www.tcconline.com/listNumbersByCode.action?confCode=3005864
conf id: 3005864# Soaphub for notes and queue: http://webconf.soaphub.org/conf/room/oasis-camp ------------------------------------------------------- Webex:
Meeting Number: 596 151 450 https://oracleconferencing.webex.com/oracleconferencing/j.php?J=596151450&PW=NYmE1YjY0NTZh
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. You should inform all meeting attendees prior to recording if you intend to record the meeting. Please note that any such recordings may be subject to discovery in the event of litigation.
|
Minutes | Link to minutes approved on 6th March 2013: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/48467/Minutes%2027th%20Feb%202013.txt |
Agenda |
Intro:
Scribe appointment: call for volunteers starting from top of the list [1]
Roll Call
Agenda approval
Minutes:
20th February 2013: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201302/msg00105.html
Action Items:
Administrivia:
Next F2F 3-5th April:
logistics: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201302/msg00113.html
Editing Team Update:
WD06: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201302/msg00129.html
New Issues:
https://tools.oasis-open.org/issues/browse/CAMP-55 Lifecycle Diagram is conflating two levels of states, leading to inconsistencies
https://tools.oasis-open.org/issues/browse/CAMP-56 Add Conformance Section
Issue Discussion:
P1- http://tools.oasis-open.org/issues/browse/CAMP-30 Parameter Scheme
Proposal in JIRA
P1 -http://tools.oasis-open.org/issues/browse/CAMP-34 Immutable and read-only attributes in the REST world
Proposal in JIRA
P2 - http://tools.oasis-open.org/issues/browse/CAMP-52 Use of Cardinality for JSON array attributes
Proposal in JIRA
P2 - http://tools.oasis-open.org/issues/browse/CAMP-50 spec needs to clarify behavior in the case of duplicate JSON keys
Proposal in JIRA
P1 - http://tools.oasis-open.org/issues/browse/CAMP-21 Clarify whether App Developers/Admins can assume what the Assembly
Template tree looks like until post-deploy
Further discussion in JIRA
AOB:
Straggler roll
-----
[1] Scribe rotation:
Behrens, Michael
Grange, Keith
Miller, Rich
Mischkinsky, Jeff (1)
Yendluri, Prasad (1)
Song, Zhexuan (1)
Jilk, David (1)
Byreddy, Bhaskar Reddy (1)
Luster, Eugene (1)
Heneveld, Alex (1)
Karmarkar, Anish (1)
Malhotra, Ashok (1)
Rutt, Tom (1)
Otto, Adrian (2)
Johnston-Watt, Duncan (1)
Durand, Jacques (2)
Carlson, Mark (2)
Roshan, Agrawal (1)
Tupitza, Charles (1)
Pilz, Gilbert (3)
Krishna Raman (1) |
Submitter | Dr. Martin Chapman |
Group | OASIS Cloud Application Management for Platforms (CAMP) TC |
Access | This event is visible to OASIS Cloud Application Management for Platforms (CAMP) TC and shared with
|