BEGIN:VCALENDAR
CALSCALE:GREGORIAN
METHOD:PUBLISH
VERSION:2.0
PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T090000Z
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T100000Z
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
CATEGORIES:MEETING
STATUS:CONFIRMED
TRANSP:OPAQUE
DTSTAMP:20131121T000000Z
DTSTART;VALUE=DATE-TIME;TZID=America/Los_Angeles:20131113T100000
DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20131113T113000
SEQUENCE:4515
SUMMARY:Regular CAMP TC Call
DESCRIPTION:\n Dial-in:\n\n +1 866-682-4770\n +1
408-774-4073\n 1800932479 (Ireland toll free)\n +353 1 247
5650\n 0800-694-8154 (UK toll free)\n +44 208 118-1001\n +44
844 493-6817\n 800-819-5024 (CN toll free)\n +86 400
670-0514\n\n Other numbers:
https://www.tcconline.com/listNumbersByCode.action?confCode=3005864\n\n conf
id: 3005864#\n Password: \n\n Soaphub for notes and queue:
http://webconf.soaphub.org/conf/room/oasis-camp\n\n -------------------------------------------------------\n\n Webex:\n\n Meeting
Number: 596 151 450\n Meeting Password:
2267\n\n https://oracleconferencing.webex.com/oracleconferencing/j.php?J=596151450&PW=NYmE1YjY0NTZh\n\n http://www.webex.com\n\n
\n\n 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. \n\n \n\nAgenda: \n \n Intro:\n \n Scribe
appointment: call for volunteers starting from top of the
list [1]\n Roll Call\n Agenda approval\n \n Minutes:\n
\n 6th November 2013:
https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00041.html\n
- correction needed the minutes approved were for the 30th
october 2013.\n \n Notes from Scrum sessions: Session 1:
https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00051.html\n
Session 2:
https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00078.html\n
Session 3:
https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00094.html\n
\n Action Items:\n \n
\n Administrivia:\n \n \n Status:\n \n
Timeline:
https://www.oasis-open.org/apps/org/workgroup/camp/download.php/51056/CAMP%20sched%202013-10-16.pdf\n
Current open issues: 34 in total; 2 P1, 24 P2, 8
P3.\n Status after scrum sessions:
https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00097.html\n
\n \n Editing Team Update:\n \n WD29:
https://www.oasis-open.org/apps/org/workgroup/camp/document.php?document_id=51313\n
\n New Issues:\n \n \n \n Issue Discussion:\n \n \n \n
Pre scrum proposal: \n \n
https://tools.oasis-open.org/issues/browse/CAMP-72 Error
Response Message Resource looks like relic of a bygone
age\n Proposal in JIRA\n \n \n Scrum proposals:\n
\n Issues with proposal to change the spec:\n P1:
https://tools.oasis-open.org/issues/browse/CAMP-86 Nature
of YAML makes its suitability as a normative reference
problematic [trivial/editorial]\n
https://tools.oasis-open.org/issues/browse/CAMP-80 Section
6.11 "Registering an Application" is unclear about what
Content-Type header must be for various scenarios\n
\n P2:
https://tools.oasis-open.org/issues/browse/CAMP-144 no way
to correlate a resource's "type" value with the array of
type definitions contained in the TypeDefinitions
resource\n
https://tools.oasis-open.org/issues/browse/CAMP-118 4.3.2.4
services - "application in"? [trivial/editorial]\n
https://tools.oasis-open.org/issues/browse/CAMP-117 4.3.3
Artifact Specification\n
https://tools.oasis-open.org/issues/browse/CAMP-116 4.3
Deployment Plan Schema - well-formed/conforms to description
[trivial]\n
https://tools.oasis-open.org/issues/browse/CAMP-113 4.3.2.1
campVersion - SHALL?\n
https://tools.oasis-open.org/issues/browse/CAMP-109 4.3.1
General Attributes [trivial/editorial]\n
https://tools.oasis-open.org/issues/browse/CAMP-105 4.2
Deployment Plan Overview - RPM file?
[trivial/editorial]\n \n \n \n Issues with proposals to
close no action:\n \n P2:
https://tools.oasis-open.org/issues/browse/CAMP-147 Psuedo
schema in section 1.7 is not sufficient\n
https://tools.oasis-open.org/issues/browse/CAMP-143 Section
2.1.6 is a mess\n
https://tools.oasis-open.org/issues/browse/CAMP-114 4.3.2.2
origin\n
https://tools.oasis-open.org/issues/browse/CAMP-88 1.5 PaaS
Roles\n
https://tools.oasis-open.org/issues/browse/CAMP-84 Text
highlighting, Section 2.1.6 and following
(camp-spec-v1.1-csprd01)\n
https://tools.oasis-open.org/issues/browse/CAMP-79 Will
OASIS manage/approve common artifact types in the future?\n
https://tools.oasis-open.org/issues/browse/CAMP-42
Spec should say how to limit/specify the scope of returned
data\n
https://tools.oasis-open.org/issues/browse/CAMP-11
Expression of Scaling Policy\n \n P3:
https://tools.oasis-open.org/issues/browse/CAMP-69 Need
interoperable means to obtain the endpoint(s) of an
Application Component\n
https://tools.oasis-open.org/issues/browse/CAMP-59
Inconsistent definition of link attributes to point at
templates used to instantiate resource types\n
https://tools.oasis-open.org/issues/browse/CAMP-27 Should
CAMP surface the names of the application
states?\n \n \n Issues awaiting proposals:\n \n P2:
https://tools.oasis-open.org/issues/browse/CAMP-148 Section
3 is redundant, and
https://tools.oasis-open.org/issues/browse/CAMP-98 3
Application Management Lifecycle\n \n (148 and 98 to be
treated as one issue.\n
https://tools.oasis-open.org/issues/browse/CAMP-146
campVersion limits future compability\n
https://tools.oasis-open.org/issues/browse/CAMP-110 Values
for "attributeType" are not clearly defined.\n
https://tools.oasis-open.org/issues/browse/CAMP-102 4.1.2
Validating Integrity\n
https://tools.oasis-open.org/issues/browse/CAMP-74 Plans
resource does not have Parameters (direction proposed in
scrum session)\n
https://tools.oasis-open.org/issues/browse/CAMP-66 Creating
instance of a Platform Component (two choices outlined in
scrum session)\n
https://tools.oasis-open.org/issues/browse/CAMP-62 JSON
arrays of Links are more constrained than the underlying
implementation (direction proposed in scrum)\n \n P3:
https://tools.oasis-open.org/issues/browse/CAMP-128 C.1
Mandatory Statements (conflicting proposals)\n
https://tools.oasis-open.org/issues/browse/CAMP-73 Make the
style of figures consistent [trivial/editorial]\n
https://tools.oasis-open.org/issues/browse/CAMP-63
TypeDefinitions for CAMP-defined types (proposal needs
updating)\n
https://tools.oasis-open.org/issues/browse/CAMP-44 Clarify
resource type issues and API\n
https://tools.oasis-open.org/issues/browse/CAMP-26 Need to
define a core set of Platform Component types\n \n \n
\n \n AOB:\n \n Straggler roll\n -------\n \n [1] Scribe
rotations:\n \n Yendluri, Prasad (2)\n Johnston-Watt, Duncan
(3)\n Carlson, Mark (4)\n Heneveld, Alex (4)\n Byreddy,
Bhaskar Reddy (3)\n Rutt, Tom (4)\n Pilz, Gilbert
(10)\n Behrens, Michael (2)\n Otto, Adrian (7)\n Durand,
Jacques (7)\n Karmarkar, Anish (6)\n Agrawal, Roshan
(2)\n Raman, Krishna (4)\n Malhotra, Ashok (4)\n \nGroup:
OASIS Cloud Application Management for Platforms (CAMP)
TC\nCreator: Dr. Martin Chapman
URL:https://www.oasis-open.org/apps/org/workgroup/camp/event.php?event_id=33925
UID:https://www.oasis-open.org/apps/org/workgroup/camp/event.php?event_id=33925
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR
