Meeting minutes by Dennis E. Hamilton OASIS CONTENT MANAGEMENT INTEROPERABILITY SERVICES (CMIS) TC Monday, December 22, 2008 17:00-18:00 UT (09:00 - 10:00 PST) 1. LOGISTICS AND ADMINISTRATION The chat room: http://webconf.soaphub.org/conf/room/cmis (doesn't count as attendance) Call-in information: http://wiki.oasis-open.org/cmis/MeetingInfo OASIS CMIS TC Wiki: http://wiki.oasis-open.org/cmis/ David Choy reminded us that the conference system provides a mute function for those who are not able to mute their own phones. Press "#5" to toggle between mute and un-mute. Mute should be used to prevent unwanted noise and echo when you are not speaking. 1.1 ROLL CALL; DETERMINE QUORUM - 13/26 - No quorum QUORUM CHECK: 13 of 26 Voting Members counted in the roll-call (14 required) - NO QUORUM Because there was no quorum, no committee actions were taken. Meeting Attendees: [added by David Choy] John Newton David Nuescheler David Choy Norrie Quinn Craig Randall Gregory Grefenstette Julian Reschke Derek Carr Patrick Ryan Dennis Hamilton Gershon Janssen Florent Guillaume Jens Huebel Paul Goetz Volker John This meeting counts for attendance purpose, even though a quorum was not achieved 1.2 ACCEPTANCE OF PREVIOUS MEETING MINUTES [1] - NO ACTION 1.3 ACCEPTANCE OF TODAY'S AGENDA [2] - NO ACTION 1.4 FYI David Choy reported that AIIM will have two members on the committee. In response to a question about sending proxies to the Face-to-Face (F2F) meeting, David reported that proxies are not permitted for any members at an OASIS TC meeting. * FYI (if any) - Chair, Secretary/Editor, Liaison 2. HIERARCHICAL/COMPLEX PROPERTY DISCUSSION David Choy summarized the list conversation on the different aspects and the thoughtful treatment now available on the list and on the wiki. - We discussed whether or not this is critical for CMIS 1.0, with some leaning toward deferral to a later version. - It is being asked who has a mandatory need for the feature. - There is concern that whatever is done in CMIS 1.0 does not create problems for addition later, including backward-compatibility issues. 3. CMIS 1.0 SETBACK REQUIREMENTS FOR ACHIEVING STANDARD - It was asked whether the setbacks from completion of final working draft to formal availability of an OASIS Standard is understood. - It was asked whether there is an intention to take an OASIS Standard to ISO [because that influences the form of the specification and some other matters --dh:] - It was suggested that until all of the issues are known, it is difficult to know how long it would take [to get to a committee-acceptable working draft candidate for 1.0] - Based on experience with other substantial standards, it was observed that we could easily have 1000 issues to resolve before CMIS 1.0 is baked. 4. QUICK STATUS DISCUSSION ON OTHER PROPOSALS: ACCESS CONTROL, MIXIN TYPE, REST ENHANCEMENT 4.1 ACCESS CONTROL LISTS A link to the current draft is on the wiki. http://wiki.oasis-open.org/cmis/ACL_Proposal The 0.3 draft document can be provided (some difficulty being able to upload to the CMIS TC area). 4.2 MIXIN TYPE John Newton needs to add thoughts about Mixin types, and consideration of joins between base objects and the mixin itself. Thinking of using the policy mechanism as a way to apply a Mixin. To be added to the wiki. 4.3 REST ENHANCEMENT Julian Reschke has been submitting material and noticed a number of things. It was observed during this discussion that we want to get the tough issues into the open for discussion and resolution at the F2F meeting. David Nuescheler has some container issues and those need to be worked on. Some REST provisions have implications throughout the specification, and the CMIS headers figure into this. David Nuescheler suggested becoming more properly RESTful in nature. We should probably say we are making an AtomPub binding and not talk about "REST binding" at all. 5. ISSUE RESOLUTION PROCESS David Choy emphasized that we need to get this right and we need to do this carefully. All issues must be brought to the TC for explicit resolution is the basic idea. There is a straw-man proposal from Gershon Janssen with a flow-chart. We should customize it for us. Gershon pointed out how it helps to keep our work organized. Choy proposed to revise the flow-chart a little bit. We can refine it off-line. Intent is to have a ballot on it and have it approved, after the 01-26 meeting. There is some concern about having this in place for demonstrating that we've taken a responsible approach to moving to an 0.52 working draft coming out of the F2F meeting. 6. REFERENCE IMPLEMENTATION There was a question whether a reference implementation (RI) is required and should it be part of the CMIS TC work or be something that friends-of-CMIS undertake on the side. It was also observed that an RI is not as important for demonstrating implementability as having running implementations that cover the feature space and can be used interoperably. David Choy's thinking is that a test kit is more important than an RI, and what is the value of a formal RI from CMIS TC. Concern that any RI not be a commercial implementation and that it be something that is open for anyone to use, adapt, etc. End of the 10:03 AM. Happy holidays, etc. January 12 is the next call. 7. NEXT CALL Monday, January 12, 2009 We ended at 18:04 UT [1] Al Brown: 2008-12-08 Meeting Minutes http://www.oasis-open.org/committees/download.php/30331/2008-12-08%20Meeting%20Minutes.txt [2] David Choy: Agenda for Dec 22 TC meeting http://lists.oasis-open.org/archives/cmis/200812/msg00064.html [end of 2008-12-22 Meeting Notes]