[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Draft Minutes 24th July 2013
Meeting Minutes 24th July 2013
Attendees:
US Department of Defense (DoD) Michael Behrens Voting Member
Oracle Mark Carlson Voting Member
Oracle Martin Chapman Chair
Cloudsoft Corporation Limited Alex Heneveld Voting Member
Oracle Anish Karmarkar Voting Member
Oracle Ashok Malhotra Voting Member
Rackspace Hosting, Inc. Adrian Otto Secretary
Oracle Gilbert Pilz Voting Member
Fujitsu Limited Tom Rutt Voting Member
Software AG, Inc. Prasad Yendluri Member
Intro:
Anish Assumes scribe duties
Roll: Attendees listed above
Voting Members: 9 of 11 (81%), meeting is quorate
Topic: agenda bashing
Martin reviews agenda
MOTION: m:gil s:adrian to approve agenda
anish asks to discuss PR plans
motion approved w/o objection
Topic: approval of minutes
17th July 2013: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201307/msg00071.html
MOTION: m: gil s: anish approve minutes 2013-07-17 call located at https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201307/msg00071.htm l
motion approved w/o
Topic: administrivia
Adrian did talk to the ETSI ppl.
Gil sent them a link to the TA
Adrian: they did find a bug and I will file an issue for it
Topic: updated timelines/status
martin discusses the new timeline
https://www.oasis-open.org/apps/org/workgroup/camp/document.php?document_id=50034
Current open issues: 29 in total; 3 P1, 17 P2, 9 P3.
Topic: editing team update
Gil: got wd18 out. Added 55 issue resolution
... harder to process as there were lots of changes in lot of places including heading changes
Tom: simplified diagrams for lifecycle are in WD18
Martin: TC process requires that we include an ack section including all the participants in the TC
... have prepared the list. Contains everyone who is a member and has attended at least one meeting
Martin: if you want your name removed or if you think we left someone out, please let me know
... by next tuesday
Topic: new issues
Gil: filed issue 74 https://tools.oasis-open.org/issues/browse/CAMP-74
Gil explains the issue
Motion: m: gil s: Adrian to open issue 74
motion approved w/o
Alex Heneveld (Cloudsoft): All components are created equal. Link 74 to CAMP-29 !
Gil: filed issue 75 https://tools.oasis-open.org/issues/browse/CAMP-75
motion: m:gil s:alex to open issue 75 as a p2 issue
mike: would this remove a feature?
gil: no it would just remove outdated text
mike: removing it sounds good
motion approved w/o
Gil: filed issue https://tools.oasis-open.org/issues/browse/CAMP-76 , usecases are no longer necessary
Adrian: i never read the appendix. If we keep this would like to see it in a separate doc
ashok: we are going to add a scaling example in the appendix. What are we going to do about that?
Michael Behrens: +1 separate doc for use cases, non-normative/informational doc.
martin: this is about usecases, not scaling examples
alex: i think a separate doc is the right place to put all the non-normative stuff. May be a primer doc
motion: m:gil s:anish to open issue 76 as a p2 issue
motion approved w/o
anish: wonder if we can resolve it now and nuke the appendix
martin: we need an action for a new doc so it doesn't get lost
gil: if someone cares then they'll bring it up
motion: m:gil s:alex resolve issue 76 by removing the usecase appendix
motion approved w/o
motion: m:gil s:mikeB resolve issue 75 by removing section 6.11 in WD18
motion approved w/o
Gil: filed issue https://tools.oasis-open.org/issues/browse/CAMP-77 about example DB is out of date.
We have made lot of changes since we created that appendix
motion: m:gil s:alex to open issue 77 as a p2 issue assigned to Gil
motion approved w/o
Gil Pilz (Oracle): anyone want to move to resolve?
Gil: filed issue https://tools.oasis-open.org/issues/browse/CAMP-78 , same deal. Out of date scaling example
Gil: scaling example does not talk about sensors
... may be material for primer
Alex Heneveld (Cloudsoft): do we have an issue for a primer ?
Ashok: we agreed that we are going to add an example. The example would talk about operations and sensors. We can take it out and back in again.
@alex no
Alex Heneveld (Cloudsoft): (i thought we did but search for "primer" returns nothing)
motion: m:gil s:alex to open issue 78 as a p2 issue assigned to Gil
motion approved w/o
motion: m:gil s:gil resolve issue 78 by removing appendix E in WD18
motion approved w/o
Alex Heneveld (Cloudsoft): thx @anish. will create an issue to remind us, and to reference the removed appendices from WD18 as they could be useful material there.
topic: Issue 45 - Normative Statement Overhaul https://tools.oasis-open.org/issues/browse/CAMP-45
Gil presents his proposal
Alex Heneveld (Cloudsoft): +1 @gil superb work
Adrian: would like to recognize the effort that this proposal took
Alex Heneveld (Cloudsoft): i have to leave but nice work!
gil: builds on the work that Tom did
gil explains his 'rose'-colored highlighting
mandatory and non-mandatory stmts are separated out in different tables
gil: MUSTs got turned into SHALLs
Arian: like the formatting, but will it appear in HTML
anish: i have done this before and word generates the right styles for HTML
gil: note to editors this is all a character-style
... not section-style
tom: i struggled with complex nested normative stmts. looks like you tackled that
gil: as an example see section 4.1.1, i just broke it out as separate stmts
... allows us to be more precise in errors
gil: for some (eg RE-11) didn't make sense to break it up
Gil: this issue is disruptive to the editing process. So wanted to get this done: tagging, highlighting, formatting. There will be duplicates etc, but those are different issues
More discussion on the changes Gil made (including changes from may->can etc)
Gil: should mention that I did not update section 6.11, but we just got rid of it
MikeB: is the pink coloring part of the style and is that meant to be in the final doc? And is it normal?
Gil: yes
MikeB: what about italicized?
Martin: the TC can decide
Tom: in registering the PDP there were a lot of "is"s, did you change that?
Gil: no
Gil: was less comfortable creating new normative stmts where nothing existed
anish: the styles can be easily changed
Mark: if there is normative language that should be inserted (and doesn't exist now) that should be a separate issue
Mark speaking for attendance
Motion: m:gil s:tom moves to resolves 45 with proposal at https://www.oasis-open.org/apps/org/workgroup/camp/download.php/50039/camp-spec-v1.1-wd18-issue45-v1.doc
no discussion
motion approved w/o
Adrian Otto (Rackspace): applause
Topic: Add Conformance Section https://tools.oasis-open.org/issues/browse/CAMP-56
Martin posed a proposal Adrian made a revision to it
Martin and Adrian explain the proposal
anish: the 'provider' and 'consumer' should have first letter capitalized, esp. if that is what is used in 45
martin: that should be capitalized
adrian: did you mean "Targets" with capital T?
martin: lower case is fine
adrian: made a few changes already in v3
https://www.oasis-open.org/apps/org/workgroup/camp/download.php/50073/camp-spec-v1.1-wd18-issue-56v3.doc
motion: m:anish s:adrian resolve issue 56 with proposal in https://www.oasis-open.org/apps/org/workgroup/camp/download.php/50073/camp-spec-v1.1-wd18-issue-56v3.doc with instructions to the editors to fix case for 'provider', 'consumer' and 'Targets'
no discussion
motion approved w/o
topic: issue 61 CAMP is vague about which HTTP methods each resource supports
proposal from gil at https://www.oasis-open.org/apps/org/workgroup/camp/download.php/50051/camp-spec-v1.1-wd18-issue-61-v1.do c
gil explains his proposal
Anish Karmarkar (Scribe) btw we should not call HTTP a transport protocol. that is like waving a red flag to the RESTafarians
Gil explains section 5.5
Adrian: like it, but it does not mention delete
gil: this is just boilerplate, there is more to the proposal
gil: thanks to Alex for clarification on section 5.10
motion: m:gil s:tom resolve 61 with proposal at https://www.oasis-open.org/apps/org/workgroup/camp/download.php/50051/camp-spec-v1.1-wd18-issue-61-v1.doc with instructions to the editors to tag new normative stmts and put in the table
no discussion
motion approved w/o
Adrian Otto (Rackspace): celebration of resolution of all P1 issues!!
Topic: Plan for PR
martin: we have resolved all our P1
... significant milestone
anish: need to plan for PR and PR vote
... suggest a vote for next call
gil: i can take these issues that we just resolved and create a new WD by friday morning
... would like to do clean up as a separate thing (WD)
... will provide a candidate draft on monday morning
martin: is that enough time for the TC members?
anish: still a draft, but will be declaring to the world that this is a PR draft seeking feedback
tom: few new issues filed today (eg: missing params), when would we fix that
martin: yes we would be fixing those after the PR starts
no one uncomfortable with plan that Gil laid out
martin: we should expect a PRD01/CSD03 motion next week
gil: urge people to take the time on friday/monday to read the spec and give me feedback quickly. I'll try fold it in quickly
martin: we agreed at the f2f to take into account august vacation season and end the PR on sept 13
Topic: AOB
Martin: tom has given a notice for LOA for next two weeks. No action required by the TC
topic: stragglers
martin: added Mark
Meeting Adjourned
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]